Tool profile
GHunt
Open-source Google account OSINT lead-generation tool
Claims and corrections are reviewed before public profile changes.
Repository screenshot
mxrch
Open-source Google account OSINT lead-generation tool
Best for: Checking public Google-account signals from an email, Gaia ID, Drive artifact, or account clue during authorized people, source,…
Signal summary
Trust / disclosure
How to read this profile
Editorial line
Editorial judgment and commercial context are kept separate on OSINT4ALL.
Review status
Hands-on notes or editorial review dates are attached where available.
Claims / submissions
Corrections and claim requests are reviewed before any public change is made.
Commercial context
No commercial relationship is disclosed on this profile.
Editorial verdict
Use case and fit
This is editorial guidance, not vendor copy.
Checking public Google-account signals from an email, Gaia ID, Drive artifact, or account clue during authorized people, source, or case research.
Useful for advanced practitioners, but too sensitive for casual use without clear authorization, privacy discipline, and careful notes.
Best when a Google account identifier needs cautious public-footprint triage by an experienced operator, not identity proof.
Operational snapshot
Workflow, access, and coverage
Email and professional identity research, Public account-registration signals
Email, Domain, Phone Number, Organization, Username
Account Clue, Professional Contact Pattern, Reputation Signal, Identity Lead, Service Registration Signal
Discovery, Enrichment, Verification
Start from an authorized Google-related clue, record only necessary public signals, flag uncertainty, avoid retaining cookies or sensitive identifiers, then corroborate with archives, profiles, direct documents, or source-protected reporting before drawing conclusions.
Tooling and documentation are English-first. Interpreting account context may require local-language review.
Limits
Strengths, caveats, and risk
Open-source and inspectable, with CLI modules, JSON export, and a focused workflow for Google-related public account context.
May require authentication/cookie handling, depends on changing Google surfaces, and can produce sensitive or weak leads that are easy to overstate.
Does not prove identity, account ownership, current control, private activity, or consent; some checks may fail or change as Google surfaces change.
Account-enrichment work can expose private individuals to misidentification, stalking, or harassment risk if weak leads are published as facts.
Use only within lawful, authorized research. Avoid invasive collection, credential misuse, cookie sharing, or attempts to access non-public account data.
Every lead needs independent corroboration from profile context, timestamps, archives, direct sources, or other verified records.
Alternatives
Alternatives
Epieos for email-led enrichment, WhatsMyName for username leads, and Advanced Search Operators Workflow for manual corroboration.
Maintenance
Last verified & suggest an update
Help keep this profile accurate. Update requests are reviewed and logged before publication.
Last verified: 2026-05-27
If something is outdated, please submit a correction or verified update request. Claim requests are reviewed and do not grant editorial control.
Commercial or sponsorship requests use the separate partner workflow.