Check up to 10 crypto addresses against OFAC’s SDN data.
Paste a small batch. Get a dated exact-match result for each address. No wallet connection, account or payment.
Free batch check
A non-match is not sanctions clearance. OFAC says its listed digital-currency addresses are not exhaustive. This check does not assess ownership, the 50 Percent Rule, transaction exposure, geography or other sanctions lists. OFAC FAQ 562 · Ownership guidance.
What is checked?
The address is compared with digital-currency address fields in our existing OFAC SDN snapshot. EVM addresses compare without letter case; other identifiers compare exactly.
The result shows when our snapshot was built. Checks stop if it is missing or older than 26 hours. This timestamp is not OFAC’s publication time.
Screen thousands via the API or Apify Actor
Automate larger lists in bounded requests or jobs. Each request has its own limits; the free page accepts at most 10 addresses.
Sanctions Screener on Apify supports bounded address batches at its displayed Store price.
Payee Screening API adds name and domain signals. The free address-only route below needs no x402 payment.
Use the free API
Submit addresses with 1–10 items in a JSON body. The existing single address format also works. No wallet, key, trial parameter or payment header. The example is the public Base USDC contract identifier, not a recommendation or a stored result.
curl -i https://api.spendpreflight.com/v1/ofac-address-check \
-H 'Content-Type: application/json' \
-d '{"addresses":["0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913"]}'200 returns ordered results and a count for a batch. Each row reports address_match, match details when present, snapshot_built_at, source and scope. 400 means invalid input, 429 means temporarily busy, and 503 means no fresh determination is available. Never treat an error as a non-match. GET/HEAD do not screen. Empty batches, more than 10 items, any malformed address or extra fields reject the whole request without a determination. Duplicates remain separate rows in input order. The shared per-instance abuse limit is best effort, not a distributed per-user quota.
Privacy and review
Our service processes the addresses in memory against an existing snapshot. This route does not write queried addresses or results, call a blockchain, look up wallet ownership or create a public report. The form sends addresses in a POST body rather than a URL. Shared transient request counters contain no caller identity. Normal infrastructure policies still apply. Full privacy policy.
Informational screening, not legal advice or a compliance certification. Review possible matches against official records. How to screen a crypto address against OFAC (free and API) → · Official OFAC search.