Skip to main content
GET
Check Blacklist & Sanctions
Check if a blockchain address is blacklisted by token issuers (Tether, Circle, Coinbase, PayPal, Paxos, Agora, Ripple) or listed on any sanctions list Range ingests: OFAC, UK, EU, EU Russia sanctions packages, France, and Japan, plus Israeli NBCTF seizure orders and FBI IC3 advisories. See Understanding Risk Scores for how this fits into Range’s broader risk methodology.
  • Token Blacklist Events: Real-time monitoring on Ethereum, Tron, Solana, Base, Arbitrum, Optimism, Polygon, and Avalanche for specific token issuers.
  • Sanctions Lists: Sourced from official government publications and network-agnostic. The response names every list the address is on in sanctions.
is_sanctioned and is_ofac_sanctioned are different flags. is_sanctioned is true when the address is on any government sanctions list: OFAC, UK, EU, EU Russia packages, France, or Japan. is_ofac_sanctioned covers OFAC only, so an address sanctioned by the UK but not by OFAC returns is_ofac_sanctioned: false and is_sanctioned: true. Israeli NBCTF seizure orders and FBI IC3 advisories appear in sanctions but do not set is_sanctioned. For a broader check for malicious actors and exposure, use Address Risk (v2) or Address Risk Score (v1).
Pre-sign gates must fail closed. lists_checked: false means a sanctions or blacklist store could not be read, so the result may be incomplete. is_sanctioned is then null unless a listing was found anyway, and false values in is_ofac_sanctioned and is_token_blacklisted are not a clean result either. Treat the address as unknown: block or retry, never allow.

How It Works

The endpoint performs these checks:
  1. Token Blacklist Check: Monitors onchain blacklist events emitted by token issuer contracts on Ethereum, Tron, Solana, Base, Arbitrum, Optimism, Polygon, and Avalanche. When issuers like Tether or Circle blacklist an address, it is blocked from transferring their tokens. The endpoint tracks freezes (blacklist), releases (unblacklist) and burns of a frozen balance (destroyedblackfunds) in real-time to determine the current status.
  2. OFAC Sanctions Check: Cross-references the address against the US Treasury OFAC Specially Designated Nationals (SDN) list. OFAC data is sourced from official published reports and covers any network published by OFAC.
  3. Other Sanctions Lists: Cross-references the address against every other list Range ingests (see Sanctions List Coverage). Each list the address is on, OFAC included, is one entry in sanctions.
  4. Attribution Data: In addition to real-time blacklist events, the endpoint includes attribution labels that may provide extended context and information beyond what is captured in onchain events.
Note: The is_token_blacklisted field reflects the current status based on the most recent event. An address that was blacklisted and later unblacklisted will show false. Use blacklist_event_history to view the complete history.

Path Parameters

Query Parameters

Note: network does not narrow the check. Blacklist status and sanctions lists are looked up by the address alone, across every network, so an EVM address frozen on any EVM network is flagged whichever network you pass. The value is only echoed in network when the address has no record. Accepted values are ethereum, tron, solana, base, arbitrum, optimism, polygon, and avalanche. Any other value returns HTTP 400.

Sanctions List Coverage

Sanctions list data is sourced from official government publications and is network-agnostic. If an address appears on a list, it is flagged across all 300+ supported networks. See Supported Chains for full coverage. The signal_id is the same signal the Address Risk endpoints fire for that list: the signal value in Address Risk (v2) and a risk_categories entry in Address Risk Score (v1). List Signals & Behaviours returns the full catalog. sanctioned is Range’s generic label for an address on a government sanctions list with no single named list; it is left out of sanctions when the address is also on a named government sanctions list. NBCTF and FBI IC3 listings do not count, so an address on NBCTF and the generic label keeps both entries. See Risk Data Sources for each source.

Direct and Indirect Listings

  • direct: the list names this address itself. OFAC, UK, France, Japan, NBCTF, and FBI IC3 entries are direct, and so are EU entries where the EU financial sanctions file names the address.
  • indirect: the list designates an entity or token, not the address, and Range attributed the address to it. The EU lists name entities rather than crypto addresses, so most EU entries are indirect, for example a wallet of an EU-sanctioned Russian entity or an A7A5 token holder. The generic sanctioned label is also indirect.
Both set is_sanctioned. An indirect entry rests on Range attribution, not on the list itself, so you can route it to review instead of an automatic block if your policy distinguishes the two.

Supported Networks & Tokens (Blacklist Events)

Real-time blacklist event monitoring is available for the following token issuers: An EVM address is looked up by the address alone, so a freeze on any EVM network flags it on every network. See Supported Tokens for the issuer of each token.

Response Schema

The response contains the sanctions and blacklist status for the queried address. This example is a Bitcoin address of Rapira Group, on the UK sanctions list but not on OFAC’s.

Top-Level Fields

Sanctions

One entry per list the address is on. See Sanctions List Coverage for every value of signal_id, source, and jurisdiction.

Token Status Summary

Shows the current blacklist status for each token and network that has flagged this address, one entry per token and network.

Blacklist Event History

A chronological record of all onchain blacklist and unblacklist events.

OFAC Info

Details about OFAC sanctions. Only present when the address is sanctioned.

Attribution

Additional context and labels for the address, which may include information beyond onchain events.

Examples

UK Sanctioned Only (Not OFAC)

The Rapira Group address from Response Schema is on the UK list only. is_ofac_sanctioned is false, while is_sanctioned is true and sanctions names the UK list.

Sanctioned on Several Lists

Garantex (0x7FF9cFad3877F21d41Da833E2F775dB0569eE3D9) is on OFAC, UK, and EU lists and is token blacklisted. The response has is_token_blacklisted: true, is_ofac_sanctioned: true, and is_sanctioned: true, with one sanctions entry per list. The two EU entries are indirect because the EU designates the entity, not the address. The OFAC entry’s listed_at and programs come from ofac_info.first_sanctioned_date and ofac_info.programs.

Lists Could Not Be Read

When a sanctions or blacklist store does not answer and no listing is found, the response still returns 200 with these fields:
is_ofac_sanctioned and is_token_blacklisted can read false in this case without the address being clean. Block or retry; do not allow.
Some examples below omit lists_checked, sanctions, and is_sanctioned, which every response also carries. Responses marked abbreviated omit some metadata and show only the first entry of token_status_summary, blacklist_event_history, and sanctions.

Multi-Provider Blacklisted Address

An OFAC-sanctioned address blacklisted by multiple stablecoin issuers, including Tether, Circle, Paxos, and Coinbase.
Response (abbreviated):

OFAC Sanctioned and Token Blacklisted

An address that is both OFAC sanctioned and token blacklisted by multiple providers.

OFAC Sanctioned and Token Blacklisted on Tron

A Tron address that is both OFAC sanctioned and blacklisted by Tether and Circle.
Response (abbreviated):

Solana Blacklisted Address

A Solana address blacklisted by Tether. Note the token_account field which is specific to Solana.

Previously Blacklisted (Now Unblacklisted)

An address that was blacklisted then unblacklisted. is_token_blacklisted is false but the full history is preserved.

Clean Address

An address with no sanctions or blacklist history.

Compatibility Parameter: include_details=false

include_details is accepted but ignored. Setting it to false still returns token status, event history, OFAC information, and attribution when available.
Response (abbreviated):

Errors


Case Auto-Creation

When the request uses a workspace-scoped key and case_auto_create is enabled in the workspace risk configuration, a hit opens a sanctions_screen case:
  • OFAC or an issuer blacklist: a severe case, always.
  • Any other government sanctions list: a case only when that list’s signal is enabled in the workspace’s attribution_signals, at the severity the workspace configured for it. When the address is on several such lists, the case takes the highest configured severity.
  • Israel NBCTF and FBI IC3 entries: no case, since they do not set is_sanctioned.

Best Practices

  • Gate on the right flags: For sanctions screening across every government list, check is_sanctioned and is_token_blacklisted. Check is_ofac_sanctioned only when a policy is OFAC-specific.
  • Fail closed: Treat lists_checked: false or is_sanctioned: null as unknown, not clean. Block or retry.
  • Decide on indirect listings: Use sanctions[].basis to route indirect entries to review if your policy treats Range attribution differently from a list naming the address.
  • Real-time checks: Blacklist status can change; avoid caching for high-risk use cases.
  • Read available details: Event history is returned when available; include_details does not change the response.
  • Addresses are case-insensitive: Both 0x1DA5... and 0x1da5... return identical results.

Use Cases

  • Pre-transaction screening: Check counterparty addresses before processing payments or transfers.
  • Exchange compliance: Screen addresses during deposit/withdrawal flows.
  • DeFi integration: Add sanctions checks to smart contract interactions or front-ends.
  • Audit trails: Generate compliance reports with full event history.

Authorizations

X-API-KEY
string
header
required

Authorization method required to allow user to access the api endpoints.

Path Parameters

address
string
required

Blockchain address to check (EVM, Solana, or Tron format)

Example:

"0x1da5821544e25c636c1417ba96ade4cf6d2f9b5a"

Query Parameters

network
enum<string>

Does not narrow the check: the address is looked up across every network, so an EVM address frozen on any network is flagged. Only echoed in the response network when the address has no record.

Available options:
ethereum,
tron,
solana,
base,
arbitrum,
optimism,
polygon,
avalanche
include_details
boolean
default:true

Include detailed event history and attribution (default: true)

Response

200 - application/json

Blacklist and sanctions check result

address
string
required

The queried blockchain address

Example:

"0x1da5821544e25c636c1417ba96ade4cf6d2f9b5a"

network
string | null
required

Network filter applied (null if all networks checked)

Example:

"ethereum"

is_token_blacklisted
boolean
required

Whether address is currently blacklisted by any token issuer

Example:

true

is_ofac_sanctioned
boolean
required

Whether address is on OFAC sanctions list

Example:

false

checked_at
string
required

UTC timestamp when check was performed (ISO 8601)

Example:

"2025-11-28T12:53:24Z"

is_sanctioned
boolean | null

Whether the address is on any government sanctions list: OFAC, UK, EU, EU Russia packages, France, Japan. Israeli NBCTF seizure orders and FBI IC3 advisories appear in sanctions but do not set this. Indirect designations count (see sanctions[].basis). null when a list could not be read (lists_checked: false) and none was found: treat it as unknown, not as clean.

Example:

true

lists_checked
boolean

Whether every sanctions and blacklist store answered. false means the result may be incomplete: a caller gating on it should fail closed or retry.

Example:

true

sanctions
object[]

Every list the address is on, one entry per list, including OFAC (empty when none)

token_status_summary
object[] | null

Current blacklist status per token and network (when include_details=true)

blacklist_event_history
object[] | null

Chronological list of blacklist/unblacklist events (when include_details=true)

ofac_info
object | null

OFAC sanction details (when sanctioned)

attribution
object | null

Known attribution/label for the address

Last modified on October 8, 2026