How to use OFAC's Sanctions List Search, field by field
OFAC's Sanctions List Search is Treasury's free tool for checking a name against the SDN list and OFAC's Consolidated (non-SDN) list (OFAC FAQ 369). Enter the name, leave the type as "All" unless you know it, lower the minimum name score below 100 so near spellings appear, and run the search. Each result shows its list, program and a score; a lower score is a looser match. It is built for individual users checking names one at a time (OFAC FAQ 287).
Where it is
The tool is at sanctionssearch.ofac.treas.gov. OFAC also links to it from the Sanctions List Service.
The fields
The search form has these inputs:
| Field | What it does |
|---|---|
| Type | All, Aircraft, Entity, Individual or Vessel |
| Name | The only field that uses fuzzy matching |
| ID # / Digital Currency Address | Passport, registration or other ID numbers, and crypto addresses |
| Address, City, State/Province, Country | Narrow results by location |
| Program | Limit to one sanctions program code, such as SDGT or RUSSIA-EO14024 |
| List | Limit to one list |
| Minimum Name Score | The slider that sets how close a name must be to appear |
OFAC says only the name field uses fuzzy logic; the other fields use character matching (OFAC FAQ 246). So a misspelled city will not find the record, but a misspelled name often will.
The minimum name score
The slider defaults to 100, which means exact match (OFAC FAQ 247). At 100 the tool returns only names whose characters exactly match what you typed. At 50 it returns every name it judges at least 50 percent similar (OFAC FAQ 248). Lowering the threshold widens the results.
The score combines a character-similarity algorithm (Jaro-Winkler) and a phonetic one (Soundex), comparing both the full name and its parts (OFAC FAQ 249). OFAC added a further algorithm when it upgraded the tool on 25 January 2021, so results can differ from older tests (OFAC FAQ 892).
OFAC does not recommend a threshold. Each search has its own facts, and users must set thresholds from their own risk assessment and compliance practices (OFAC FAQ 250). Whatever you choose, write it into your procedure so every check uses the same setting.
Reading the results
Each row shows the name, address, type, program(s), list and score. The tool's own page asks users to pay close attention to the program codes, because they indicate how a true hit should be treated (Sanctions List Search).
A result is a possible match, not a finding. Compare the full entry with what you know about your party: full name, date of birth, nationality, address, identification numbers. Our guide to clearing an OFAC false positive has a reason template.
Which lists it covers
The tool searches the SDN list and OFAC's Consolidated non-SDN lists together, and the List column shows which list each result is on (OFAC FAQ 369). It does not search Commerce's Entity List or Denied Persons List; those are on Trade.gov's Consolidated Screening List. See SDN, Consolidated and the CSL.
What it does not do
- No history. It always reflects the current lists. Removed names and earlier versions of updated entries do not appear (OFAC FAQ 467).
- No record of your search. Nothing is saved, so the proof is whatever you capture yourself. See OFAC license vs OFAC clearance for what a usable record contains.
- No automation. OFAC says the tool should not be used by automated systems running continual searches. For machine use it points to the downloadable XML, CSV and other data files (OFAC FAQ 287). See where to download the SDN list.
- No monitoring. It will not tell you when a customer or vendor you checked last month is added later. See how often to re-screen.
The page itself says using it is not a substitute for appropriate due diligence and does not limit liability (Sanctions List Search).
When it is the right tool
Treasury's search is a good fit for a handful of one-off checks where you capture the result yourself. Once you are screening a customer or vendor list, need a stored record per check, or need to know when a listed name changes, you need batch screening and monitoring on top of the same official data.
This is screening data, not legal advice.
Run a free OFAC check against the same SDN and Consolidated lists, with the match explained and the list publication date shown.