# Bulk Email Verifier - SMTP Validation (`leadproof/bulk-email-verifier`) Actor

Verify email deliverability in bulk. Paste a list or chain it after any scraper - get ok / catch-all / invalid / disposable verdicts per address.

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

## Pricing

from $4.90 / 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.

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 — SMTP Validation

Verify email deliverability in bulk, right inside your Apify workflow. Paste a list of addresses — or chain this Actor after any scraper — and get a clean verdict for every address: **deliverable, catch-all, invalid, disposable, or unknown**.

No API keys to manage, no verification account to set up. You pay only per verified result.

### Why verify?

Scraped email lists typically contain 10–40% undeliverable addresses. Sending to them destroys your sender reputation and gets your domain blacklisted. Verifying first means your outreach lands.

### How to use

**Option A — paste a list**: put your addresses in the *Email addresses* field and run.

**Option B — chain after a scraper**: run any scraper that outputs emails (Google Maps, website contact scrapers, etc.), then pass its **dataset ID** to this Actor. Set *Email field name* if the scraper uses a field other than `email`. Fields containing arrays of emails are handled automatically.

### Output

One dataset item per unique input address:

| Field | Meaning |
|---|---|
| `email` | The address (normalized: lowercased, trimmed, deduplicated) |
| `result` | `ok` · `catch_all` · `invalid` · `disposable` · `unknown` · `error` |
| `quality` | `good` · `bad` · `risky` |
| `subresult` | Detailed reason (e.g. `mailbox_not_found`, `malformed_syntax`) |
| `is_deliverable` | `true` only when `result` is `ok` — safe to send |
| `free_provider` | Address is on a free provider (gmail, yahoo, …) |
| `role_address` | Role-based address (info@, support@, …) |
| `did_you_mean` | Suggested correction for likely typos |

A run **SUMMARY** (totals by verdict) is saved to the key-value store and shown in the run status.

Malformed addresses are filtered locally and returned as `invalid` / `malformed_syntax` — they never count against verification.

### Notes

- **Fair use:** only submit email data you obtained and use lawfully (e.g. under GDPR/CAN-SPAM as applicable to you). You are responsible for the lists you verify.
- Duplicate addresses are verified once.
- `catch_all` domains accept all mail — deliverability can't be confirmed mailbox-by-mailbox. Treat as "risky".
- `unknown` means the mail server didn't respond in time; re-running just those addresses often resolves them.

***

*Looking for leads that come pre-verified? Try [Google Maps Leads with Verified Emails](https://apify.com/leadproof/google-maps-verified-leads) — B2B leads with SMTP-verified emails, review-count filtering, and dedup against your own CRM export. You pay only for delivered leads.*

# Actor input Schema

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

List of email addresses to verify. Use this, a dataset ID, or both.

## `datasetId` (type: `string`):

ID of a dataset produced by another Actor run (e.g. a Google Maps scraper). Emails are read from the field configured below.

## `emailField` (type: `string`):

Which field of each dataset item holds the email address. A field holding an array of emails works too.

## `concurrency` (type: `integer`):

How many verification requests run in parallel.

## `mvTimeoutSeconds` (type: `integer`):

How long a single mailbox check may take before returning 'unknown'.

## Actor input object example

```json
{
  "emails": [
    "john.doe@gmail.com",
    "contact@apify.com"
  ],
  "emailField": "email",
  "concurrency": 10,
  "mvTimeoutSeconds": 20
}
```

# 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",
        "contact@apify.com"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("leadproof/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",
        "contact@apify.com",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("leadproof/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",
    "contact@apify.com"
  ]
}' |
apify call leadproof/bulk-email-verifier --silent --output-dataset

```

## MCP server setup

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

```

## OpenAPI specification

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