Email investigation playbook

Verified publisher

Trace a suspicious message and find where an address is registered, without alerting its owner

beginnerabout email6 toolslicence CC-BY-4.0
Contents 5/6
  1. 1 Email investigation playbook
  2. 2 Scope and legal
  3. 3 Read the message headers
  4. 4 Check the sender's domain
  5. 5 Find registered accounts
  6. 6 Pivot
Tools (6)

Tools used in this guide

  • email-header-parser Parses raw email headers into senders, relay hops, IPs and SPF/DKIM/DMARC resultsot install osintverse-community/email-header-parser
  • checkdmarc Checks a domain's SPF, DMARC, MX, BIMI and DNSSEC records and reports problemsot install osintverse-community/checkdmarc
  • dns-records Looks up a domain's A, AAAA, CNAME, MX, NS, TXT, SOA and CAA recordsot install osintverse-community/dns-records
  • holehe Checks whether an email address is registered on 120+ sites, without alerting its ownerot install osintverse-community/holehe
  • socialscan Checks whether a username or email address is in use on major platforms, accurately and quicklyot install osintverse-community/socialscan
  • mailcat Finds existing email addresses for a nickname across 25+ mail providersot install osintverse-community/mailcat

Install them all:

ot guide tools osintverse-community/email-investigation

Find registered accounts

Most sites tell you, one way or another, whether an address already has an account. These tools ask in ways that do not notify the owner.

ot run osintverse-community/holehe --email someone@example.com
ot run osintverse-community/socialscan --query someone@example.com

holehe checks 120+ sites and lists the ones where the address is registered, sometimes with a partly masked recovery phone or email. socialscan covers fewer platforms but uses their own availability checks, so its answers are reliable.

Reading the results

  • A hit says an account exists. It does not show the profile, and many services allow an address to be registered without verification, so someone else may have used it.
  • Rate limits produce errors, not "not registered". Re-run later rather than treating an error as a negative.
  • Masked recovery details (+1 ••• ••• ••23, j•••@g•••.com) can be matched against identifiers you already hold. Never try to unmask them through the site's recovery flow.

Note

Breach and paste lookups (Have I Been Pwned and similar) are useful here too, but need API keys and their own legal review. Add them only where your scope allows.

Next: pivot.

Published 20 Oct 2026. Read it in a terminal: ot guide read osintverse-community/email-investigation; offline: ot guide get osintverse-community/email-investigation · Source · Markdown

Esc

Try

↑ ↓ to move↵ to open