otlite · Email
Install h8mail on Linux or macOS in one command
h8mail checks an email address against breach sources and, with API keys, pulls the matching records. Without keys it still queries the free sources and local breach dumps you point it at.
h8mail in three lines
pipx install otlite
otlite install h8mail
otlite run h8mail -- e:jane@example.comRuns khast3x/h8mail (Other, ★ 5.3k, otlite 1.2.1, catalog updated Oct 23, 2026). otlite installs and runs it at a tested version; it does not change or verify the tool itself.
What h8mail is for
- A quick breach check on an address.
- Searching your own local dump files with -lb.
- Chaining into reverse lookups on discovered passwords with the original flags.
Typed inputs for h8mail
otlite translates these prefixes into h8mail's own flags. Anything else after -- is passed through unchanged, so every original flag still works.
- e:
- Email ·
otlite run h8mail -- e:jane@example.com
Run every installed tool that takes the same input at once: otlite run --all e:jane@example.com
otlite marks it dual-use, so it asks you to accept a responsible-use notice before it installs.
Where the results go
Every run lands under ./results/h8mail/<target>/ as a timestamped output file, a .meta.json sidecar (the exact command, start and end time, exit code, and the SHA-256 of the output), and a .envelope.json with the entities found, in the same shape for every tool. List runs with otlite results, group them with --case, compare the last two with otlite diff h8mail <target>, and pull indicators out with otlite extract h8mail.
Before you run it
- The useful sources need API keys. Add them with otlite keys set NAME; otlite keys check verifies them.
- Breach data is sensitive. Store results under a case and restrict the folder.
Update, remove, inspect
otlite info h8mail # inputs, keys, an example command
otlite example h8mail # sample output, where there is one
otlite update h8mail # move to the next tested version
otlite remove h8mail # delete its virtualenvFull reference: the otlite docs, and the tool's own README on GitHub.
Pairs with
When open-source isn't enough
h8mail depends on the keys you bring. SearchIn runs breach providers per lookup from one wallet, with no subscriptions to manage.
FAQ
h8mail with otlite, answered
How do I install h8mail on Kali, Ubuntu, or macOS?
Install otlite once with pipx install otlite (or the one-line installer on the otlite page), run otlite init, then otlite install h8mail. The tool lands in its own virtualenv under ~/.otlite/, pinned to a version that was tested, so nothing touches your system Python. otlite doctor prints the command that fixes a missing git or venv module.
Which inputs does h8mail take through otlite?
e: (email). otlite maps each prefix to h8mail's own flag. Everything after -- that is not a typed input is passed through unchanged, so the original flags still work.
Where does otlite save h8mail results?
Under ./results/h8mail/<target>/ in the folder you run from, as a timestamped output file plus a .meta.json sidecar (the exact command, timing, exit code, and SHA-256) and a .envelope.json with the entities found. Add --case <name> to group runs, otlite results to list them, and otlite diff h8mail <target> to compare the last two.
Does h8mail need an API key or a login?
No key is required for the basic run. The useful sources need API keys. Add them with otlite keys set NAME; otlite keys check verifies them.
Can I run h8mail together with other tools?
Yes. otlite run --all e:jane@example.com runs every installed tool that takes email input, in parallel, including h8mail. Save the combination as a playbook to repeat it.