Sanctions and Blacklist Check
Check if a blockchain address is blacklisted by stablecoin issuers or listed on OFAC sanctions list.
Check if a blockchain address is blacklisted by token issuers (e.g. Tether, Circle, Coinbase, Paxos) or sanctioned by the US Treasury’s Office of Foreign Assets Control (OFAC). See Understanding Risk Scores for how this fits into Range’s broader risk methodology.Documentation Index
Fetch the complete documentation index at: https://docs.range.org/llms.txt
Use this file to discover all available pages before exploring further.
- Token Blacklist Events — Real-time monitoring on Ethereum, Tron, and Solana for specific stablecoin issuers.
- OFAC Sanctions — Sourced from official OFAC reports and covers any network published by OFAC.
How It Works
The endpoint performs two types of checks:-
Token Blacklist Check — Monitors on-chain blacklist events emitted by stablecoin issuer contracts on Ethereum, Tron, and Solana. When issuers like Tether or Circle blacklist an address, it is blocked from transferring their tokens. The endpoint tracks both
blacklistandunblacklistevents in real-time to determine the current status. - 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.
- 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 on-chain events.
Note: Theis_token_blacklistedfield reflects the current status based on the most recent event. An address that was blacklisted and later unblacklisted will showfalse. Useblacklist_event_historyto view the complete history.
Path Parameters
| Name | Type | Required | Description |
|---|---|---|---|
| address | string | ✅ | Blockchain address to check |
Query Parameters
| Name | Type | Required | Default | Description |
|---|---|---|---|---|
| network | string | ❌ | all | Filter blacklist events by network |
| include_details | boolean | ❌ | true | Include event history, token status breakdown, and attribution |
Recommendation: In general, we do not recommend using thenetworkparameter. Omitting it ensures comprehensive screening across all networks for both blacklist events and OFAC sanctions. Only use thenetworkparameter if you have a specific use case, such as:
- Limiting the search to a specific network for performance reasons
- Checking an address format that exists on multiple networks (e.g., EVM addresses on Ethereum vs other EVM-compatible chains)
OFAC Sanctions Coverage
OFAC sanctions data is sourced from official US Treasury reports and is network-agnostic. If an address appears in OFAC publications, we flag it across all 300+ networks we support. See Supported Chains for full coverage.Supported Networks & Tokens (Blacklist Events)
Real-time blacklist event monitoring is available for the following stablecoin issuers:| Network | USDT (Tether) | USDC (Circle) | CBBTC (Coinbase) | USDP (Paxos) |
|---|---|---|---|---|
| Ethereum | ✅ | ✅ | ✅ | ✅ |
| Tron | ✅ | ✅ | — | — |
| Solana | ✅ | ✅ | — | — |
Response Schema
The response contains the sanctions and blacklist status for the queried address.Top-Level Fields
| Field | Type | Description |
|---|---|---|
address | string | The blockchain address that was checked. |
network | string | null | The network filter applied. Returns null if all networks were checked. |
is_token_blacklisted | boolean | true if the address is currently blacklisted by any stablecoin issuer. |
is_ofac_sanctioned | boolean | true if the address appears on the OFAC sanctions list. |
checked_at | string | Timestamp (ISO 8601) when this check was performed. |
token_status_summary | array | null | Breakdown of blacklist status per token. null when include_details=false or no blacklist data exists. |
blacklist_event_history | array | null | Chronological list of on-chain blacklist/unblacklist events. null when include_details=false or no events exist. |
ofac_info | object | null | Details about the OFAC sanction. null if not sanctioned. |
attribution | object | null | Additional labels and context for the address. null when include_details=false or no attribution exists. |
Token Status Summary
Shows the current blacklist status for each token that has flagged this address.| Field | Type | Description |
|---|---|---|
token | string | Token symbol: USDT, USDC, CBBTC, or USDP. |
issuer | string | The company that issued the token: Tether, Circle, Coinbase, or Paxos. |
is_currently_blacklisted | boolean | true if the address is currently blocked from using this token. |
first_blacklisted_date | string | When the address was first blacklisted for this token (YYYY-MM-DD). |
last_event_date | string | Date of the most recent blacklist or unblacklist event. |
last_event_type | string | Either blacklist or unblacklist. Determines current status. |
Blacklist Event History
A chronological record of all on-chain blacklist and unblacklist events.| Field | Type | Description |
|---|---|---|
event_type | string | blacklist (address blocked) or unblacklist (address unblocked). |
token | string | Token symbol. |
issuer | string | Token issuer. |
network | string | Blockchain where the event occurred: ethereum, tron, or solana. |
date | string | Event date (YYYY-MM-DD). |
block_number | integer | Block number of the transaction. |
block_timestamp | string | Timestamp of the block. |
transaction_hash | string | On-chain transaction hash for verification. |
token_account | string | null | The token account address (Solana only). null for EVM chains. |
OFAC Info
Details about OFAC sanctions. Only present when the address is sanctioned.| Field | Type | Description |
|---|---|---|
is_sanctioned | boolean | Always true when this object is present. |
name_tag | string | Name of the sanctioned individual or entity. |
category | string | Sanction category (e.g., “OFAC Sanctioned”). |
entity | string | Sanctioning body (e.g., “OFAC”). |
address_role | string | Individual or Entity. |
first_sanctioned_date | string | Date when the address was first sanctioned (YYYY-MM-DD). |
sanction_url | string | Link to the official OFAC announcement. |
Attribution
Additional context and labels for the address, which may include information beyond on-chain events.| Field | Type | Description |
|---|---|---|
name | string | Human-readable name or label for the address. |
category | string | Category (e.g., “USDT Blacklist”, “Multi-Provider Blacklist”). |
role | string | Role description (e.g., “Blacklisted Address”). |
entity | string | null | Associated entity, if known. |
tags | array | null | List of tags (e.g., ["BLACKLISTED", "COMPLIANCE"]). |
malicious | boolean | true if the address is considered malicious. |
Examples
Multi-Provider Blacklisted Address
An address blacklisted by multiple stablecoin issuers (USDT, USDC, USDP, CBBTC) on Ethereum.OFAC Sanctioned and Token Blacklisted
An address that is both OFAC sanctioned and token blacklisted by multiple providers.OFAC Sanctioned Only
A Tron address that is OFAC sanctioned but not token blacklisted.Solana Blacklisted Address
A Solana address blacklisted by Tether. Note thetoken_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.Minimal Response
Useinclude_details=false for high-volume screening when you only need pass/fail results.
Errors
| HTTP Code | Cause | Recommended Action |
|---|---|---|
| 400 | Invalid address format | Validate the address format before making the request |
| 429 | Rate limit exceeded | Implement exponential backoff and retry |
| 5xx | Internal server error | Retry after a short delay; contact support if persists |
Best Practices
- Check both flags — Always check both
is_token_blacklistedandis_ofac_sanctionedfor comprehensive compliance screening. - Real-time checks — Blacklist status can change; avoid caching for high-risk use cases.
- Use full details — Keep
include_details=true(default) when you need event history. - Addresses are case-insensitive — Both
0x1DA5...and0x1da5...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
Use Authorization: Bearer
Path Parameters
Blockchain address to check (EVM, Solana, or Tron format)
"0x1da5821544e25c636c1417ba96ade4cf6d2f9b5a"
Query Parameters
Filter by blockchain network. If omitted, checks all networks.
ethereum, tron, solana Include detailed event history and attribution (default: true)
Response
Blacklist and sanctions check result
The queried blockchain address
"0x1da5821544e25c636c1417ba96ade4cf6d2f9b5a"
Network filter applied (null if all networks checked)
"ethereum"
Whether address is currently blacklisted by any token issuer
true
Whether address is on OFAC sanctions list
false
UTC timestamp when check was performed (ISO 8601)
"2025-11-28T12:53:24Z"
Current blacklist status per token (when include_details=true)
Chronological list of blacklist/unblacklist events (when include_details=true)
OFAC sanction details (when sanctioned)
Known attribution/label for the address

