# Email Validator: Syntax, MX, Disposable & Role Check (`dodge_bot/email-validator`) Actor

Clean an email list in bulk: syntax check, does the domain exist and accept mail (MX records), disposable/throwaway providers, role addresses like info@, free providers like Gmail, and typo suggestions (gmial.com). No emails are sent and mailboxes are not probed.

- **URL**: https://apify.com/dodge\_bot/email-validator.md
- **Developed by:** [Dodge Sucharda](https://apify.com/dodge_bot) (community)
- **Categories:** Lead generation, Marketing
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

Pay per event

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

## Email Validator: Syntax, MX, Disposable & Role Check

Clean an email list before you send to it. For each address you get a verdict (`valid`, `risky` or `invalid`) with the reasons: bad syntax, a domain that doesn't exist or can't receive email, disposable (throwaway) providers, role addresses such as info@ or sales@, free providers such as Gmail, and typo fixes such as gmial.com → gmail.com.

**$1 per 1,000 addresses.** Invalid addresses are charged (finding them is the point); temporary DNS failures are free.

### Good for

- Cleaning sign-up forms and CRM exports to cut bounces
- Filtering lead lists before outreach
- Separating business addresses from free and throwaway ones

### Output (one row per address, shortened)

```json
{
  "input": "bob@gmial.com",
  "email": "bob@gmial.com",
  "verdict": "risky",
  "reasons": ["possible typo, did you mean bob@gmail.com?"],
  "syntaxValid": true,
  "mailServer": true,
  "disposable": false,
  "roleAccount": false,
  "freeProvider": false,
  "typoSuggestion": "bob@gmail.com"
}
```

| Verdict | Meaning |
|---|---|
| `valid` | Correct syntax, and the domain has a working mail setup |
| `risky` | Deliverable domain, but disposable, a role address, or a likely typo |
| `invalid` | Bad syntax, the domain doesn't exist, has no mail server, or declares it takes no email (null MX) |
| `unknown` | DNS didn't answer (not charged); try again later |

### What it does not do

- **It does not check whether the mailbox itself exists.** That needs connecting to the recipient's mail server, which many providers block or treat as abuse; this tool never does it. An address can pass here and still bounce if the person left the company.
- The disposable list covers hundreds of well-known providers, but new throwaway domains appear every day.
- No emails are sent.

# Actor input Schema

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

One address per line, up to 100,000 per run. Duplicates are removed.

## Actor input object example

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

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

// Run the Actor and wait for it to finish
const run = await client.actor("dodge_bot/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": [
        "jane.doe@gmail.com",
        "info@apify.com",
        "someone@mailinator.com",
        "bob@gmial.com",
    ] }

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

```

## MCP server setup

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