Category: Sanctions Lists and Screening

Specially Designated Nationals (SDN) List

Also known as: SDN List, Specially Designated Nationals and Blocked Persons List, SDN and Blocked Persons List, OFAC SDN List

Simply put

The SDN List is a list published by the U.S. Treasury's Office of Foreign Assets Control (OFAC) that names individuals, companies, and groups that the United States has designated under its sanctions programs. It also captures parties owned or controlled by, or acting for or on behalf of, those designated persons. Its purpose is to advance U.S. national security and foreign policy goals by financially isolating and constraining the listed parties.

Formal definition

The Specially Designated Nationals and Blocked Persons List is a consolidated list maintained and published by OFAC identifying individuals, entities, and groups designated under OFAC-administered sanctions authorities, together with parties that are owned or controlled by, or acting for or on behalf of, such designated persons. Assets and interests in property of listed parties within U.S. jurisdiction are generally subject to blocking, and U.S. persons are typically prohibited from dealing with them, though the precise scope of prohibitions and any applicable exemptions or general licenses depends on the specific sanctions program under which a party is designated; practitioners should confirm program-specific requirements against the governing OFAC regulations. The list is disseminated by OFAC in multiple machine-readable formats (including XML and fixed-field/delimited files) to support automated sanctions screening. Inclusion on the list reflects a regulatory designation for sanctions purposes and should not be conflated with a finding of criminal wrongdoing.

Why it matters

The SDN List is one of the most consequential sanctions lists in global compliance because of the breadth of U.S. jurisdictional reach and the severity of the prohibitions attached to designation. Assets and interests in property of listed parties within U.S. jurisdiction are generally subject to blocking, and U.S. persons are typically prohibited from dealing with them. For financial institutions, this means that a failure to identify an SDN in a customer relationship or transaction can result in the processing of prohibited dealings, exposing the institution to enforcement action and reputational harm. Because the precise scope of prohibitions and any applicable exemptions or general licenses depends on the specific sanctions program under which a party is designated, screening against the list is only the starting point, understanding the governing program is essential.

The list's reach extends beyond the parties explicitly named. It also captures parties that are owned or controlled by, or acting for or on behalf of, designated persons, meaning compliance teams cannot rely solely on a literal name match to identify exposure. This creates operational complexity, as institutions must consider ownership and control relationships that may not appear on the face of a transaction. OFAC's dissemination of the list in machine-readable formats such as XML and fixed-field/delimited files exists precisely to support the automated screening programs that most obliged entities depend upon to manage this exposure at scale.

It is important to keep the regulatory character of the list in perspective. Inclusion on the SDN List reflects a regulatory designation for sanctions purposes and should not be conflated with a finding of criminal wrongdoing. A screening match likewise does not by itself establish that a customer is a designated party; matches must be reviewed and resolved before any action is taken. Compliance professionals should treat the list as an authoritative regulatory instrument for identifying prohibited or restricted dealings, not as evidence of criminal conduct by any listed or matched party.

Who it's relevant to

Sanctions and financial crime compliance teams

These teams are responsible for configuring and maintaining screening systems that compare customers, counterparties, and transactions against the SDN List. They typically ingest OFAC's machine-readable files, tune matching logic, and manage the review and resolution of potential matches. They must also account for parties owned or controlled by, or acting for or on behalf of, designated persons, which may not appear as direct name matches.

U.S. persons and institutions within U.S. jurisdiction

U.S. persons are generally prohibited from dealing with listed parties, and assets and interests in property of listed parties within U.S. jurisdiction are typically subject to blocking. Financial institutions, corporations, and other entities that fall within U.S. jurisdiction rely on the list to identify and avoid prohibited dealings, though the precise obligations depend on the applicable sanctions program.

Legal and regulatory advisors

Sanctions lawyers and compliance advisors are relied upon to interpret the program-specific requirements that govern each designation. Because prohibitions, exemptions, and general licenses vary by program, advisors help institutions confirm the governing OFAC regulations, assess ownership and control questions, and distinguish a regulatory designation from any implication of criminal wrongdoing.

Investigators and financial intelligence analysts

Analysts use the SDN List as a reference point when reviewing customer relationships, transaction patterns, and potential exposure to designated parties. They should treat a designation or a screening match as a basis for further review rather than as proof of criminal conduct, and resolve potential matches before drawing conclusions.

Inside SDN List

Designated Individuals and Entities

The SDN List, maintained by the US Treasury's Office of Foreign Assets Control (OFAC), identifies individuals, companies, and organizations that have been designated under various US sanctions programs. Designations may arise from country-based programs or list-based (targeted) programs such as those addressing terrorism, narcotics trafficking, or proliferation.

Blocking Obligation

US persons are generally prohibited from dealing with SDNs, and property or property interests of SDNs that come within the possession or control of US persons must typically be blocked (frozen) and reported to OFAC. The precise obligations depend on the applicable sanctions program and authority.

Identifying Information

Entries typically include identifying details such as names, known aliases (a.k.a.), addresses, dates of birth, identification or passport numbers, and other data intended to help distinguish a listed party from similarly named persons who are not designated.

50 Percent Rule Consideration

Under OFAC guidance, entities owned 50 percent or more, in the aggregate, by one or more blocked persons are generally considered blocked even if not separately named on the SDN List. Practitioners should confirm the current application of this guidance against OFAC's published materials.

Program Tags

Each SDN entry is generally associated with one or more sanctions program tags indicating the authority under which the party was designated, which can affect the scope and nature of the applicable prohibitions.

Common questions

Answers to the questions practitioners most commonly ask about SDN List.

Does appearing on the SDN List mean a person or entity has been criminally convicted?

No. Designation on the SDN List is an administrative action taken by OFAC under its sanctions authorities, not a criminal conviction or a finding of guilt in a court of law. Designation reflects that OFAC has determined the person or entity meets the criteria of one or more sanctions programs, but it is distinct from criminal due process. Treating an SDN designation as proof of criminal wrongdoing conflates an administrative sanctions listing with a criminal-law determination, which are separate concepts.

Is the SDN List the same as a global or universal sanctions list that all countries follow?

No. The SDN List is maintained by OFAC, a component of the US Treasury, and reflects US sanctions authorities. It is not a single global list, and other jurisdictions maintain their own designations, such as UK, EU, and UN sanctions lists, which may overlap but do not necessarily match. A party on the SDN List may not appear on other regimes' lists, and vice versa. Obliged entities should not assume that screening against the SDN List alone satisfies sanctions obligations under other applicable regimes; the relevant lists depend on the jurisdictions and nexus applicable to the institution.

Which lists should we screen against in addition to the SDN List?

The lists an institution screens against generally depend on its jurisdictional exposure and the sanctions regimes to which it is subject. In addition to OFAC's SDN List, institutions may need to consider OFAC's other lists, such as its non-SDN consolidated lists, as well as UN, EU, UK (OFSI), and other national or regional lists relevant to their operations and customer base. The precise scope of required screening should be confirmed against the applicable regulations and the institution's own risk assessment rather than assumed to be limited to a single list.

How should we handle a potential match against the SDN List?

A screening alert typically indicates a possible name match, not confirmation that the customer or counterparty is the designated party. Institutions generally apply a review and escalation process to determine whether an alert is a true match or a false positive, considering identifying details beyond name alone. Where a true match is confirmed, obligations may include blocking or rejecting transactions and reporting as required under the applicable sanctions program. Because handling requirements and reporting timelines vary by regime, the specific procedures should be aligned with the applicable OFAC rules and the institution's sanctions policies. An unresolved or potential match, on its own, does not establish wrongdoing.

How often is the SDN List updated, and how should that affect our screening?

OFAC may add, amend, or remove entries from the SDN List at any time, and updates are not on a fixed periodic schedule. Because of this, screening controls are generally designed to use current list data, and many institutions implement processes to obtain and apply updates promptly and to rescreen existing customers and relationships against revised list content. The appropriate frequency and method should be determined by the institution's risk-based approach and confirmed against applicable regulatory expectations.

Does screening against the SDN List guarantee that we will not deal with a sanctioned party?

No. Screening against the SDN List is a control that helps detect and mitigate the risk of dealing with designated parties, but it does not guarantee prevention. Effectiveness can be affected by data quality, name variations, aliases, incomplete or manipulated identifying information, the timeliness of list updates, and the calibration of matching logic. Screening should be understood as one component of a broader, risk-based sanctions compliance program rather than a measure that eliminates sanctions risk.

Common misconceptions

The SDN List is the same as a PEP list, so screening against it covers politically exposed persons.

SDN screening (sanctions screening) and PEP screening are distinct activities. The SDN List identifies parties subject to US sanctions prohibitions, whereas PEP screening identifies individuals who hold or have held prominent public functions and who may warrant enhanced due diligence based on risk. Being a PEP is not itself a sanctions designation, and the two should not be treated as interchangeable.

A screening match against the SDN List proves that a customer is a criminal or has done something unlawful.

A screening hit is an operational alert indicating a potential name match that requires review and possible escalation; it does not by itself establish wrongdoing. Many alerts are false positives arising from similar names, and a designation itself reflects US sanctions policy rather than a criminal conviction of the listed party.

Screening the named SDN List alone is sufficient to satisfy US sanctions obligations.

The named list is not necessarily the full scope of prohibited dealings. Under OFAC guidance, entities owned 50 percent or more by blocked persons may be considered blocked even if not separately listed, and broader country-based or program-based restrictions may apply. Reliance solely on exact-name matches against the published list may leave residual risk.

Best practices

Screen customers and relevant transactions against the current SDN List and refresh screening when OFAC publishes updates, as designations and identifying details change over time.

Configure fuzzy or approximate matching to account for aliases, transliterations, and name variations, then apply a documented process to investigate and disposition alerts as true or false positives.

Incorporate consideration of the OFAC 50 percent rule into ownership analysis so that entities owned by blocked persons are addressed even where they are not separately named, confirming the current application against OFAC guidance.

Keep sanctions screening operationally distinct from PEP screening, using each for its intended purpose while recognizing that a single party could appear in both contexts.

Maintain audit-ready records of screening runs, list versions used, alert reviews, and escalation decisions to support regulatory examination and internal governance.

Establish clear escalation and blocking or rejecting procedures, and confirm reporting obligations to OFAC against the applicable sanctions authority before acting on a confirmed match.