# Bulk Email Verifier & Validator (MX, Disposable, Role) (`proper_ecosystem_cie/email-validator`) Actor

Validate email lists fast: syntax, domain and MX records, disposable/temporary domains, role-based addresses and free providers. Returns valid, risky or invalid with reasons. No SMTP probing.

- **URL**: https://apify.com/proper_ecosystem_cie/email-validator.md
- **Developed by:** [Proper Ecosystem Tools](https://apify.com/proper_ecosystem_cie) (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

$3.00 / 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: MX, Disposable & Role-Based Checker

Clean an email list before you send. Paste thousands of addresses and get back, for each one, whether it is **valid**, **risky**, or **invalid**, with the reasons. Fast, cheap, and safe: it never connects to the recipient's mail server, so it can't hurt your sender reputation or trip spam traps.

### What it checks

- **Syntax** (RFC 5322-style local part, valid domain, length limits)
- **Domain and MX records**: does the domain exist and accept mail (MX, null-MX, or A-record fallback)
- **Disposable / temporary email domains** (about 10,000 domains, from the CC0 community list [disposable-email-domains](https://github.com/disposable-email-domains/disposable-email-domains))
- **Role-based addresses** such as info@, sales@, support@, noreply@
- **Free providers** such as Gmail, Outlook, Yahoo (flag B2B lists that contain personal addresses)

It does **not** do SMTP mailbox probing, so it cannot confirm that a specific mailbox exists. Use it as a fast first pass that removes typos, dead domains, and throwaway addresses.

### Input

| Field | Description |
|---|---|
| `emails` | List of email addresses (one per line). Duplicates are removed. |
| `concurrency` | Parallel DNS lookups (default 20). |
| `maxItems` | Cap on unique emails processed. |

### Output (illustrative example, one item per email)

```json
{"email": "x@mailinator.com", "status": "risky", "reasons": ["disposable_domain"], "syntaxValid": true,
 "domain": "mailinator.com", "hasMx": true, "mxHosts": ["mail.mailinator.com"],
 "isDisposable": true, "isRoleAccount": false, "isFreeProvider": false}
```

`status` is `valid` (deliverable domain, no red flags), `risky` (disposable, role account, or A-record-only), or `invalid` (bad syntax, domain doesn't exist or doesn't accept mail). Export to CSV, Excel, or JSON, or call it from the API, Make, Zapier, n8n, or an AI agent via MCP.

### Pricing

Pay per validated email. Rows that fail because of a temporary DNS error are returned free with an `error` field. Set a max charge per run to cap spend.

### Use cases

Cold-email list hygiene, CRM cleanup, signup-form fraud filtering, lead-list QA before importing into HubSpot, Salesforce, Instantly, or Lemlist.

# Actor input Schema

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

One email per line. Duplicates are removed.

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

Parallel DNS lookups.

## `maxItems` (type: `integer`):

Stop after this many unique emails.

## Actor input object example

```json
{
  "emails": [
    "jane@example.com",
    "info@gmail.com"
  ],
  "concurrency": 20,
  "maxItems": 100000
}
```

# Actor output Schema

## `dataset` (type: `string`):

Dataset with one row per input item

## `runStats` (type: `string`):

Summary counts for the 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": [
        "jane@example.com",
        "info@gmail.com"
    ]
};

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

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

```

## MCP server setup

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