Tool profile
ICIJ Offshore Leaks Database
Investigative offshore entity and intermediary database
Claims and corrections are reviewed before public profile changes.
Trust / disclosure
How to read this profile
Editorial line
Editorial judgment and commercial context are kept separate on OSINT4ALL.
Review status
This profile is marked as editor-tested; workflow notes and caveats are shown where available.
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.
Checking whether a person, company, intermediary, address, or entity appears in ICIJ offshore leak datasets during due diligence or accountability reporting.
Treat every hit as a lead requiring source-context review, not as a conclusion about wrongdoing.
Best for checking whether people, companies, or intermediaries appear in ICIJ offshore leak datasets.
Operational snapshot
Workflow, access, and coverage
Entity and relationship records from ICIJ offshore investigations
Entity Name, Person Name, Address, Jurisdiction
Offshore Entity Reference, Historical Relationship, Source Investigation
Historical Entity Discovery, Ownership Lead Research
Being listed does not imply illegal or improper conduct. Names can refer to different entities, and each source investigation covers a particular historical period. Corroborate identifiers and dates; the database is not a complete or current ownership register.
Search exact names and variants, inspect connected entities and source dataset, record confidence level, then corroborate with primary registries, filings, sanctions, court records, archives, and subject response where appropriate.
Names may appear with transliteration, aliases, entity suffixes, and jurisdiction-specific spelling variants.
Limits
Strengths, caveats, and risk
High-value investigative lead source that can reveal offshore relationships and document trails worth deeper review.
Sensitive matches can be legally and reputationally serious, and weak name matching can create false associations.
Does not prove illegality, beneficial ownership, current control, tax status, sanctions exposure, or that a record still reflects present-day relationships.
False positives, name collisions, historical records, and misunderstood roles can create serious reputational harm.
Do not imply criminality or wrongdoing from an offshore database match alone; seek legal/editorial review for sensitive publication.
Always state the dataset, match basis, entity role, dates, and corroborating records when referencing 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-26
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.