otlite · Email
Install Holehe on Linux or macOS 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 otlite
otlite install holehe
otlite run holehe -- e:jane@example.comRuns megadose/holehe (GPL-3.0, ★ 15k, 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 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
otlite translates these prefixes into Holehe's own flags. Anything else after -- is passed through unchanged, so every original flag still works.
- e:
- Email ·
otlite run holehe -- e:jane@example.com
Run every installed tool that takes the same input at once: otlite run --all e:jane@example.com
Where the results go
Every run lands under ./results/holehe/<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 holehe <target>, and pull indicators out with otlite extract holehe.
Before you run it
- Several services rate limit quickly; a rate-limited row is unknown, not absent.
- otlite runs Holehe with its password-recovery modules switched off by default.
Update, remove, inspect
otlite info holehe # inputs, keys, an example command
otlite example holehe # sample output, where there is one
otlite update holehe # move to the next tested version
otlite remove holehe # delete its virtualenvFull reference: the otlite docs, and the tool's own README on GitHub.
Pairs with
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.
FAQ
Holehe with otlite, answered
How do I install Holehe 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 holehe. 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 Holehe take through otlite?
e: (email). otlite 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 otlite save Holehe results?
Under ./results/holehe/<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 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 with otlite keys set NAME and are passed only to tools that declare them.
Can I run Holehe together with other tools?
Yes. otlite run --all e:jane@example.com runs every installed tool that takes email input, in parallel, including Holehe. Save the combination as a playbook to repeat it.