GHunt – Investigate Google Accounts with emails.

GHunt is an OSINT tool to extract information from any Google Account using an email.

It can currently extract:

  • Owner’s name
  • The last time the profile was edited
  • Google ID
  • If the account is a Hangouts Bot
  • Activated Google services (YouTube, Photos, Maps, News360, Hangouts, etc.)
  • Possible YouTube channel
  • Possible other usernames
  • Public Photos
  • Phone models
  • Phone firmwares
  • Installed software
  • Google Maps reviews
  • Possible physical location



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 his 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. (commit 01dc016)
    It requires the “Profile photos” album to be public (it is by default)



You can build the Docker image with:

docker build --build-arg UID=$(id -u ${USER}) --build-arg GID=$(id -g ${USER}) -t ghunt .

Any of the scripts can be invoked through:

docker run -v $(pwd)/resources:/usr/src/app/resources -ti ghunt
docker run -v $(pwd)/resources:/usr/src/app/resources -ti ghunt <email_address>

Manual installation

  • Make sure you have Python 3.6.1+ installed. (I developed it with Python 3.8.1)
  • These Python modules are required (we’ll install them later):

1. Chromedriver & Google Chrome

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

2. Requirements

In the GHunt folder, run:

python -m pip install -r requirements.txt

Adapt the command to your operating system if needed.


For the first run and sometimes 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 4 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:

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 find these 4 cookies?

  1. Log in to
  2. After that, open the Dev Tools window and navigate to the Storage tab (Shift + F9 on Firefox) (It’s called “Application” on Chrome)
    If you don’t know how to open it, just right-click anywhere and click “Inspect Element”.
  3. Then you’ll find every cookie you need, including the 4 ones.


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