Free OFAC Search: How to Check a Name for Free

A free OFAC search sounds like it should be simple: type a name, get an answer. In practice, "free" and "OFAC search" don't always mean the same thing depending on where you look — raw government data downloads are free but nearly unusable without engineering effort, while a proper ad-hoc screening tool can give you a real, readable result in seconds at no cost. This guide covers what a genuine free OFAC search actually gets you, where the free-tier limits sit, and when you'll outgrow it.

TL;DR

• A free, no-login OFAC search that checks the SDN list, Consolidated list and UN Security Council list in one go is available at Screen100's free screen.
• Downloading OFAC's raw XML or CSV files is also free, but it hands you a static dataset with no fuzzy matching, no scoring, and no built-in way to handle aliases.
• A single free check is enough for a one-off vetting decision. Recurring customers, large name lists, audit requirements and programmatic access all need more than an ad-hoc search.
• Screen100's free tier is genuinely useful but rate-limited; higher-volume and automated use sits on the Pro plan.

Is there a free way to check the OFAC sanctions list?

Yes — and it's worth separating two things that both get called "free OFAC search" but behave very differently. The first is the US Treasury's own published data: OFAC makes its Specially Designated Nationals (SDN) list and Consolidated (Non-SDN) list available for public download in XML, CSV and fixed-field formats through its Sanctions List Service. That data is free in the sense that nobody charges you to download it. The second is a screening tool built on top of that data — one that takes a name, runs fuzzy matching against every list entry and alias, and hands you back a scored result. Screen100's free screen is this second kind: no login, no account, no card details, just a name in and a readable answer out.

Why the raw OFAC data files aren't a practical free option

Treasury's own documentation is candid about the shape of this data: the SDN list is published as XML, fixed-field and delimited files intended to be imported into other software, and a complete relational picture requires linking multiple files together. That's a reasonable design for compliance vendors and software teams building their own systems — it's a poor fit for someone who just needs to check one name today. There's no search box, no fuzzy matching for a misspelt name or transliterated alias, and no score to tell you whether "Mohammed Al-Rashid" is a strong hit against "Mohamed Al Rasheed" or an unrelated coincidence. Treasury does also run its own Sanctions List Search web tool, which does apply fuzzy logic across the SDN and Non-SDN Consolidated lists — a reasonable free option in its own right, though it doesn't cover the UN Security Council list or give you a downloadable audit record of the search.

A compliance practitioner who reviews vendor onboarding for a mid-sized firm put it plainly in a conversation about tooling choices: "The government list is authoritative, but it was never built to be searched by a person under time pressure — it was built to be downloaded and processed." That's the gap a proper screening tool closes: same underlying data, but with matching logic, a legible result, and a record of what you checked and when.

What does a free OFAC search actually get you?

With Screen100's free ad-hoc screen, one search covers the OFAC SDN list, the OFAC Consolidated list and the UN Security Council Consolidated list simultaneously — not just the SDN list alone, which is the most common gap in a manual check. You type the full legal name, optionally add date of birth, nationality or entity type, and get back a result in one of three bands: Clear, Possible match, or Match, each backed by the specific listed entry it scored against. No account is required for a single check, which makes it a genuinely fast option when you need an answer right now rather than after setting up a login.

A quick example

Picture a freelance designer who's just been approached by a new client based overseas, offering a decent-sized project and asking for an invoice before any contract is signed. Nothing about the request looks unusual, but the client is unfamiliar and the payment is coming from an account in a jurisdiction the designer hasn't dealt with before. Rather than either refusing the work out of caution or invoicing blind, they run the client's full legal name through a free OFAC search first. It takes under a minute, the result comes back Clear, and they proceed with the invoice — with a screenshot of the result saved in case anyone ever asks why they felt comfortable taking the job. That's the realistic use case for a free ad-hoc check: a one-off decision, made quickly, with no ongoing relationship to track yet.

When is a free ad-hoc check enough — and when do you need more?

A single free search is the right tool when you have one name, one moment in time, and no ongoing obligation to keep checking. It stops being enough once any of three things becomes true: the relationship persists past that first check, you have more than a handful of names to screen at once, or someone downstream — a regulator, an auditor, a client — needs proof of what you screened and when.

Option	Best for	Limitation
Free ad-hoc check (/screen)	A single name, a one-off decision, right now	No memory between checks; not built for repeat re-screening
Batch screening	Many names at once — a supplier list, a portfolio, a new customer cohort	Still a point-in-time snapshot unless paired with monitoring
Ongoing monitoring	Recurring customers or vendors who need re-screening as lists update	Needs the subject saved and tracked, not just searched once
API / audit certificates	Programmatic access, or proof of a screen for compliance records	Metered usage; free tier has volume limits

How do I decide which one I need?

If you're vetting one counterparty before a single transaction, the free check genuinely is the right answer — use it and move on. If you're bringing on a batch of new accounts, or you review a supplier list quarterly, batch screening saves you from running the same search dozens of times by hand. If the relationship is ongoing — a customer who'll keep transacting with you, a vendor on a retainer — that's what ongoing monitoring exists for, since a name that clears today can be designated next month and a one-time check won't catch that. And if you need to hand a screening result to an auditor, insurer or client as proof of due diligence, an audit certificate gives you a timestamped, referenceable record rather than a screenshot. Programmatic access to any of this, including from AI agents and automated workflows, runs through the API.

It's worth being upfront here: Screen100's free tier is designed to be genuinely useful, not a crippled trial. But it is a free tier, with sensible rate limits on ad-hoc use, and it isn't built for high-volume batch runs or unattended automation — that's what the Pro plan is for. If your need is a handful of one-off checks, you shouldn't need to pay for anything.

Getting the most out of a free search

A few habits make a free OFAC search more reliable rather than just faster:

• Use the subject's full legal name, not initials or a nickname — partial names produce noisier results.
• Add date of birth or nationality if you have it; these are what let you rule out a same-name coincidence when a possible match comes back.
• Treat a Clear result as accurate as of the moment you ran it, not permanently — lists update regularly, which is exactly why ongoing relationships need monitoring rather than a single check.
• Save the result if you might need to justify the decision later, even informally.

A free OFAC search covers more ground than most people expect — a real match against three lists, in seconds, with no account required — but it's still a snapshot, not a system. For a one-off name, that's exactly enough. For anything recurring, start with the fundamentals in how to do an OFAC check, then look at whether monitoring or the API fits how your checks actually happen.