# Bulk Email Verifier — MX, Disposable & Deliverability (`haketa/bulk-email-verifier`) Actor

Verify thousands of emails at once: syntax, MX/domain check, disposable & role-based detection, free-provider flag and a deliverability score. Fast, cheap, keyless bulk email validation for lead lists and list cleaning.

- **URL**: https://apify.com/haketa/bulk-email-verifier.md
- **Developed by:** [Haketa](https://apify.com/haketa) (community)
- **Categories:** Lead generation, Automation, Developer tools
- **Stats:** 1 total users, 0 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.70 / 1,000 results

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/platform/actors/running/actors-in-store#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

## Bulk Email Verifier — Syntax, MX, Disposable & Deliverability

Verify **thousands — or millions — of emails at once.** Paste a list and get, for every address: **syntax validity, MX/domain check, disposable & role-based detection, free-provider flag, and a deliverability score** with a clear valid / risky / invalid status.

Fast, cheap and keyless — clean your lead lists before you send, and cut bounces.

***

### Why this Actor?

A dirty email list wrecks your sender reputation: hard bounces, spam traps and wasted sends. Verifying emails one by one is slow, and most tools charge per credit. This Actor cleans a whole list at once — DNS-based, so it's fast and inexpensive at scale — and tells you exactly which addresses are safe to send to.

- **Clean lead lists** before an outreach or newsletter campaign.
- **Cut bounce rate** and protect sender reputation.
- **Enrich a CRM** with deliverability status and flags.
- **Filter forms/signups** by catching disposable and role-based addresses.

***

### What you get

One record per email:

| Field | Description |
| --- | --- |
| `email` | The address |
| `status` | `valid`, `risky`, or `invalid` |
| `isValid` | Whether it's a valid, deliverable address |
| `deliverabilityScore` | 0–100 confidence score |
| `reason` | Why this status |
| `domain` | Email domain |
| `syntaxValid` | Passes RFC syntax |
| `hasMx` | Domain has MX records (can receive mail) |
| `mxHost` | Primary mail server |
| `isDisposable` | Disposable / temporary domain |
| `isRoleBased` | Role address (info@, admin@, sales@…) |
| `isFreeProvider` | Free provider (Gmail, Yahoo, Outlook…) |
| `scrapedAt` | Timestamp |

***

### Example output

```json
{
  "email": "ceo@microsoft.com",
  "status": "valid",
  "isValid": "true",
  "deliverabilityScore": "92",
  "reason": "deliverable",
  "domain": "microsoft.com",
  "syntaxValid": "true",
  "hasMx": "true",
  "mxHost": "microsoft-com.mail.protection.outlook.com",
  "isDisposable": "false",
  "isRoleBased": "false",
  "isFreeProvider": "false",
  "scrapedAt": "2026-07-08T15:00:00.000Z"
}
```

- `bad@nonexistent-domain.com` → **invalid** (no MX — the domain can't receive mail).
- `test@mailinator.com` → **risky** (disposable domain).
- `info@company.com` → **risky** (role-based).
- `john@gmail.com` → **valid** (free provider).

***

### How the status is decided

| Status | Meaning |
| --- | --- |
| **invalid** | Bad syntax, or the domain has no MX record (cannot receive mail) — don't send. |
| **risky** | Deliverable domain but disposable or role-based — send with caution. |
| **valid** | Good syntax + real mail domain, not disposable, not role — safe to send. |

The `deliverabilityScore` (0–100) gives you a single number to threshold on.

***

### Input

| Field | Type | Default | Description |
| --- | --- | --- | --- |
| `emails` | array | — | **Required.** The emails to verify (thousands to millions). |
| `checkDisposable` | boolean | `true` | Flag disposable/temporary domains against an up-to-date blocklist of 7,900+ domains. |
| `maxConcurrency` | integer | `50` | Emails verified in parallel. |

#### Example

```json
{
  "emails": ["john@gmail.com", "info@company.com", "test@mailinator.com"],
  "checkDisposable": true
}
```

***

### Use cases in detail

#### 1. Clean a lead list before outreach

Run your list, keep `status: valid`, drop `invalid`, and review `risky` — you'll cut bounces dramatically and protect your domain's reputation.

#### 2. Reduce newsletter bounce rate

Verify subscribers before a big send; remove dead domains and disposables.

#### 3. Enrich & segment a CRM

Add `deliverabilityScore`, `isFreeProvider` and `isRoleBased` to segment personal vs business vs role contacts.

#### 4. Signup / form hygiene

Catch disposable and role addresses at the point of collection.

***

### How to use it

1. Click **Try for free**.
2. Paste your emails.
3. Click **Start**.
4. Export results as **JSON, CSV, Excel**, or via the Apify API.

Runs are fast — domains are cached, so a big list resolves in seconds.

***

### Calling from the API

```bash
curl -X POST "https://api.apify.com/v2/acts/YOUR_ACTOR_ID/runs?token=YOUR_APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{ "emails": ["john@gmail.com", "test@mailinator.com"] }'
```

Then fetch the dataset:

```bash
curl "https://api.apify.com/v2/acts/YOUR_ACTOR_ID/runs/last/dataset/items?token=YOUR_APIFY_TOKEN&format=csv"
```

Works with webhooks, Zapier, Make and n8n.

***

### Frequently asked questions

**How does it check deliverability without sending?**
It validates syntax, checks the domain's MX records (whether it can receive mail at all), and flags disposable, role-based and free-provider addresses. This catches the large majority of bad addresses reliably.

**Does it do SMTP mailbox verification?**
No — SMTP mailbox probing requires port 25 (blocked on virtually all cloud/hosting networks) and is unreliable anyway (catch-all domains, greylisting, false positives). This Actor gives you honest, fast, DNS-based verification instead of a flaky SMTP guess.

**How many emails can it handle?**
Thousands to millions — domains are cached, so unique-domain lookups (not per-email) drive the work.

**What's a role-based address?**
Addresses like `info@`, `admin@`, `sales@` that go to a team, not a person — often lower engagement and higher spam-complaint risk.

**Is the disposable list current?**
Yes — it fetches an up-to-date community blocklist (7,900+ domains) on each run, with a built-in fallback.

***

### Tips

- **Threshold on `deliverabilityScore`** (e.g. keep ≥ 80) for a quick clean.
- **Keep `valid`, drop `invalid`, review `risky`** for the safest list.
- **Filter `isRoleBased` / `isFreeProvider`** to separate business from personal contacts.

***

### Notes

This Actor performs DNS/MX lookups and pattern checks on the emails you provide. It does not send mail. Verify that you have the right to process the email addresses you submit, in line with applicable privacy laws (GDPR/CAN-SPAM etc.).

***

### Support

Want catch-all detection, SMTP (where possible), or another flag? Open an issue from the Actor's page.

# Actor input Schema

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

Paste the email addresses you want to verify — one per line. Handles anything from a handful to millions. Leave this empty to run a quick demo on a sample list and see exactly what the results look like.

## `checkDisposable` (type: `boolean`):

Catch throwaway and temporary addresses by matching against an up-to-date blocklist of thousands of disposable domains. Recommended for cleaning lead lists.

## `maxConcurrency` (type: `integer`):

How many emails to verify at the same time. Higher is faster; lower is gentler. The default works well for most lists.

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

Apify Proxy. Off by default — email verification runs over DNS and does not need a proxy.

## Actor input object example

```json
{
  "emails": [
    "john.doe@gmail.com",
    "info@apify.com",
    "sales@microsoft.com",
    "test@mailinator.com",
    "nobody@thisdomaindoesnotexist-xyz9.com"
  ],
  "checkDisposable": true,
  "maxConcurrency": 50,
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}
```

# Actor output Schema

## `email` (type: `string`):

The email

## `status` (type: `string`):

valid / risky / invalid

## `isValid` (type: `string`):

Whether it's a valid deliverable address

## `deliverabilityScore` (type: `string`):

Deliverability score 0-100

## `reason` (type: `string`):

Why this status

## `domain` (type: `string`):

Email domain

## `syntaxValid` (type: `string`):

Syntax valid

## `hasMx` (type: `string`):

Domain has MX records

## `mxHost` (type: `string`):

Primary mail server

## `isDisposable` (type: `string`):

Disposable/temporary domain

## `isRoleBased` (type: `string`):

Role address (info@, admin@…)

## `isFreeProvider` (type: `string`):

Free provider (gmail, yahoo…)

## `scrapedAt` (type: `string`):

Timestamp

# 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": [
        "john.doe@gmail.com",
        "info@apify.com",
        "sales@microsoft.com",
        "test@mailinator.com",
        "nobody@thisdomaindoesnotexist-xyz9.com"
    ],
    "maxConcurrency": 50
};

// Run the Actor and wait for it to finish
const run = await client.actor("haketa/bulk-email-verifier").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": [
        "john.doe@gmail.com",
        "info@apify.com",
        "sales@microsoft.com",
        "test@mailinator.com",
        "nobody@thisdomaindoesnotexist-xyz9.com",
    ],
    "maxConcurrency": 50,
}

# Run the Actor and wait for it to finish
run = client.actor("haketa/bulk-email-verifier").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print("💾 Check your data here: https://console.apify.com/storage/datasets/" + run["defaultDatasetId"])
for item in client.dataset(run["defaultDatasetId"]).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": [
    "john.doe@gmail.com",
    "info@apify.com",
    "sales@microsoft.com",
    "test@mailinator.com",
    "nobody@thisdomaindoesnotexist-xyz9.com"
  ],
  "maxConcurrency": 50
}' |
apify call haketa/bulk-email-verifier --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "command": "npx",
            "args": [
                "mcp-remote",
                "https://mcp.apify.com/?tools=haketa/bulk-email-verifier",
                "--header",
                "Authorization: Bearer <YOUR_API_TOKEN>"
            ]
        }
    }
}

```

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/acts/w0c4VUcwFVb0wMCbM/builds/HskeA2aiF5Y9q0n8f/openapi.json