Tool profile
FOCA
Open-source document metadata analysis for OSINT and exposure review
Claims and corrections are reviewed before public profile changes.
Live interface preview
ElevenPaths
Open-source document metadata analysis for OSINT and exposure review
Best for: Inspecting public document metadata for usernames, software clues, paths, and organization context during authorized research.
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.
Inspecting public document metadata for usernames, software clues, paths, and organization context during authorized research.
Useful for analysts who understand metadata limits and need a structured way to inspect public documents.
Best when public documents need metadata inspection for usernames, software clues, and document-origin context.
Operational snapshot
Workflow, access, and coverage
Find public documents, inspect metadata, separate weak clues from strong ones, then corroborate with source pages, archives, and direct records before reporting.
Interface and documentation are English/Spanish-adjacent depending on release context; metadata values can appear in any language.
Limits
Strengths, caveats, and risk
Focused metadata workflow that can surface hidden document clues useful for verification or defensive exposure review.
Older tooling and document-specific behavior can make results inconsistent, especially with stripped or transformed files.
Metadata is not proof by itself. It can be stale, copied from templates, removed by platforms, or unrelated to the current publisher.
Metadata can expose personal or operational details. Handle findings carefully and avoid publishing unnecessary identifiers.
Analyze only public or authorized documents. Do not use metadata findings for harassment, intrusion, or unsupported exposure claims.
Confirm metadata clues with document provenance, archives, source pages, and separate records before making claims.
Alternatives
Alternatives
Maintenance
Last verified & suggest an update
Help keep this profile accurate. Update requests are reviewed and logged before publication.
Last verified: 2026-05-06
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.