Practical guide

How to Use Zhengdao’s Global Sanctions List Database (Without Treating a Match as a Transaction Decision)

Learn how to use Zhengdao’s global sanctions list database—a named-file match is not a transaction decision. Not legal advice.

Schematic: search across separate official list files — a match is not a transaction decision

When you open Zhengdao’s global sanctions list database, you are checking which record sits in a named official file now—not finishing a transaction decision. A match means that file contains the record; it does not decide whether a deal may proceed, and it does not merge two authorities into one person. Search runs in your browser. This page is workbench literacy only, not legal advice.

When you use the sanctions hub vs China lists vs one-box screening

You open the sanctions hub when your question sits inside the foreign official-file mirror: UN, US, UK, EU, Canada, Australia and Switzerland list files the site currently indexes. You open the China lists hub when you mainly need China export-control and countermeasure notices—start from Paste a name or email domain. Find the party behind it. and keep How to Screen a Counterparty on Zhengdao’s China Export-Control Lists (Without Over-Reading a Hit) for that walkthrough. You open counterparty list screening when you want one entry across China measures and the foreign files together—use Counterparty list screening as the live tool only; China’s measures stay in the entity-list database and are not merged into this sanctions surface.

You treat these as different moments. Sanctions answers “is this string in one of the named foreign files on this snapshot?” China lists answers a China-notice location question. One-box screening answers a first party pass across both datasets while keeping results separate. You do not collapse those jobs into one screenshot.

Scope of the 14 files and local-first search

You should treat the hub as a searchable mirror of 14 downloadable official files with 61,251 current records on the live page at draft time, with the snapshot assembled 2026-09-19 16:58:23 (UTC+8). Those stamps move; you re-check the live page instead of treating a draft-day figure as permanent coverage. The database answers one checkable question: which record is in a named official file now. It does not decide whether a transaction may proceed, and it does not merge two authorities into one person.

Search runs in this browser. The text you type is not sent to a server. A match means the official file contains that record. It is not a decision that a transaction is prohibited or allowed. Each row in the fourteen-file table is one downloadable official file. The file date is the date written in that file; if the file states no date, the cell stays empty. The local assembly time is not relabeled as an official date.

Named files on the live table include, among others, the OFAC Specially Designated Nationals List, the UN Security Council Consolidated List, the EU Consolidated Financial Sanctions List, the UK Sanctions List, and the BIS Entity List—alongside Australian, Canadian, Swiss and further US BIS files. You read each file under its own issuer. You never invent a per-file count beyond the disclosed total of 61,251 records across 14 sources.

Schematic: fourteen official files stay under each issuer — records are not merged across authorities

How to read a public record

You read each public record the way the hub publishes it. Fields the public record keeps include source id, party type, primary name, capped aliases, program or list labels, measure labels, countries the file states, and dates the file states; vessels or aircraft may keep an IMO number when the file provides one. Fields not published include date of birth, document numbers, street addresses, phones and emails. On the Canadian list, the country field means the sanctions regime stated in that file—not nationality.

You therefore never treat a shared spelling across two issuers as one global person. Each hit stays under its own source id and file. A similar name on another authority’s list is a separate lead until you verify identity, ownership and control against the official texts that matter for your case.

After a hit—and after a miss

You should treat a sanctions hit as a lead into the named official file, not as this site’s finding that a transaction must stop. You open the official source file the card names, compare primary name and aliases, program or list labels, measure labels and any dates the file states with your counterparty facts, then look for later notices, amendments, delistings or licence language that may apply on your transaction date. Ownership, control, intermediaries, carriers, banks and end users can still matter after you confirm the string match.

You likewise remember what a miss does not prove. No match does not rule out another list, an ownership rule, a sector measure or a licence. Queries miss for naming, aliases, transliteration, truncated strings and measures outside these fourteen files. China’s export-control lists stay in the entity-list database; to search both at once you use counterparty screening. You check the official text, and you ask a licensed attorney when the matter needs legal advice.

When you need watch-list versus control-list legal-effect literacy for one China export transaction—not this foreign-file mirror—keep Watch lists vs control lists: how to check and act on one export transaction once and return here for sanctions-hub method.

Boundaries and a practical checklist

You keep humility beside every screen. The live boundary footer states that the site provides general compliance information, not legal advice. Coverage stamps, file dates and record counts on the live sanctions page can change; do not treat a past screenshot as today’s clearance story. Keep Editorial and regulatory verification policy nearby when you need Zhengdao’s sourcing and “not legal advice” boundary in one place.

Before anyone treats a hit as a transaction decision, you can work these steps:

  1. Confirm the exact legal name and known aliases you searched.
  2. Note which issuer and which named official file produced the hit.
  3. Open the downloadable official file (or the issuer’s current publication) for the date that matters.
  4. Compare program or list labels, measure labels and dates the file states with your counterparty facts.
  5. Check ownership, control, intermediaries and end use when the case needs that depth.
  6. Look for later notices, amendments, delistings or licence language.
  7. Escalate to a licensed attorney when the workbench cannot answer your shipment question.
Flow: sanctions hit → open official source file → escalate — not a transaction decision

Frequently asked questions

What question does Zhengdao’s global sanctions list database answer?

You use it to check which record is in a named official foreign list file now, across the fourteen files the hub currently mirrors. A match means that file contains the record under its own source id. The database does not decide whether a transaction may proceed, and it does not merge two authorities into one person. You still open the official text and escalate when your case needs a judgment these pages cannot give.

When should you use the sanctions hub instead of China lists or one-box screening?

You use the sanctions hub when you already know you are working only inside the foreign-file mirror. You use the China lists hub when your question is China export-control or countermeasure notices. You use counterparty screening when you want one box across both datasets with results kept separate. Those surfaces stay complementary. You do not merge their hits into one party story just because the names look similar.

How should you read the fourteen-file table and the snapshot stamp?

You read each row as one downloadable official file. The file date is the date written in that file; if the file states no date, the cell stays empty. The local assembly time on the page is not relabeled as an official date. Live stamps such as 61,251 records, 14 sources and the snapshot assembled time move; you re-check the live page and record which stamp you read. You never invent per-file counts beyond the disclosed total.

What does a public record keep—and what stays unpublished?

You see source id, party type, primary name, capped aliases, program or list labels, measure labels, countries the file states and dates the file states; vessels or aircraft may keep an IMO when the file provides one. Date of birth, document numbers, street addresses, phones and emails are not published. On the Canadian list, the country field is the sanctions regime, not nationality. You keep each issuer’s identifier separate instead of inventing one global person card.

What does a match prove, and what does no match not rule out?

You should treat a match as a lead that the named official file contains that record—not as a Zhengdao ruling that you must stop. You open the official text, compare identifiers and labels, then escalate when ownership, licence or end-use questions remain. No match does not rule out another list, an ownership rule, a sector measure or a licence. Live language is clear: a quiet result is not clearance.

What should you do after a hit before anyone treats it as a decision?

You note issuer and file, open the official source, compare names, aliases, program or list labels and measure labels with your facts, then check later notices and licence language for your date. You also confirm ownership, control and end use when the case needs that depth. You ask a licensed attorney when the matter needs legal advice. You keep an audit trail of which coverage stamp and which file you read.

Open the sanctions hub—then verify the official file

When you are ready to search a party against the fourteen official foreign list files—and to treat every match as a lead rather than a transaction decision—open Global sanctions list database and keep humility beside you. You use Zhengdao’s sanctions hub to locate records inside named official files as of the disclosed snapshot, not to finish a stop-or-clear determination. Orient, open the official text, then escalate when needed.


Sources

This article is general compliance information and does not constitute legal advice; regulations are governed by the current official text.

Practical verification checklist

Scope · evidence · decision trail

Use the steps below to review this page. Verify the complete official text before making a decision. Seek qualified advice when needed.

  1. Define the decision

    State the exact decision, owner, deadline, trade direction and required evidence. Do this before you search.

  2. Identify every party

    Confirm each legal name and alias. Check registration, ownership, control, intermediaries, carriers, banks and beneficial owners.

  3. Describe the item

    Record the item’s function, operating principle, material, model and performance. Include software, technology, accessories and decisive parameters.

  4. Check classification

    Treat customs and export-control classification as separate tasks. Keep the facts, assumptions and reasoning for each result.

  5. Map the route

    Confirm origin, departure, destination and transit points. Include re-export, remote access, technology transfer and each delivery path.

  6. Verify end use

    Identify the stated purpose and real operating environment. Check integration, sensitive sectors, military links and prohibited uses.

  7. Verify end users

    Check the purchaser, consignee, end user, operator and parent company. Identify anyone who can redirect or control the item.

  8. Read the complete source

    Treat a search result as a lead. Read the official scope, definitions, notes, exclusions, annexes and licence conditions.

  9. Check current measures

    Use the version effective on the transaction date. Review later notices, temporary controls, destination measures and policy changes.

  10. Test exceptions carefully

    Prove every condition before using an exception or exemption. Apply the same rule to licence facilitation and general authorisations.

  11. Resolve contradictions

    Pause when names, codes, documents, routes, prices or explanations conflict. Obtain evidence instead of filling gaps with assumptions.

  12. Escalate uncertainty

    Send unresolved questions to the compliance owner or a qualified adviser. This includes classification, ownership, use, destination and licensing.

  13. Keep an audit trail

    Keep source links, files, checksums, screenshots, search terms and results. Record the reviewer, approvals and final reasoning.

  14. Schedule re-checks

    Set a new review date for open transactions. Re-check changing parties, destinations, specifications, official lists and licences.