Pro Tier Module

OFAC Sanctions Screening - SDN list (keyless, local match)

Screen a name against the OFAC SDN list locally and keylessly - a match is a lead, not a finding.

See it run - a worked example, 100% in this browser tab

The problem

Sanctions screening against the OFAC SDN list often means paid services or live API keys, and a screen is only useful if you know exactly how fresh the list is and that a hit is a lead, not a verdict.

The local-first solution

A keyless, deterministic screen matches your query locally against a cached Treasury SDN snapshot through the GDBS server proxy, returning scored matches with the snapshot's as-of date shown prominently and no per-query call to OFAC.

What it does

Local name/entity match against the U.S. Treasury OFAC SDN list
0-to-1 match score from token overlap and substring containment, no AI
OFAC program tags (for example SDGT, IRAN, RUSSIA-EO14024) on each hit
Entry type (Individual, Entity, Vessel, Aircraft) and SDN list-entry id
Snapshot as-of date shown prominently so you know the freshness
Bindable in Worklog to screen a party automatically on matter intake

Honest scope

Keyless and local against a cached snapshot that can lag the live list, so confirm against live OFAC at the time of a decision. A match is a lead requiring human review, not a finding that a party is sanctioned, and a non-match is not a legal clearance - the SDN list is only one of several OFAC lists. No AI, no legal advice.

Authorities cited

Screen the name

Run the SDN screen in your browser and attach the dated, scored matches to a Worklog case. You supply no key, and the match runs locally rather than as a live OFAC query.

Try it live inside GDBS Open a free Standard account
GDBS by VaultSync Solutions Inc. - Verifiable Computation. gdbs.getvaultsync.com