# Data Breach Checker (`intelscrape/data-breach-checker`) Actor

Check emails or passwords against Have I Been Pwned. Returns breach metadata only (never leaked values). Passwords use k-anonymity (free). Email checks need your optional HIBP API key. Includes demoMode fixtures.

- **URL**: https://apify.com/intelscrape/data-breach-checker.md
- **Developed by:** [IntelScrape](https://apify.com/intelscrape) (community)
- **Categories:** Developer tools, Automation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 1 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.00 / 1,000 dataset items

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

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

## Data Breach Checker

![Actor Banner](https://api.apify.com/v2/key-value-stores/PyvJzfQg02FD3RYhd/records/data-breach-checker-banner.png)

Check any **email** or **password** against known data breaches using the official **Have I Been Pwned** APIs. Returns *which* breaches, *when* they happened, and *what types* of data were exposed — **metadata only, never leaked values**.

- Passwords use **k-anonymity** (only the first 5 characters of the SHA-1 leave the run). Free, no API key.
- Email checks use the HIBP `breachedaccount` API with **your** optional API key (`hibpApiKey` input or `HIBP_API_KEY` env).
- **demoMode** pushes synthetic fixtures (no live HIBP calls) for Store try-outs.
- Billing: pay-per-event on each `pushData` dataset item.

### Inputs

| Field | Notes |
|---|---|
| `demoMode` | Synthetic fixtures; default false |
| `emails` | Addresses to check (needs HIBP key) |
| `passwords` | Checked free via k-anonymity (secret) |
| `hibpApiKey` | Optional HIBP key (secret); overrides env |
| `includeUnverified` | Include unverified breaches |
| `requestDelayMs` | Throttle between email checks |
| `maxBreachesListed` | Cap breach detail per email |

### Setup (email checks)

Get a key at [haveibeenpwned.com/API/Key](https://haveibeenpwned.com/API/Key) and pass it as `hibpApiKey` or set Actor env `HIBP_API_KEY`. Password checks and demoMode need **no key**.

### Compliance

- Official / consent-based HIBP APIs only — no stolen credential dumps, no hash markets, no illegal corpora.
- Returns breach **metadata** only (never leaked passwords or PII values).
- Check only addresses/passwords you have a legitimate reason to check.
- Not affiliated with Have I Been Pwned.

### SoftCTA mesh (SOFTCTA\_DEEPEN\_BREACH\_1\_0\_8)

Each result row includes a `softCta` object with next-step links to Email Finder, Contact, Website Leads, Maps Email, Watson, Phone Validator, TruePeopleSearch, and Skip Trace PRO. SoftCTA links only — no extra PPE events. Skip Trace PRO is SoftCTA-only (code frozen).

# Actor input Schema

## `demoMode` (type: `boolean`):

When true, pushes synthetic fixture results and does not call Have I Been Pwned. Use for Store try-outs. Default false.

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

Email addresses to check for breach exposure via HIBP breachedaccount. Requires hibpApiKey input or HIBP\_API\_KEY env var. Ignored in demoMode.

## `passwords` (type: `array`):

Passwords to check as a JSON array. Only the first 5 chars of the SHA-1 hash are sent (k-anonymity) — the password never leaves the run. No API key needed. Ignored in demoMode.

## `hibpApiKey` (type: `string`):

Your HIBP API key for email checks (haveibeenpwned.com/API/Key). Overrides HIBP\_API\_KEY env if set. Stored as a secret. Not required for password checks or demoMode.

## `includeUnverified` (type: `boolean`):

Include breaches HIBP has not fully verified.

## `requestDelayMs` (type: `integer`):

Throttle to respect your HIBP rate-limit tier (raise if you see 429s).

## `maxBreachesListed` (type: `integer`):

Cap the breach detail array per email (summary fields are always returned).

## Actor input object example

```json
{
  "demoMode": false,
  "emails": [
    "test@example.com"
  ],
  "includeUnverified": true,
  "requestDelayMs": 1600,
  "maxBreachesListed": 100
}
```

# Actor output Schema

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

Result rows pushed to 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@example.com"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("intelscrape/data-breach-checker").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@example.com"] }

# Run the Actor and wait for it to finish
run = client.actor("intelscrape/data-breach-checker").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@example.com"
  ]
}' |
apify call intelscrape/data-breach-checker --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,intelscrape/data-breach-checker"
        }
    }
}
```

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/YHrLdOspbSBpY7W9B/builds/FT2LiBJ2JiQN5Nrsa/openapi.json