# Email Verifier — Bulk List Cleaning & Deliverability Check (`seemuapps/bulk-email-verifier`) Actor

Verify email addresses in bulk: syntax, MX records, disposable domains, role accounts, and live SMTP deliverability checks for clean, sendable lists.

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

## Pricing

$1.80 / 1,000 email verifieds

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

## Email Verifier — Bulk List Cleaning & Deliverability Check

Clean a list of email addresses before you send to it — syntax, MX records, disposable domains, role accounts, and live SMTP deliverability, all in one pass.

### What you get

- **Syntax check** — catches malformed addresses instantly
- **MX record check** — confirms the domain actually accepts mail (including RFC 7505 "null MX" domains that explicitly reject all mail)
- **Live SMTP deliverability check** — connects to the real mail server and asks whether the specific mailbox exists, catching typos and dead addresses that pass a syntax/MX-only check
- **Disposable domain detection** — flags mailinator.com, guerrillamail.com, and 50,000+ other throwaway domains
- **Role account detection** — flags info@, admin@, support@, sales@ and similar shared inboxes
- **Catch-all domain detection** (optional) — flags domains that accept mail for any address, which makes deliverability unverifiable for a single mailbox
- Final `status` per email: `valid`, `invalid`, `risky`, or `unknown`

### Use cases

- Scrub a purchased or scraped lead list before an email campaign
- Reduce bounce rate and protect sender reputation before a cold-outbound send
- Validate signup-form emails in a batch backfill
- Deduplicate and grade an email list by deliverability confidence

### How to use

1. Paste your list into **Emails** (one per line)
2. Leave **Check SMTP deliverability** on for the most accurate results (some networks block outbound SMTP — those checks report `unknown` rather than failing)
3. Optionally enable **Check for catch-all domains** to catch domains where SMTP can't tell you a specific mailbox is real
4. Run the actor — results appear in the **Dataset** tab

### Output format

Each dataset record:

```json
{
  "email": "someone@example.com",
  "isValidSyntax": true,
  "domain": "example.com",
  "hasMxRecord": true,
  "mxHost": "mail.example.com",
  "isDisposable": false,
  "isRoleAccount": false,
  "smtpCheck": "deliverable",
  "isCatchAll": false,
  "status": "valid",
  "reason": "verified_deliverable"
}
```

`status` is the field to filter/sort on: `valid` (safe to send), `risky` (disposable, role-based, or catch-all — send with caution), `invalid` (bad syntax, no mail server, or the mailbox doesn't exist), `unknown` (deliverability couldn't be confirmed, usually because the target mail server didn't respond to the SMTP check).

# Actor input Schema

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

List of email addresses to verify, one per line.

## `checkSmtp` (type: `boolean`):

Connect to each domain's mail server and check whether the mailbox actually accepts mail (in addition to syntax and MX checks). Slower, but catches invalid mailboxes that pass MX-only checks. Some networks block outbound SMTP, in which case results fall back to 'unknown' for that check.

## `checkCatchAll` (type: `boolean`):

For domains that accept the mail, also probe a random nonexistent mailbox at the same domain. If it's also accepted, the domain is catch-all and the address is marked risky instead of valid. Adds one extra SMTP check per unique domain. Requires 'Check SMTP deliverability' to be on.

## Actor input object example

```json
{
  "emails": [
    "test@gmail.com"
  ],
  "checkSmtp": true,
  "checkCatchAll": false
}
```

# Actor output Schema

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

One record per email. Fields: email, isValidSyntax, domain, hasMxRecord, mxHost, isDisposable, isRoleAccount, smtpCheck, isCatchAll, status (valid/invalid/risky/unknown), reason.

# 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"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("seemuapps/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": ["test@gmail.com"] }

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

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,seemuapps/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/DNGVDWWDO9uaWhsrV/builds/x5pu91dQTlUTBlh3P/openapi.json