Tool profile
Intelligence X
Sensitive-source and archive search context
Claims and corrections are reviewed before public profile changes.
Editorial workflow visual
Intelligence X
Sensitive-source and archive search context
Best for: Selector-based search across archived, public-web, leak-adjacent, WHOIS, DNS, dark-web-adjacent, and document datasets when the identifier is already in…
Signal summary
Trust / disclosure
How to read this profile
Editorial line
Editorial judgment and commercial context stay separate on OSINT4ALL.
Review status
Hands-on notes or editorial review dates are attached 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.
Selector-based search across archived, public-web, leak-adjacent, WHOIS, DNS, dark-web-adjacent, and document datasets when the identifier is already in scope.
High-signal but high-responsibility tool; useful for serious investigations, not casual browsing of sensitive exposure data.
Best when a selector such as an email, domain, URL, IP, or hash needs archive and leak-adjacent search with strict handling.
Operational snapshot
Workflow, access, and coverage
Start with a scoped selector, limit review to relevant source categories, log provenance, avoid unnecessary retention of sensitive material, and corroborate useful leads through safer public sources when possible.
Interface is English-first, but archived and leaked-source material can appear in many languages and scripts.
Limits
Strengths, caveats, and risk
Powerful selector model, historical archive angle, API/SDK support, and useful coverage for email, domain, URL, IP, hash, and crypto-address pivots.
Can expose sensitive or legally complicated results, and many high-value buckets require paid access or careful access control.
Does not prove identity, authorship, compromise, current exposure, or lawful reuse of exposed material.
Leak-adjacent search can expose personal data, credentials, victim information, or unrelated people with matching selectors.
Do not republish or use exposed personal data, credentials, or sensitive material without a clear legal/editorial basis and source-protection review.
Treat results as leads requiring provenance, legality, and source-risk review before any publication or action.
Alternatives
Alternatives
Have I Been Pwned for breach-notification context, Wayback Machine for public web history, urlscan.io for URL behavior, and Aleph for document-backed public-interest records.
Maintenance
Last verified & suggest an update
Help keep this profile accurate. Update requests are reviewed and logged before publication.
Last verified: 2026-05-07
If something is outdated, please submit a correction or verified update request. Claim requests are reviewed and do not grant editorial control.
Commercial or sponsorship requests use the separate partner workflow.