# Bulk Email Validator: MX, Disposable & Role Check (`lepidata/bulk-email-validator`) Actor

Check email lists at MX level: syntax, MX records, null MX, disposable (throwaway) domains and role addresses like info@ or sales@. DNS lookups only, no SMTP or mailbox probing. One verdict row per address.

- **URL**: https://apify.com/lepidata/bulk-email-validator.md
- **Developed by:** [Lepi Data](https://apify.com/lepidata) (community)
- **Security:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.20 / 1,000 email address checkeds

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

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

Check a list of email addresses at the MX level and get one verdict row per address. It's for cleaning signup forms, CRM imports and customer lists before you use them, and for spotting typos, dead domains and throwaway addresses.

**Input:** a list of email addresses (up to 50,000 per run).

**Output:** a verdict (`valid-mx`, `risky` or `invalid`) with reasons, plus syntax, MX record, null MX, disposable-domain, role-address and free-provider flags.

**This is an MX-level check.** It tells you whether an address is well formed and whether its domain is set up to receive mail. It never connects to a mail server, so it does not and cannot confirm that a particular mailbox exists. A `valid-mx` address can still bounce.

### Email validator input

- `emails`: one address per line, up to 50,000. Duplicates are skipped.
- `maxResults`: stop after this many checked addresses.

Addresses at `example.com` are the example input: each returns one free `EXAMPLE_INPUT` row, no lookup is made and nothing is charged. Replace them with your own list.

### What is checked

1. **Syntax:** RFC 5321/5322 dot-atom form, length limits, valid domain labels (international domains converted to punycode).
2. **Domain mail records (DNS):** MX records; a null MX (RFC 7505) means the domain accepts no mail; no MX but an A/AAAA record is reported as `risky`; no records or a non-existent domain is `invalid`.
3. **Disposable domains:** a bundled public-domain (CC0) list of about 10,000 throwaway-mail domains, subdomains included.
4. **Role addresses:** shared inboxes such as `info@`, `sales@`, `support@`, `noreply@`.
5. **Free providers:** flags common free mailbox domains (`gmail.com`, `outlook.com` ...). This flag does not change the verdict.

### Output fields

`input`, `email`, `domain`, `verdict`, `reasons`, `syntaxValid`, `hasMx`, `nullMx`, `mxHosts`, `disposable`, `role`, `freeProvider`, `note`

Verdicts: `valid-mx` (MX records found, not disposable, not a role address), `risky` (disposable domain, role address, or A record only), `invalid` (bad syntax, domain does not exist, null MX, or no mail records). When a DNS lookup fails or times out the row says `unknown` and is not charged.

Free rows (not charged): `EXAMPLE_INPUT`, `unknown` verdicts, `invalid-input`, `free-plan-limit`, `charge-limit-reached`.

**Example:** `{"emails":["jane@yourcompany.com","sales@yourcompany.com","someone@mailinator.com"]}`

### Data source and compliance

- DNS lookups only, once per domain per run. No SMTP connection, no port 25, no RCPT or VRFY probing, no mailbox checks.
- Your list is processed in memory and written only to the run's dataset. Nothing is stored anywhere else or reused between runs.
- Use it on lists you have the right to process, for example your own customers or signups. Follow the privacy and anti-spam laws that apply to you.
- Disposable-domain list: disposable-email-domains project, CC0 1.0 (public domain), bundled in the image.
- Free-plan accounts get up to 100 results per run.

**Pricing.** Pay per result: $0.20 per 1,000 addresses checked ($0.0002 each), the same price on every plan, no start fee. Free status rows are never charged.

# Actor input Schema

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

One address per line, up to 50,000. Duplicates are skipped. Addresses at example.com are the example input: they return one free EXAMPLE_INPUT row each and are never looked up or charged.

## `maxResults` (type: `integer`):

Stop after this many checked addresses (charged rows).

## Actor input object example

```json
{
  "emails": [
    "info@example.com"
  ],
  "maxResults": 50000
}
```

# Actor output Schema

## `items` (type: `string`):

All rows from this run.

# 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": [
        "info@example.com"
    ]
};

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

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

```

## MCP server setup

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