# Bulk Email Validator – Syntax, MX, Disposable & Typos (`siftwright/email-validator-mx-disposable`) Actor

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

## Pricing

from $0.80 / 1,000 email validateds

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 Validator – Syntax, MX, Disposable & Typos

Clean an email list before you send. For every address you get one JSON row with a **verdict** (`deliverable`, `risky`, `undeliverable` or `invalid`), the **reason**, the domain's **live MX records**, and flags for **disposable** domains, **role** addresses (info@, support@), **free providers** and **likely typos** with a corrected suggestion (`someone@gmial.com` → `someone@gmail.com`).

It checks syntax and the domain's DNS mail routing. It does **not** open SMTP connections to mailboxes (see Limits), so it is fast, deterministic and cheap.

### What you get

| Field | Meaning |
|---|---|
| `verdict` | `deliverable`, `risky`, `undeliverable`, `invalid` or `unknown` |
| `reason` | `domain_not_found`, `no_mail_server`, `null_mx`, `disposable`, `possible_typo`, `role_address`, `invalid_local_part`, ... |
| `valid` | Whether the domain can receive mail at all |
| `mx` | Up to 5 MX hosts with priority |
| `disposable`, `role`, `freeProvider`, `plusTag` | Flags |
| `suggestion` | Corrected address when the domain looks mistyped |

### Real output

Input: 8 addresses (one duplicate-by-case, one malformed). Real run on Apify:

| email | verdict | reason |
|---|---|---|
| support@stripe.com | risky | role\_address |
| jane@github.com | deliverable | |
| sam@apify.com | deliverable | |
| test@mailinator.com | risky | disposable |
| someone@gmial.com | risky | possible\_typo (suggests someone@gmail.com) |
| nobody@this-domain-does-not-exist-siftwright.com | undeliverable | domain\_not\_found |
| bad@@x | invalid | invalid\_local\_part |

7 of the 8 rows were charged (the malformed address was free).

### Pricing

Pay per event: **$0.80 per 1,000 emails** ($0.0008 each) plus Apify's $0.00005 start event.

- Charged once per unique address that gets a definitive verdict.
- **Free:** invalid syntax, duplicates, and inconclusive DNS lookups (timeouts/SERVFAIL).
- Set a maximum cost per run and the Actor stops exactly at the limit.

### How it compares

| | This Actor | Typical SMTP-probe verifiers |
|---|---|---|
| Price per 1,000 | $0.80 | $0.85-$2.50 plus start fees on some |
| Detects disposable / role / typos | Yes | Varies |
| Mailbox-level check | No | Sometimes |
| Failed lookups free | Yes | Varies |

### Limits (honest)

- **No mailbox-level verification.** `deliverable` means the address is well-formed and its domain publishes mail routing. It cannot confirm that a specific inbox exists; many providers (Gmail, Microsoft 365) block or mask SMTP probes, and outbound port 25 is typically blocked on cloud hosts.
- The disposable-domain list is a hand-maintained best-effort list of several hundred well-known services, not an exhaustive database; new throwaway domains appear daily.
- Catch-all domains look `deliverable`.

### Use it from code

```python
from apify_client import ApifyClient
client = ApifyClient("<APIFY_TOKEN>")
run = client.actor("siftwright/email-validator-mx-disposable").call(run_input={"emails": ["jane@github.com", "someone@gmial.com"]})
for row in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(row["email"], row["verdict"], row["reason"])
```

```bash
curl -X POST "https://api.apify.com/v2/acts/siftwright~email-validator-mx-disposable/run-sync-get-dataset-items?token=<APIFY_TOKEN>" \
  -H "Content-Type: application/json" -d '{"emails":["jane@github.com","someone@gmial.com"]}'
```

Works with Apify's MCP server, so AI agents can call it as a tool.

### FAQ

**Why is `support@stripe.com` "risky"?** Role addresses are shared inboxes: valid, but they rarely reach a person and hurt cold-email metrics.
**Do you store my list?** No. Input and results live in your own Apify run storage.

Built by [Siftwright](https://siftwright.com). Questions: support@siftwright.com.

# Actor input Schema

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

One address per line. "Name <a@b.com>" and mailto: forms are accepted. Duplicates are checked and charged once.

## `checkMx` (type: `boolean`):

Look up the domain's mail servers. Turn off for a syntax-only check.

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

How many addresses to check at the same time.

## `timeoutSecs` (type: `integer`):

How long to wait for each DNS answer. Inconclusive lookups are free.

## Actor input object example

```json
{
  "emails": [
    "support@stripe.com",
    "someone@gmial.com",
    "test@mailinator.com",
    "nobody@this-domain-does-not-exist-siftwright.com"
  ],
  "checkMx": true,
  "maxConcurrency": 20,
  "timeoutSecs": 8
}
```

# Actor output Schema

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

One row per unique address with verdict, reason, MX records and flags.

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

Totals, duplicates, charged count and verdict breakdown.

# 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": [
        "support@stripe.com",
        "someone@gmial.com",
        "test@mailinator.com",
        "nobody@this-domain-does-not-exist-siftwright.com"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("siftwright/email-validator-mx-disposable").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": [
        "support@stripe.com",
        "someone@gmial.com",
        "test@mailinator.com",
        "nobody@this-domain-does-not-exist-siftwright.com",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("siftwright/email-validator-mx-disposable").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": [
    "support@stripe.com",
    "someone@gmial.com",
    "test@mailinator.com",
    "nobody@this-domain-does-not-exist-siftwright.com"
  ]
}' |
apify call siftwright/email-validator-mx-disposable --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,siftwright/email-validator-mx-disposable"
        }
    }
}
```

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/ffEzCXaDbrMoHVyqT/builds/KbvJ9uHjnZMsMEKcU/openapi.json