See inside a BLACKEYES report
The structure, depth, and detail you receive from every investigation — rendered here as a hybrid example.
This is a hybrid example based on anonymised elements drawn from multiple real investigations. No real individual is represented. The structure, section breakdown, citation style, and investigative depth are exactly what you receive from a live report.
The same report, built for every use case
This example happens to be a cybersecurity consultant. The eleven-section structure, source citations, and investigative depth are identical across every use case. A recruiter, letting agent, insurance fraud investigator, private investigator, or solicitor reading this report is looking at the same format you will receive for your subject.
Structured intelligence across every category
Depth of a human analyst, in minutes
Defensible and export-ready
From email input to completed report
Loading example report...
What a live report looks like
The sample above has been lightly shortened for readability. A real investigation returns the same eleven-section structure with:
Full breach-by-breach detail — every exposure cited with breach name, date, records affected, and leaked fields.
Verified vs potential URL appendix — every source categorised as verified match, potential match, or excluded, with reasoning.
Multi-pass verification — every finding cross-referenced through independent sources to prevent wrong-person attribution.
Export-ready formatting — shareable with stakeholders, legal teams, or internal case files.
Your investigations stay yours
Real reports are only ever visible to your own account. Targets are never contacted or notified — all data comes from publicly available sources and existing breach records. Reports are stored securely and encrypted.
Run your first investigation
Enter an email address and receive your own report in around 15 minutes. No platform to install, no OSINT skills required.
Reports are tools, not conclusive judgements — verify material findings before reliance. See the FAQ