OSINTverse

otinstaller · Email

Install Holehe on Linux in one command

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. It reports used, not used, or rate limited per site.

Holehe in three lines

pipx install otinstaller
ot install holehe
ot run holehe -- e:jane@example.com

Runs megadose/holehe (GPL-3.0, ★ 15k, otinstaller v0.0.4, registry updated Oct 13, 2026). otinstaller installs and runs it; it does not change or verify it.

What Holehe is for

  • Confirming an address is real and active before spending credits on it.
  • Seeing which platforms to look at next for a given email.
  • Bulk checks from a file with the original --only-used flag.

Typed inputs for Holehe

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

e:
email · ot run holehe -- e:jane@example.com
u:
username · ot run holehe -- u:jane_doe

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/holehe/<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 holehe <target>, and pull indicators out with ot extract.

Before you run it

  • Several services rate limit quickly; a rate-limited row is unknown, not absent.
  • otinstaller runs Holehe with its password-recovery modules switched off by default.

Update, remove, inspect

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

Full reference for this tool: docs for holehe.

Pairs with

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.
h8mail checks an email address against breach sources and, with API keys, pulls the matching records.
socialscan asks a short list of major platforms whether a username or email is available, taken, or invalid, using their own sign-up validation.

When open-source isn't enough

Holehe says where an address is registered. SearchIn's leak and identity providers return the records behind it: breach rows, names, and linked accounts.

People & identity
People & identity
Breach intelligence
Breach intelligence

FAQ

Holehe with otinstaller, answered

How do I install Holehe on Kali or Ubuntu?

Install otinstaller once with pipx install otinstaller, run ot init, then ot install holehe. 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 Holehe take through otinstaller?

e: (email), u: (username). otinstaller maps each prefix to Holehe'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 Holehe results?

Under ./results/holehe/<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 holehe <target> to compare the last two.

Does Holehe need an API key or a login?

No key is required for the basic run. Optional keys, where the project supports them, go in ~/.otinstaller/.env and are passed only to tools that declare them.

Can I run Holehe together with other tools?

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