# Holehe Email OSINT Scraper - Find Accounts by Email (`scrapesage/holehe-scraper`) Actor

Email OSINT like Holehe: for each email, check whether it is registered on a validated set of sites, resolve its Gravatar profile (avatar and linked accounts), and get OSINT footprint and breach-check URLs (HIBP, DeHashed, IntelX). No login, no key. Export JSON, CSV, Excel.

- **URL**: https://apify.com/scrapesage/holehe-scraper.md
- **Developed by:** [Scrape Sage](https://apify.com/scrapesage) (community)
- **Categories:** Automation, Lead generation, Agents
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $4.40 / 1,000 email analyseds

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Holehe Email OSINT Scraper - Find Accounts by Email

Investigate an email address the way **Holehe** does. For each email you get:

- **Site registrations** - whether the email is registered on a validated set of sites (checked live).
- **Gravatar profile** - if the email has a Gravatar, its profile URL, display name and any linked accounts.
- **OSINT footprint URLs** - ready-made Google dorks, social searches, and **breach-check** links (Have I Been Pwned, DeHashed, Intelligence X).

One rich record per email. No login, no API key.

### A note on coverage (read this)

Email-registration enumeration has been **deliberately hardened across the industry** - most sites that once leaked "this email is registered" have closed that hole. So this Actor does **not** pretend to check 120 sites: it runs a **curated, live-validated set** of checks that genuinely still work, and is honest about the rest. The **Gravatar** lookup and the **footprint / breach-check URLs** always work and are where most of the OSINT value is. This is the realistic state of email OSINT in 2026.

### Example output

```json
{
  "type": "email",
  "email": "matt@mullenweg.com",
  "valid": true,
  "gravatar": {
    "exists": true,
    "profileUrl": "https://gravatar.com/...",
    "displayName": "Matt",
    "accounts": [{ "name": "wordpress", "url": "https://profiles.wordpress.org/..." }]
  },
  "registeredOn": ["WordPress.com", "Duolingo", "Firefox"],
  "registeredCount": 3,
  "checkedSites": 4,
  "footprintUrls": [
    { "kind": "breach", "name": "Have I Been Pwned", "url": "https://haveibeenpwned.com/account/matt%40mullenweg.com" },
    { "kind": "google", "name": "Google exact", "url": "https://www.google.com/search?q=%22matt%40mullenweg.com%22" }
  ]
}
```

| Field | Meaning |
|---|---|
| `valid` | Whether the address is syntactically a valid email |
| `gravatar` | Gravatar profile (exists, profile URL, display name, linked accounts) |
| `registeredOn` | Sites the email is registered on (empty if none found) |
| `registeredCount` / `checkedSites` | How many of the checked sites matched |
| `footprintUrls` | OSINT recon + breach-check URLs for the email |

### Input

| Field | Description |
|---|---|
| **Emails** | Email addresses to investigate (up to 2,000). |
| **Include OSINT footprint URLs** | Generate recon & breach-check URLs (on by default). |
| **Include adult (NSFW) sites** | Include adult sites in the registration checks (off by default). |
| **Proxy** | Residential proxies reduce rate-limiting. |

### Use cases

- **OSINT & investigations** - fingerprint an email: profile, registrations, breach leads.
- **Lead & account enrichment** - see whether a lead's email has real accounts and a public profile.
- **Fraud / due diligence** - check an address against Gravatar and breach directories in one step.

### Sibling actors

Pair this with **Sherlock / Maigret username scrapers** (accounts by username) and the **PhoneInfoga phone scraper** (numbers) for full OSINT coverage across handle, email and phone. For mailbox deliverability (MX, disposable, role, catch-all) see our **Bulk Email Verifier** - a different job from this account-discovery Actor.

### Run it from an agent (MCP / API)

Agent-ready: typed input schema, structured JSON output. An agent can call this Actor to enrich or investigate an email in one step. Pass `emails` and read the `email` records back.

### FAQ

**Does it need an API key?** No.
**Why so few checked sites?** Because email-registration enumeration is mostly closed now - this Actor only runs checks that still work, rather than reporting hundreds of dead ones. Gravatar + footprint carry the value.
**Is this legal?** It checks publicly observable signals and builds public search links. Use the results in line with each site's terms and applicable law.

# Actor input Schema

## `emails` (type: `array`):

One or more email addresses to investigate, e.g. <code>john@gmail.com</code>. Each is checked for site registrations, a Gravatar profile, and OSINT footprint URLs. Up to 2,000 per run.

## `includeFootprint` (type: `boolean`):

Generate reconnaissance and breach-check URLs (Google dorks, Have I Been Pwned, DeHashed, social search, Gravatar) for each email.

## `includeNsfw` (type: `boolean`):

Include adult-content sites in the registration checks. Off by default.

## `proxyConfiguration` (type: `object`):

Proxies used for the checks. Residential proxies reduce rate-limiting on some sites.

## Actor input object example

```json
{
  "emails": [
    "test@gmail.com"
  ],
  "includeFootprint": true,
  "includeNsfw": false,
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}
```

# Actor output Schema

## `results` (type: `string`):

All analysed email records as JSON items in the default dataset.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "emails": [
        "test@gmail.com"
    ],
    "proxyConfiguration": {
        "useApifyProxy": true
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("scrapesage/holehe-scraper").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "emails": ["test@gmail.com"],
    "proxyConfiguration": { "useApifyProxy": True },
}

# Run the Actor and wait for it to finish
run = client.actor("scrapesage/holehe-scraper").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "emails": [
    "test@gmail.com"
  ],
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}' |
apify call scrapesage/holehe-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,scrapesage/holehe-scraper"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/dH7OGgUbgpCFvMtnB/builds/n2isNL8nG77XYxukR/openapi.json