otlite · Email
Install GHunt on Linux or macOS in one command
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. It works through Google's own endpoints.
GHunt in three lines
pipx install otlite
otlite install ghunt
otlite run ghunt -- e:jane@example.comRuns mxrch/GHunt (Other, ★ 20k, 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 GHunt is for
- Confirming a Gmail address belongs to a live account.
- Finding the display name and photo behind an address.
- Pivoting from an address to public Maps reviews.
Typed inputs for GHunt
otlite translates these prefixes into GHunt's own flags. Anything else after -- is passed through unchanged, so every original flag still works.
- e:
- Email ·
otlite run ghunt -- e:jane@example.com
GHunt asks questions in the terminal, so otlite run --all and otlite auto skip it. Run it on its own.
Where the results go
Every run lands under ./results/ghunt/<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 ghunt <target>, and pull indicators out with otlite extract ghunt.
Before you run it
- Needs a one-time login (ghunt login) with your own Google cookies. Use a dedicated research account.
- Google changes endpoints often; if a module fails, update with otlite update ghunt.
Update, remove, inspect
otlite info ghunt # inputs, keys, an example command
otlite example ghunt # sample output, where there is one
otlite update ghunt # move to the next tested version
otlite remove ghunt # delete its virtualenvFull reference: the otlite docs, and the tool's own README on GitHub.
Pairs with
When open-source isn't enough
GHunt covers Google. SearchIn's identity and leak providers cover the other services the same address is registered on.
FAQ
GHunt with otlite, answered
How do I install GHunt 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 ghunt. 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 GHunt take through otlite?
e: (email). otlite maps each prefix to GHunt'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 GHunt results?
Under ./results/ghunt/<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 ghunt <target> to compare the last two.
Does GHunt need an API key or a login?
Yes. Needs a one-time login (ghunt login) with your own Google cookies. Use a dedicated research account. Keys go in with otlite keys set NAME, which stores them in ~/.otlite/.env with permissions 600, and otlite keys check verifies them.
Can I run GHunt together with other tools?
Not under --all. GHunt asks questions in the terminal, so otlite run --all and otlite auto skip it on purpose. Run it on its own.