GHunt | Enumerate Gmails | Extract Information From Any Google Account Using An Email

Python minimum version

Docker Cloud Build Status GitHub Workflow Status


GHunt is a modulable OSINT tool designed to evolve over the years, and incorporates many techniques to investigate Google accounts, or objects.
It currently has email, document, youtube and gaia modules.

:fire: GHunt is being completely refactored, to allow use as a Python library, removing Selenium and Google Chrome dependencies, using definition types and async, to prepare for v2.
You can track the progress on this project here:
And on this branch :
Please understand that the activity of the master branch will now be reduced, and therefore the pull requests too.

What can GHunt find ?

:world_map: Email module:

  • Owner’s name
  • Gaia ID
  • Last time the profile was edited
  • Profile picture (+ detect custom picture)
  • If the account is a Hangouts Bot
  • Activated Google services (YouTube, Photos, Maps, News360, Hangouts, etc.)
  • Possible YouTube channel
  • Possible other usernames
  • Google Maps reviews (M)
  • Possible physical location (M)
  • Events from Google Calendar (C)
  • Organizations (work & education) (A)
  • Contact emails (A)
  • Contact phones (A)
  • Addresses (A)
  • Public photos (P)
  • Phones models (P)
  • Phones firmwares (P)
  • Installed softwares (P)

:world_map: Document module:

  • Owner’s name
  • Owner’s Gaia ID
  • Owner’s profile picture (+ detect custom picture)
  • Creation date
  • Last time the document was edited
  • Public permissions
  • Your permissions

:world_map: Youtube module:

  • Owner’s Gaia ID (through Wayback Machine)
  • Detect if the email is visible
  • Country
  • Description
  • Total views
  • Joined date
  • Primary links (social networks)
  • All infos accessible by the Gaia module

:world_map: Gaia module:

  • Owner’s name
  • Profile picture (+ detect custom picture)
  • Possible YouTube channel
  • Possible other usernames
  • Google Maps reviews (M)
  • Possible physical location (M)
  • Organizations (work & education) (A)
  • Contact emails (A)
  • Contact phones (A)
  • Addresses (A)

The features marked with a (P) require the target account to have the default setting of Allow the people you share content with to download your photos and videos on the Google AlbumArchive, or if the target has ever used Picasa linked to their Google account.
More info here.

Those marked with a (M) require the Google Maps reviews of the target to be public (they are by default).

Those marked with a (C) require user to have Google Calendar set on public (default it is closed).

Those marked with a (A) require user to have the additional info set on profile with privacy option “Anyone” enabled.


:newspaper: Latest news

  • 02/10/2020 : Since a few days ago, Google returns a 404 when we try to access someone’s Google Photos public albums, we can only access it if we have a link to one of their albums.
    Either this is a bug and this will be fixed, either it’s a protection that we need to find how to bypass.
  • 03/10/2020 : Successfully bypassed. :man_dancing: (commit 01dc016)
    It requires the “Profile photos” album to be public (it is by default)
  • 20/10/2020 : Google WebArchive now returns a 404 even when coming from the “Profile photos” album, so the photos scraping is temporary (or permanently) disabled. (commit e762543)
  • 25/11/2020 : Google now removes the name from the Google Maps profile if the user has 0 reviews (or contributions, even private). I did not find a bypass for the moment, so all the help in the research of a bypass is appreciated.
  • 20/03/2021 : Successfully bypassed. :man_dancing: (commit b3b01bc)


Manual installation

  • Make sure you have Python 3.8+ installed. (I developed it with Python 3.8.1)
  • Some Python modules are required which are contained in requirements.txt and will be installed below.

1. Chromedriver & Google Chrome

This project uses Selenium and automatically downloads the correct driver for your Chrome version.
:warning: So just make sure to have Google Chrome installed.

2. Cloning

Open your terminal, and execute the following commands :

git clone cd ghunt

3. Requirements

In the GHunt folder, run:

python3 -m pip install -r requirements.txt

Adapt the command to your operating system if needed.


The Docker image is automatically built and pushed to Dockerhub after each push on this repo.
You can pull the Docker image with:

docker pull

Then, you can use the and to invoke GHunt through Docker, or you can use these commants :

docker run -v ghunt-resources:/usr/src/app/resources -ti
docker run -v ghunt-resources:/usr/src/app/resources -ti


For the first run and sometime after, you’ll need to check the validity of your cookies.
To do this, run
If you don’t have cookies stored (ex: first launch), you will be asked for the required cookies. If they are valid, it will generate the Authentication token and the Google Docs & Hangouts tokens.

Then, you can run the tool like this:

python3 email [email protected]

python3 doc

:warning: I suggest you make an empty account just for this or use an account where you never login because depending on your browser/location, re-logging in into the Google Account used for the cookies can deauthorize them.

Where I get these cookies ?

Auto (faster)

You can download the GHunt Companion extension that will automate the cookies extraction in 1-click !

Firefox Chrome Edge

You just need to launch the file and choose the extraction mode you want to use, between putting GHunt in listening mode, or copy/paste the encoded cookies in base64.


  1. Be logged-in to
  2. After that, open the Dev Tools window and navigate to the Network tab
    If you don’t know how to open it, just right-click anywhere and click “Inspect Element”.
  3. Go to, and in the browser requests, select the GET on “” that gives a 302 redirect
  4. Then you’ll find every cookie you need in the “cookies” section.


:shield: Protecting yourself

Regarding the collection of metadata from your Google Photos account:

Given that Google shows “X require access” on your Google Account Dashboard, you might imagine that you had to explicitly authorize another account in order for it to access your pictures; but this is not the case.
Any account can access your AlbumArchive (by default):


Here’s how to check and fix the fact that you’re vulnerable (which you most likely are):
Go to while logged in with your Google account. You will be automatically redirected to your correct albumarchive URL ( After that, click the three dots on the top left corner, and click on setting


Then, uncheck the only option there:


On another note, the target account will also be vulnerable if they have ever used Picasa linked to their Google account in any way, shape or form. For more details on this, read PinkDev1’s comment on issue #10.
For now, the only (known) solution to this is to delete the Picasa albums from your AlbumArchive.


This tool is based on Sector’s research on Google IDs and completed by my own as well.
If I have the motivation to write a blog post about it, I’ll add the link here !

  • Palenath (for the name bypass)



Bravo! Thank you for this intel @SaM!