# Bulk Email Validator - Syntax, Disposable, Typos, MX ($0.60/1k) (`mmaker-bot/apify-bulk-email-validator`) Actor

Validate email lists in bulk: syntax, typo suggestions, disposable and role addresses, DNS mail-server check, mail provider. No SMTP probing, no API key. AI-operated.

- **URL**: https://apify.com/mmaker-bot/apify-bulk-email-validator.md
- **Developed by:** [Kay Đặng](https://apify.com/mmaker-bot) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.60 / 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 Validator: syntax, typos, disposable, role and MX checks

Clean an email list in minutes: for each address you get a **result (ok / risky / invalid)**, a **0-100 score**, the reasons, a **"did you mean" fix** for typos like `gmial.com`, disposable and role-address flags, the **mail servers** of the domain and the **mail provider** (Google Workspace, Microsoft 365, Zoho...).

> This actor is built and operated by an AI agent (mmaker), with human oversight. Issues are read and fixed.

### What it checks (and what it does not)

| Check | Detail |
|---|---|
| Syntax | RFC-style local part and domain rules, length limits, IDN domains converted to punycode, `Name <a@b.com>` and `mailto:` cleaned |
| Domain DNS | MX lookup per domain (cached). No MX but an A record is flagged. Domains that do not exist, or publish a null MX, are invalid |
| Typos | Suggests a fix for near-misses of major providers (`gmial.com`, `hotmail.con`) |
| Disposable | 9,000+ throwaway domains (CC0 list `disposable-email-domains`), including subdomains |
| Role addresses | `info@`, `admin@`, `support@`, `noreply@`... |
| Provider | Google, Microsoft, Zoho, Proofpoint, Mimecast, Yahoo, GoDaddy and more, from the MX hosts |

**It does not open SMTP connections**, so it cannot prove that a specific mailbox exists or detect catch-all servers. Treat `ok` as "well-formed address on a domain that accepts mail", which removes the bulk of bounces (typos, dead domains, fake and throwaway addresses) at a fraction of the price of SMTP verifiers. If your sender reputation is critical, follow up with an SMTP verifier on the `ok` rows.

### How to use

1. Paste addresses into **Emails**, or paste a column / CSV text into **Emails as text**.
2. Click **Start**. Results land in a dataset you can download as JSON, CSV or Excel.
3. Keep `result = ok`, review `risky`, drop `invalid`.

### Input

| Field | Description |
|---|---|
| `emails` | List of addresses. Duplicates are skipped |
| `emailsText` | Text with addresses separated by new lines, commas, semicolons or spaces |
| `checkDns` | Default `true`. Turn off for a syntax, disposable and typo check only |
| `concurrency` | 1-100 parallel checks, default 25 |

### Output (one row per unique address)

```json
{"email":"bob@gmial.com","result":"risky","score":0,"reasons":["disposable_domain","possible_typo:gmail.com"],"local":"bob","domain":"gmial.com","isDisposable":true,"isRole":false,"isFreeProvider":false,"didYouMean":"bob@gmail.com","mxHosts":null,"mailProvider":null}
```

A `SUMMARY` record in the key-value store has the totals per result.

**Scoring.** Start at 100. Disposable -70, possible typo -45, role address -20, no MX record (A record only) -25, DNS error -30. Below 80 is `risky`; invalid syntax, unknown domains and null-MX domains are `invalid` (score 0).

### Sample inputs

**Four quick examples**

```json
{"emails":["anna@gmail.com","info@apify.com","test@mailinator.com","bob@gmial.com"]}
```

**Paste a CSV column, syntax and typo check only (fastest)**

```json
{"emailsText":"a@acme.io, b@acme.io; c@foo.co","checkDns":false}
```

**Large list, more parallelism**

```json
{"emails":["..."],"concurrency":60}
```

### Price guide

Pay per event: $0.0006 per email checked. Rough cost by volume:

| Emails | Cost |
|---|---|
| 1,000 | $0.60 |
| 10,000 | $6.00 |
| 100,000 | $60.00 |

The Apify free plan includes monthly credit, enough to try it. Set a maximum charge per run in the run options to cap spend.

### FAQ

**How much does it cost?** $0.60 per 1,000 emails checked, billed per unique address. Duplicates in your input are skipped and free.

**Is it as accurate as SMTP verification?** No, and it says so. It catches typos, fake domains, throwaway and role addresses. It cannot confirm that a mailbox exists.

**Are my emails stored or shared?** The actor processes your list in your run only; results stay in your Apify dataset. DNS queries contain only the domain part.

**Why is a typo domain like `gmial.com` also "disposable"?** Some typo domains appear on the public disposable list. Either way the row is `risky` and `didYouMean` shows the fix.

**Can I schedule it or call it by API?** Yes. Use Apify schedules, the API, or Make, Zapier and n8n integrations.

**Is it legal?** The actor does not contact mail servers or recipients. You are responsible for how you use email addresses, including GDPR, CAN-SPAM and anti-spam rules.

# Actor input Schema

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

Email addresses to check. Forms like "Jane <jane@acme.io>" and "mailto:" links are cleaned up. Duplicates are skipped.

## `emailsText` (type: `string`):

Optional. Paste a whole column or CSV text; addresses can be separated by new lines, commas, semicolons or spaces.

## `checkDns` (type: `boolean`):

Look up MX records for every domain (cached per domain). Turn off for a syntax, disposable and typo check only.

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

Parallel checks, 1-100.

## Actor input object example

```json
{
  "emails": [
    "anna@gmail.com",
    "info@apify.com",
    "test@mailinator.com",
    "bob@gmial.com"
  ],
  "checkDns": true,
  "concurrency": 25
}
```

# Actor output Schema

## `overview` (type: `string`):

No description

## `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": [
        "anna@gmail.com",
        "info@apify.com",
        "test@mailinator.com",
        "bob@gmial.com"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("mmaker-bot/apify-bulk-email-validator").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": [
        "anna@gmail.com",
        "info@apify.com",
        "test@mailinator.com",
        "bob@gmial.com",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("mmaker-bot/apify-bulk-email-validator").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": [
    "anna@gmail.com",
    "info@apify.com",
    "test@mailinator.com",
    "bob@gmial.com"
  ]
}' |
apify call mmaker-bot/apify-bulk-email-validator --silent --output-dataset

```

## MCP server setup

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

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/1aiXh64VIdLv6offM/builds/rHYkKdyaQSeAcg8oV/openapi.json