How to install Holehe, step-by-step guide

This guide walks you through installing Holehe on Linux, macOS, Windows and Docker, and how to verify it works. Before you dive in: if you just want a report right now, the online version requires no install at all.

The fast path, use Holehe online

Before installing anything, know that holehe-osint.com is the full Holehe inside your browser. No Python dependencies, no terminal, no version conflicts, paste an email address and the report arrives in seconds. It is the recommended option if you just want a result fast.

Run a Holehe scan with no install →

Install Holehe on Linux and macOS

Holehe is a Python package published on PyPI. The clean way is to always use a virtual environment so you do not pollute your system Python.

  1. Check your Python version: python3 --version. Aim for 3.10 or 3.11.
  2. Create a virtual environment: python3 -m venv .venv
  3. Activate it: source .venv/bin/activate
  4. Upgrade pip: pip install --upgrade pip
  5. Install Holehe: pip install holehe

On macOS, if python3 is not installed, the easiest path is Homebrew: brew install [email protected].

Install Holehe on Windows

On Windows you can install Holehe via Python for Windows, WSL or Docker. Each route has its own gotchas: PowerShell execution policies, Python version conflicts, dependencies that do not love native Windows…

We have a dedicated guide covering all three methods in detail, with the exact commands and the most common errors: Holehe for Windows →

Install Holehe with Docker (optional)

If you prefer to isolate Holehe completely from your host system, Docker is a great option. You get a frozen Python environment, independent of your OS.

  1. Create a Dockerfile with a Python 3.11 base image
  2. Add RUN pip install holehe
  3. Build the image: docker build -t holehe .
  4. Run: docker run --rm holehe [email protected]

Verify your install

Once Holehe is installed, run a quick smoke test to confirm everything works:

holehe [email protected]

You should see Holehe enumerate modules one by one, then print a "Found" or "Not Found" verdict for each supported site. If you see a colourful report scrolling, the install succeeded.

Troubleshooting common errors

  • aiohttp fails to build: upgrade pip, install your OS build-tools, or downgrade to Python 3.11.
  • SSL / certificate errors: run pip install --upgrade certifi.
  • Version conflicts: delete your venv, recreate it, and reinstall Holehe from scratch.
  • Module not found: make sure your venv is activated before running the holehe command.

Frequently asked questions

Which Python version do I need for Holehe?
Holehe works best with Python 3.10 or 3.11. Newer versions (3.12+) can cause dependency conflicts with aiohttp and httpx. If you are stuck on Python 3.12+, use a virtualenv pinned to 3.11, install via pyenv, or simply use holehe-osint.com which requires no Python at all.
Can I install Holehe without sudo or root?
Yes. The recommended pattern is to create a virtual environment ("python -m venv .venv"), activate it, then run "pip install holehe". This installs Holehe and its dependencies inside the venv folder, no root access, no system-wide changes, and no risk of breaking your distro Python.
Does Holehe work on Mac M1, M2 or M3 (Apple Silicon)?
Yes. Holehe is pure Python and runs natively on Apple Silicon. Install Python via Homebrew ("brew install [email protected]"), create a venv and run "pip install holehe". If aiohttp fails to build wheels, upgrade pip first with "pip install --upgrade pip".
Can I install Holehe on Termux or Android?
Yes, but it is fiddly: install pkg termux, then python, then pip install holehe inside a venv. Some dependencies (lxml, cryptography) may need build tools. For most Android users the simpler path is to open holehe-osint.com directly in your mobile browser, same coverage, zero setup.
How do I fix common pip install errors with Holehe?
The two most common errors are (1) aiohttp build failures, fix by upgrading pip and installing build tools, or pin Python to 3.11; (2) SSL or certificate errors, fix with "pip install --upgrade certifi". If conflicts persist, wipe the venv and reinstall from scratch.