Skip to content
FonteumPublic-records evidence
Screen 25 NPIs free →Buy $129 certificate →

AI summary

List-based sanctions

What are list-based sanctions?

List-based sanctions apply restrictions because a party or item appears on a named sanctions list, unlike broader country, sector, or activity rules. Fonteum's ofac-sdn-composition-2026.json file, generated 2026-07-14 from a 2026-06-28 source snapshot, contains

20,055Source: U.S. Department of the Treasury, Office of Foreign Assets Control — OFAC SDN composition snapshot · As of 2026-06-28
SDN listing rows. Coverage is limited to that source and date, and fuzzy name similarity is inconclusive.

Published
2026-07-21
Retrieved
Not reported
Snapshot
sha256:81e6e47a7505a0663cc29926931b7c96442b02613420cd2097b92c9096c97ca9
Data as of
2026-06-28

Source artifact receipts

Each receipt below describes its exact retained artifact or live source. Dates and digests never cross artifact boundaries.

OFAC SDN composition snapshot

Evidence publisher: U.S. Department of the Treasury, Office of Foreign Assets Control. Source date: 2026-06-28.

Published
2026-07-14
Retrieved
Not reported
Snapshot
sha256:a361676e0715f46f7a8f165f3d2e41688d885d93254c3f74595139b1ad71f020
Data as of
2026-06-28

Retained artifact creator: Fonteum LLC. Generated 2026-07-14. Based on: OFAC SDN composition snapshot by U.S. Department of the Treasury, Office of Foreign Assets Control.

Scope and material limitation

What this answer covers

This answer explains the list-based concept with a dated OFAC example. It does not state that all sanctions are list-based or resolve a possible match.

Dated source facts

What the cited record says

Source-snapshot manifest receipt

Reproducible lineage, explicitly unsigned

This receipt attests the source snapshot manifest, not any individual fact.

The answer-series chain record is unsigned. It does not authenticate a person, organization, eligibility state, or individual fact.

Snapshot manifest SHA-256
0541c19a0f4923f9f6f279e30931150be8541bf13e17cd5d4a4f0c1baaf161a8
Previous chain SHA-256
b1489274a42a67fab20086dfff388b5b28824113d9750897105f09e054d455f0
Current chain SHA-256
1e28c0382a6ee3bda83b862569007c2b652eb487df9d03bdc6b4ff23dae8ac0e
signature_linked_facts
0
Answer-series chain status
unsigned
Inspect integrity recordPrevious chain recordNext chain record

Primary-source chain

Follow the answer to its source

  1. OFAC SDN composition snapshotU.S. Department of the Treasury, Office of Foreign Assets ControlSnapshot:

    Limitation: The retained aggregate covers OFAC SDN listing rows only. Rows are not unique identities, program counts can overlap, and a similar name is not an identity or legal conclusion.

  2. Introduction to OFACU.S. Department of the Treasury, Office of Foreign Assets ControlAccessed:

    Limitation: This guidance explains OFAC's sanctions-program framework. It is not a complete list export, transaction-specific legal advice, or an identity-match decision.

Re-derive this answer from the named source and dated scope; no Fonteum account is required.

Methodology and limitations

How to interpret this answer

Methodology version: citation-answer/v1

  • The example projection covers the named OFAC material only.
  • This aggregate public-record answer is not a consumer report, person-level dossier, eligibility decision, or risk score.
Read the methodology

Frequently asked questions

Questions about this answer

Are all sanctions list-based?
No. Some restrictions apply by country, sector, activity, or transaction even without a named-party list entry.
Is a fuzzy name match conclusive?
No. It requires identifier and source-program review.

What’s on file, by the numbers

Platform snapshot · 2026-07-26

13.4Mproviders & companiesProviders, organizations, owners, and facilities on file
26.2Msource-linked factsSource-linked field facts in the dated platform snapshot
90sources with dataDistinct snapshot source IDs with at least one positive record count
79fresh sourcesDistinct source IDs whose latest positive-data snapshot falls within the preceding 45 days
111sources integratedActive registry rows; integration does not establish a load
13state Medicaid jurisdictionsDistinct states represented in the state-exclusions serving table

Integrated, with-data, and fresh-observation counts are separate. No platform-wide source-completeness count is published. Completeness is source-specific and must be evaluated against the named source's expected scope. State coverage is a separate jurisdiction measure.

Source authority is record-specific

Use the issuer named on the record.

Fonteum spans federal, state, and global public publishers. A source page or returned record identifies its issuer and dataset where that metadata is available. A platform registry count does not assign every page to one authority or establish loaded, fresh, or complete coverage.

Browse source records and their stated limitations →

Reproducible by design

Inspect the evidence each published figure actually supplies.

Source and date

Research pages expose the named public file and observation date where those fields are available. Source-file SHA-256 coverage is separate; facts do not currently link deterministically to signatures.

Available derivation

Studies with a retained release and committed derivation link the SQL or method used. Other studies state the evidence and reproduction limits they actually have.

Daily observations

Dated table row-count observations can detect local drift. They do not imply that an upstream publisher released or Fonteum ingested new data that day.

Named medical review

Reviewed by Jennifer Montecillo, MD, medical reviewer. Non-practicing medical reviewer.

Read the full provenance and attestation methodology →

Request access