Global sanctions lists: an official-source directory and guide

Use a directory to understand scope, not to count names

A sanctions-list directory should identify the authority, jurisdiction, source purpose, official publication, and product availability. Several lists can overlap, and multiple aliases or records can refer to one identity. A total record count is not a count of unique sanctioned people.

SanctionsKit’s datasets directory and source coverage pages provide the existing source-oriented navigation. This guide explains how to use the official resources without treating every source as equivalent or supported.

United States: OFAC and trade-screening sources

OFAC’s Sanctions List Service distributes SDN and Non-SDN data. Preserve the underlying list and program because the restrictions differ. SanctionsKit’s documented selectors include `ofac-sdn` and `ofac-non-sdn`.

The Commerce Consolidated Screening List combines U.S. government sources with different trade-related requirements. The documented `us-csl` selector is not a synonym for OFAC SDN. Read the export-control coverage notes before interpreting candidates.

United Kingdom: use the current UK Sanctions List

The UK Sanctions List is the current government source. The former OFSI Consolidated List was retired on 28 January 2026. Older articles and integrations may still use the legacy terminology.

SanctionsKit’s documented current selector is `uk-sanctions`. Review the original designation and measures; do not assume that an old feed URL or an OFSI label represents the current source.

European Union and United Nations: distinguish reference coverage

The European Commission financial sanctions database and EU data portal entry are official starting points for consolidated financial sanctions data. The UN Security Council Consolidated List preserves committee and regime context.

In this content catalog, EU and UN sources are reference-only rather than supported SanctionsKit screening selectors. Check EU coverage and UN coverage before designing an integration. The developer guides for these sources describe local official-file validation, not invented SanctionsKit endpoints.

Canada and Australia: read the source-specific limits

Canada’s Consolidated Canadian Autonomous Sanctions List covers the stated autonomous-sanctions scope. It is administrative, not itself the law, and is not a complete substitute for all Canadian sanctions regulations. SanctionsKit documents `ca-autonomous`.

Australia’s DFAT Consolidated List is the official starting point for listed persons and entities under its scope. SanctionsKit documents `au-consolidated`. Preserve source references and aliases when comparing records.

Maintain a coverage register

For every source your policy needs, record its purpose, legal scope, official URL, supported entity types, availability, active version, limitations, and owner. Treat a required source marked unavailable or reference-only as a coverage gap to resolve, not permission to silently omit it.

Do not add unsupported list identifiers to the API. Use source documentation, the data-freshness guide, and the official publications together.