otinstaller · Email

Install h8mail on Linux 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 otinstaller
ot install h8mail
ot run h8mail -- e:jane@example.com

Runs khast3x/h8mail (Other, ★ 5.3k, otinstaller v0.0.4, registry updated Oct 13, 2026). otinstaller installs and runs it; it does not change or verify it.

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

otinstaller translates these prefixes into h8mail's own flags. Anything else after -- is passed through unchanged, so every original flag still works.

e:: email · ot run h8mail -- e:jane@example.com

Run every installed tool that takes the same input at once: ot run --all e:jane@example.com

Where the results go

Every run lands under ./results/h8mail/<target>/ as a timestamped output file plus a .meta.json sidecar: the exact command, start and end time, exit code, and the SHA-256 of the output. Group runs with --case, compare the last two with ot diff h8mail <target>, and pull indicators out with ot extract.

Before you run it

The useful sources need API keys in ~/.otinstaller/.env. Run ot keys check.
Breach data is sensitive. Store results under a case and restrict the folder.

Update, remove, inspect

ot info h8mail      # inputs, flags, keys
ot example h8mail   # sample output
ot update h8mail    # move to the next tested version
ot remove h8mail    # delete its virtualenv

Full reference for this tool: docs for h8mail.

Pairs with

Holehe

Holehe asks about 120 services whether an email address is registered, using their password-reset and sign-up checks without sending anything to the address.

MailAccess

MailAccess checks an email address against a large set of platforms for registration, groups the hits into likely identities, and flags addresses seen in breach data.

GHunt

GHunt looks up a Google account by its Gmail address and returns the public parts of it: profile name and photo, Google ID, reviews, and sometimes a calendar or Maps contributions.

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.

Breach intelligence

Breach intelligence

Breach intelligence

Breach intelligence

FAQ

h8mail with otinstaller, answered

How do I install h8mail on Kali or Ubuntu?

Install otinstaller once with pipx install otinstaller, run ot init, then ot install h8mail. The tool lands in its own virtualenv under ~/.otinstaller/, pinned to a version that was tested on Ubuntu, so nothing touches your system Python. ot doctor flags a missing git or venv module.

Which inputs does h8mail take through otinstaller?

e: (email). otinstaller 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 otinstaller save h8mail results?

Under ./results/h8mail/<target>/ in the folder you run from, as a timestamped output file plus a .meta.json sidecar with the exact command, timing, exit code, and SHA-256. Add --case <name> to group runs, and ot 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 in ~/.otinstaller/.env. Run ot keys check.

Can I run h8mail together with other tools?

Yes. ot run --all e:jane@example.com runs every installed tool that accepts email input, in parallel, including h8mail. Save the combination as a playbook to repeat it.