# Bulk Email Verifier & Validator — MX, Disposable, Role Check (`poised_beardlichen/email-verifier-bulk`) Actor

Use this when you need to check if emails are well-formed and their domain can receive mail. $0.0003/email. Input: {"email":"jane@gmial.com"}. Output: status, score, reason, hasMx, disposable, roleAccount, didYouMean. Does NOT verify that the mailbox exists (no SMTP check).

- **URL**: https://apify.com/poised_beardlichen/email-verifier-bulk.md
- **Developed by:** [Isaac](https://apify.com/poised_beardlichen) (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

$0.30 / 1,000 email checkeds

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 & Validator: MX, Disposable and Role Check

**Clean your email list in seconds, before you send.** Paste thousands of addresses and get one result per email: valid syntax, whether the domain exists and accepts mail (MX records), **disposable or temporary inbox** detection (9,900+ known providers), **role addresses** (info@, sales@, support@), **free-provider** flag (Gmail, Yahoo, Outlook…), **typo suggestions** (`jane@gmial.com` → `jane@gmail.com`) and SPF/DMARC presence. Every address gets a simple **status** and a **0–100 score**.

- ⚡ **Fast:** 2,000 emails checked in about 5 seconds, with DNS results cached per domain
- 💸 **Cheap:** pay per email checked, no start fee, no subscription. Duplicates are removed for free
- 🧹 **Practical:** catches typos, dead domains and throwaway inboxes, the main causes of bounces and fake sign-ups
- 🤖 **Agent-ready:** simple input and output, fixed price per email, works from the API and the Apify MCP server

### What does it check?

| Check | Field |
|---|---|
| RFC syntax, length and international (IDN) domains | `syntaxValid` |
| Domain exists, MX records, null-MX, A-record fallback | `domainExists`, `hasMx`, `mxRecords` |
| Disposable / temporary email providers | `disposable` |
| Role or shared inboxes | `roleAccount` |
| Free webmail providers | `freeProvider` |
| Common domain typos | `didYouMean` |
| SPF and DMARC records | `hasSpf`, `hasDmarc` |

#### Status values

- `deliverable_domain`: the syntax is valid and the domain accepts email. **The individual mailbox is not tested** (see FAQ).
- `risky`: disposable provider, role address, probable typo, or no MX record.
- `undeliverable`: invalid syntax, the domain does not exist, or the domain refuses email.
- `unknown`: DNS timed out. Not common; re-run these addresses.

### Input example

```json
{ "emails": ["john.doe@gmail.com", "info@apify.com", "someone@mailinator.com", "jane@gmial.com"] }
```

### Output example

```json
{
  "email": "jane@gmial.com",
  "status": "risky",
  "score": 0,
  "reason": "possible typo, did you mean jane@gmail.com?",
  "domain": "gmial.com",
  "hasMx": false,
  "disposable": true,
  "roleAccount": false,
  "freeProvider": false,
  "didYouMean": "jane@gmail.com",
  "mailboxVerified": false
}
```

### Use it from the API or with AI agents

```bash
curl -X POST "https://api.apify.com/v2/acts/poised_beardlichen~email-verifier-bulk/run-sync-get-dataset-items?token=<YOUR_APIFY_TOKEN>" \
  -H "Content-Type: application/json" -d '{"emails": ["john.doe@gmail.com"]}'
```

AI agents can call it through the [Apify MCP server](https://mcp.apify.com) with `https://mcp.apify.com/?tools=poised_beardlichen/email-verifier-bulk`. It also works with Make, Zapier, n8n and Google Sheets through Apify integrations.

### Pricing

Pay per unique email checked, with no start fee. Set **Maximum cost per run** and the Actor stops cleanly at your limit.

### FAQ

**Does it check whether the mailbox really exists?** No. Mailbox checks need an SMTP connection on port 25, which cloud platforms block, and many big providers (Gmail, Outlook, Yahoo) don't reveal it reliably anyway. This Actor confirms that the address is well formed and that the domain can receive email, and it flags disposable, role and typo addresses. That is why `mailboxVerified` is always `false`. Tools that claim full mailbox checks charge much more.

**Where does the disposable list come from?** From the community-maintained, public-domain [disposable-email-domains](https://github.com/disposable-email-domains/disposable-email-domains) project, plus a free-provider list from [free-email-domains](https://github.com/Kikobeats/free-email-domains) (MIT).

**Is it safe for my list?** Yes. No email is ever sent to your contacts, and the Actor only performs DNS lookups on the domains. Results stay in your own Apify storage.

**How many emails can I check?** Up to 1,000,000 per run. Larger lists can be split across runs.

**Do duplicates cost extra?** No. With *Remove duplicates* on (the default), repeated addresses are skipped.

### Calling it from an AI agent or a script (async pattern)

A single email finishes in a few seconds; 10,000 emails take a few minutes. The Apify MCP server waits only about 30–45 seconds for a run before it returns. So for batches, slow pages, or whenever a call returns before the run is done, start the run and fetch the results afterwards rather than waiting on it:

1. **Start the run:** `POST https://api.apify.com/v2/acts/poised_beardlichen~email-verifier-bulk/runs` with input such as `{"email": "jane@gmial.com"}`. The response contains `data.id` (the run ID) and `data.defaultDatasetId`.
2. **Wait for it to finish:** poll `GET https://api.apify.com/v2/actor-runs/<runId>?waitForFinish=60` until `status` is `SUCCEEDED`.
3. **Fetch the results:** `GET https://api.apify.com/v2/datasets/<defaultDatasetId>/items?clean=true`.

Send your token as `Authorization: Bearer <APIFY_TOKEN>`. Through MCP, if the call returns a run ID instead of results, use the server's run-status and dataset tools (e.g. `get-actor-run`, then `get-dataset-items`) with that ID. For small, quick jobs you can use the synchronous endpoint `POST /v2/acts/poised_beardlichen~email-verifier-bulk/run-sync-get-dataset-items` instead, which waits for up to 300 seconds.

### Other tools by us

- [PDF to Text & Markdown with OCR](https://apify.com/poised_beardlichen/pdf-to-text-markdown-ocr): turn PDFs, DOCX and scans into clean, LLM-ready text.
- [Website Screenshot & PDF API](https://apify.com/poised_beardlichen/website-screenshot-pdf): bulk screenshots and PDFs with cookie banners removed.
- [Image to Text OCR API](https://apify.com/poised_beardlichen/image-to-text-ocr): extract text from PNG, JPEG, TIFF and WebP images in 27 languages, at $1.50 per 1,000 images.
- [Bulk PageSpeed & Lighthouse Checker](https://apify.com/poised_beardlichen/pagespeed-lighthouse-checker): Lighthouse scores, Core Web Vitals and top fixes for many URLs on mobile and desktop, from $0.005 per audit.
- [Website Screenshot & PDF for AI Agents](https://apify.com/poised_beardlichen/website-screenshot-pdf-agent): a lightweight copy of the screenshot tool for agents and one-off calls (no Standby). Same prices, starting at $0.0015 per screenshot.

### Support

Spotted a wrong result or a missing disposable domain? Open an issue on the **Issues** tab.

# Actor input Schema

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

Shortcut for one email address, e.g. "john.doe@gmail.com". Combined with the list below; provide at least one of the two.

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

Email addresses to check, one per line. Up to 1,000,000 per run. Use "email" instead for a single item.

## `deduplicate` (type: `boolean`):

Skip repeated addresses (case-insensitive), so you are not charged twice.

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

How many addresses to check at the same time.

## Actor input object example

```json
{
  "emails": [
    "john.doe@gmail.com",
    "info@apify.com",
    "someone@mailinator.com",
    "jane@gmial.com",
    "not-an-email",
    "user@this-domain-does-not-exist-xyz123.com"
  ],
  "deduplicate": true,
  "concurrency": 50
}
```

# Actor output Schema

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

No description

# 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",
        "someone@mailinator.com",
        "jane@gmial.com",
        "not-an-email",
        "user@this-domain-does-not-exist-xyz123.com"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("poised_beardlichen/email-verifier-bulk").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",
        "someone@mailinator.com",
        "jane@gmial.com",
        "not-an-email",
        "user@this-domain-does-not-exist-xyz123.com",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("poised_beardlichen/email-verifier-bulk").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",
    "info@apify.com",
    "someone@mailinator.com",
    "jane@gmial.com",
    "not-an-email",
    "user@this-domain-does-not-exist-xyz123.com"
  ]
}' |
apify call poised_beardlichen/email-verifier-bulk --silent --output-dataset

```

## MCP server setup

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

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/0ohmdXDk2BN11iKXv/builds/TjEvwpg7oQ1QyFVCS/openapi.json