# Bulk Email Verifier & Email Validator - SMTP Check (`leadproof/bulk-email-verifier`) Actor

Bulk email verifier and email validator. Verify email deliverability for a pasted list or chain it after any scraper - get ok / catch-all / invalid / disposable verdicts per address. Pay only per verified result.

- **URL**: https://apify.com/leadproof/bulk-email-verifier.md
- **Developed by:** [Lead Proof](https://apify.com/leadproof) (community)
- **Categories:** Lead generation, Automation
- **Features:** Limited permissions
- **Stats:** 74 total users, 39 monthly users, 97.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/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
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.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## 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.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# 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. Verification is powered by the Million Verifier service through its Apify provider. LeadProof covers the provider cost; you pay the price listed below.

### 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 are charged output rows, but do not trigger a provider verification.

### Pricing

**$0.0049 per result** (`apify-default-dataset-item`), which is $4.90 per 1,000 checks, plus $0.00005 per run start. There is no subscription and no verification account to set up.

Every row in the dataset is one charged result. Duplicate addresses are verified once and charged once. Malformed addresses are caught locally and returned as `invalid` / `malformed_syntax` rows, so they cost the same $0.0049 but never spend a verification attempt. If you set a maximum total charge on the run, the input is trimmed to the number of results the limit covers, valid addresses first.

There is no separate provider charge to your Apify account. Provider failures stop the run before billing any rows from the failed batch; results from earlier successful batches remain available. `SUMMARY.not_processed` reports addresses that were not completed because of a limit or failure. For large lists, use batches of 5,000 addresses to stay within the owner's verification safety limit.

The legacy `concurrency` and `mvTimeoutSeconds` inputs remain accepted. The managed provider controls its own concurrency and mailbox timeouts.

### 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.*

*Built by [LeadProof](https://leadproof.co) - verified local-business lead lists, built to order.*

# 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`):

Legacy direct-API setting. The managed verification provider controls its own concurrency.

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

Legacy direct-API setting. The managed verification provider controls mailbox timeouts.

## Actor input object example

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

# Actor output Schema

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

One item per email: email, result (ok / catch_all / invalid / disposable / unknown / error), quality, subresult, is_deliverable, free_provider, role_address, did_you_mean.

## `resultsCsv` (type: `string`):

The same verdicts as a CSV file, ready to filter on is_deliverable and import into your outreach tool.

## `summary` (type: `string`):

Totals by verdict for the whole run: how many addresses were ok, catch_all, invalid, disposable, unknown, malformed or errored.

# 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(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": [
    "john.doe@gmail.com",
    "contact@apify.com"
  ]
}' |
apify call leadproof/bulk-email-verifier --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,leadproof/bulk-email-verifier"
        }
    }
}
```

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/VsKXYxza3O0jRfIeH/builds/yqGu1KcKJED58sJlO/openapi.json