OpenSanctions

Sanctions, PEP, and watchlist context with source links

Best for Sanctions, PEP, watchlist, vessel, company, and public-interest screening where structured entity data and source lists matter.
Workflow Verification
Pricing / access Freemium · Browser-Based
Source checked 2026-05-27

Claims and corrections are reviewed before public profile changes.

OpenSanctions official-page screenshot

Official-page screenshot

OpenSanctions

Source checked 2026-05-27

Sanctions, PEP, and watchlist context with source links

Verification: Verification status not listed Workflow: Verification Pricing: Freemium

Best for: Sanctions, PEP, watchlist, vessel, company, and public-interest screening where structured entity data and source lists matter.

Editorial

Signal summary

  • VendorOpenSanctions
  • PlatformPlatform coverage varies by tool.
  • Reviewed2026-05-27

Trust / disclosure

How to read this profile

Editorial

Editorial line

Editorial judgment and commercial context are kept separate on OSINT4ALL.

Review status

This profile has an editorial review date. Source checking does not mean the tool was hands-on tested.

Claims / submissions

Corrections and claim requests are reviewed before any public change is made.

Commercial context

No commercial relationship is disclosed on this profile.

Editorial verdict

Use case and fit

This is editorial guidance, not vendor copy.

Best for

Sanctions, PEP, watchlist, vessel, company, and public-interest screening where structured entity data and source lists matter.

Editorial read

Use OpenSanctions to identify sensitive source-list context, not to make standalone allegations.

Overview

Best for sanctions, PEP, watchlist, and public-interest screening when identity matching and source context are handled carefully.

Operational snapshot

Workflow, access, and coverage

WorkflowVerification
PricingFreemium
AccessBrowser-Based
RegionsGlobal
LanguagesMultilingual
StatusStatus under review
Tool function
Core jobs

Matching entities against sanctions and other risk-related datasets

Works from

Entity Name, Entity Identifier, Country, Birth Date

Produces

Possible Entity Match, Risk Topic, Source List Reference

Workflow roles

Screening Triage, Identity Corroboration

Interpretation limits

A name match requires identity review. PEPs and related parties are not automatically sanctioned, and appearing in a sanctions-source dataset is not itself a designation. Check the entity identifiers, risk topic, current primary list and relevant dates before reaching a conclusion.

Recommended workflow

Search identifiers before names, inspect source lists, compare dates and aliases, label possible matches clearly, then confirm with official lists or professional review.

Language notes

Names may appear in multiple scripts, transliterations, aliases, and local naming conventions.

Limits

Strengths, caveats, and risk

Strengths

Transparent source-list approach makes it useful for cautious screening and entity-resolution workflows.

Limitations

Identity matching remains hard; weak name-only matches can create serious false positives.

Does not prove identity, wrongdoing, current legal status, or complete global coverage from a name match alone.

Risk note

False positives can harm people and companies if weak identity matches are published or acted on too strongly.

Sanctions and compliance-sensitive findings should be checked against official sources and appropriate professional standards before decisions.

Trust note

Review the underlying source, identifiers, dates, aliases, and match confidence before using a result.

Maintenance

Source status & suggest an update

Help keep this profile accurate. Update requests are reviewed and logged before publication.

Source checked: 2026-05-27

If something is outdated, please submit a correction or ownership update request. Claim requests are reviewed and do not grant editorial control.

Commercial or sponsorship requests use the separate partner workflow.

Claim / Correct Listing