otinstaller · Email

Install GHunt on Linux 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 otinstaller
ot install ghunt
ot run ghunt -- u:jane_doe

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

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

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

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

Run every installed tool that takes the same input at once: ot run --all u:jane_doe

Where the results go

Every run lands under ./results/ghunt/<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 ghunt <target>, and pull indicators out with ot extract.

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 ot update ghunt.

Update, remove, inspect

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

Full reference for this tool: docs for ghunt.

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.

socialscan

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

GHunt covers Google. SearchIn's identity and leak providers cover the other services the same address is registered on.

People & identity

People & identity

Breach intelligence

FAQ

GHunt with otinstaller, answered

How do I install GHunt on Kali or Ubuntu?

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

u: (username), e: (email). otinstaller 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 otinstaller save GHunt results?

Under ./results/ghunt/<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 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 and tokens live in ~/.otinstaller/.env with permissions 600, and ot keys check verifies them.

Can I run GHunt together with other tools?

Yes. ot run --all u:jane_doe runs every installed tool that accepts username input, in parallel, including GHunt. Save the combination as a playbook to repeat it.