Tool profile

/

GHunt

Open-source Google account OSINT lead-generation tool

Verification: Pending Verification Status: Active
Best for Checking public Google-account signals from an email, Gaia ID, Drive artifact, or account clue during authorized people, source, or case research.
Workflow Discovery, Enrichment
Pricing / access Free ยท Desktop, Self-Hosted
Source checked 2026-05-27
Visit tool website Suggest a correction Trust notes

Claims and corrections are reviewed before public profile changes.

Signal summary

  • Vendormxrch
  • PlatformPlatform coverage varies by tool.
  • Reviewed2026-05-27

Trust / disclosure

How to read this profile

Editorial

Editorial line

Editorial judgment and commercial context are kept separate on OSINT4ALL.

Review status

This profile has an editorial review date. Source checking does not mean the tool was hands-on tested.

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.

Best for

Checking public Google-account signals from an email, Gaia ID, Drive artifact, or account clue during authorized people, source, or case research.

Editorial read

Useful for advanced practitioners, but too sensitive for casual use without clear authorization, privacy discipline, and careful notes.

Overview

Best when a Google account identifier needs cautious public-footprint triage by an experienced operator, not identity proof.

Operational snapshot

Workflow, access, and coverage

WorkflowDiscovery, Enrichment
PricingFree
AccessDesktop, Self-Hosted
RegionsGlobal
LanguagesEnglish
StatusActive
Tool function
Core jobs

Google account and shared-file context from supported identifiers

Works from

Email, Google Account ID, Drive File Or Folder

Produces

Google Account Context, Shared File Context, JSON Report

Workflow roles

Discovery, Identity Corroboration

Interpretation limits

Google-specific modules are not a general email finder or proof of account ownership. Results depend on module support, visibility and authenticated access; protect your own session data and respect access restrictions.

Recommended workflow

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.

Language notes

Tooling and documentation are English-first. Interpreting account context may require local-language review.

Limits

Strengths, caveats, and risk

Strengths

Open-source and inspectable, with CLI modules, JSON export, and a focused workflow for Google-related public account context.

Limitations

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.

Risk note

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.

Trust note

Every lead needs independent corroboration from profile context, timestamps, archives, direct sources, or other verified records.

Maintenance

Source status & suggest an update

Help keep this profile accurate. Update requests are reviewed and logged before publication.

Source checked: 2026-05-27

If something is outdated, please submit a correction or ownership update request. Claim requests are reviewed and do not grant editorial control.

Commercial or sponsorship requests use the separate partner workflow.

Claim / Correct Listing