# Email Validator API – MX & Disposable Check $1.80/1K (`fluyeporlaweb/email-validator`) Actor

Validate emails in bulk: syntax, domain MX records via DNS, disposable/temporary domains, role accounts and typos. No emails sent, no SMTP probing, no login.

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

## Pricing

from $1.80 / 1,000 emails

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 API – Syntax, MX & Disposable Check

**Email validator** and API that checks every address for **valid syntax, a real domain with MX records (DNS), disposable / temporary email providers, role accounts (info@, sales@) and common domain typos** (gmial.com → gmail.com) — without sending any email or touching the mail server.

### What does it do?

- Syntax check (RFC 5322 dot-atom local part, IDNA domains, length limits).
- DNS check over DNS-over-HTTPS (Cloudflare, fallback Google): NXDOMAIN, MX records, null MX (RFC 7505), A-record fallback.
- Disposable domain detection with the open-source disposable-email-domains list (CC0, ~5,000 domains, fetched fresh each run, subdomains included).
- Flags role accounts, free webmail providers and typo domains with a suggestion.
- A clear status per email: valid, risky, invalid or unknown, with the reason.
- No SMTP "ping", no email sent: safe for your sender reputation.

### Use cases

- **Clean signup forms and CRMs** before importing leads.
- **Reduce bounces** before an email campaign.
- **Block throwaway accounts** (trial abuse) with the disposable flag.
- **Fix typos** like gmial.com at the point of capture.
- **AI agents and automations** (Make, Zapier, n8n) that need a quick email check.

### Input

| Field | Description |
|---|---|
| `emails` | Email addresses to validate (duplicates are removed). Example: info@apify.com |
| `concurrency` | Parallel domain lookups. Example: 10 |
| `maxItems` | Upper limit of emails checked per run. Example: 1000 |

Example input:

```json
{
  "emails": [
    "info@apify.com",
    "support@github.com",
    "test@mailinator.com",
    "hello@10minutemail.com",
    "sales@gmial.com",
    "not-an-email",
    "contact@this-domain-does-not-exist-fluye-123.com",
    "postmaster@wikipedia.org"
  ]
}
```

### Output

Real output (first items of a run on 26 Oct 2026):

```json
[
  {
    "email": "info@apify.com",
    "normalized": "info@apify.com",
    "isValidSyntax": true,
    "syntaxError": null,
    "domain": "apify.com",
    "domainExists": true,
    "hasMx": true,
    "mxRecords": [
      "aspmx.l.google.com",
      "alt1.aspmx.l.google.com",
      "alt2.aspmx.l.google.com",
      "aspmx2.googlemail.com",
      "aspmx3.googlemail.com"
    ],
    "isDisposable": false,
    "isRoleAccount": true,
    "isFreeProvider": false,
    "typoSuggestion": null,
    "status": "valid",
    "reason": "Syntax OK and domain accepts email (MX)"
  },
  {
    "email": "support@github.com",
    "normalized": "support@github.com",
    "isValidSyntax": true,
    "syntaxError": null,
    "domain": "github.com",
    "domainExists": true,
    "hasMx": true,
    "mxRecords": [
      "github-com.mail.protection.outlook.com"
    ],
    "isDisposable": false,
    "isRoleAccount": true,
    "isFreeProvider": false,
    "typoSuggestion": null,
    "status": "valid",
    "reason": "Syntax OK and domain accepts email (MX)"
  }
]
```

Export the results as JSON, CSV or Excel, read them through the API, or send them to Google Sheets, Make, Zapier, n8n or webhooks. You can also run this Actor from AI agents through the Apify MCP server.

### Pricing

Pay per event: **$1.80 per 1,000 emails** plus $0.00005 per run start. There is no extra platform usage charge.

### FAQ

**Does it send emails or connect to SMTP servers?** No. It only uses DNS and a public domain list, so it never contacts the mailbox. That also means it cannot confirm that a specific mailbox exists (catch-all domains look valid).

**What do the statuses mean?** valid = syntax OK and domain accepts mail; risky = disposable domain, typo domain or only an A record; invalid = bad syntax, domain does not exist, null MX or no mail records; unknown = DNS error.

**Where does the disposable list come from?** github.com/disposable-email-domains/disposable-email-domains (CC0), downloaded at the start of each run.

**How fast is it?** About 1,000 emails per minute; domains are cached within a run.

**Can I schedule it?** Yes, with Apify schedules, or call it from the API for each new signup.

**Do you store my emails?** Only in your own Apify dataset for the run.

**Do I need a login or API key?** No. It uses the source's public API; you only need an Apify account.

**Can AI agents use it?** Yes. Call it through the Apify API, or from Claude, Cursor or any MCP client via the Apify MCP server.

### Data source and license

Sources: DNS answers from public DNS-over-HTTPS resolvers (Cloudflare 1.1.1.1, Google Public DNS) and the [disposable-email-domains](https://github.com/disposable-email-domains/disposable-email-domains) list (CC0 1.0). Not affiliated with Cloudflare, Google or the list maintainers.

This Actor is not affiliated with or endorsed by the data source. You are responsible for using the data in line with the source's license and terms.

# Actor input Schema

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

Email addresses to validate (duplicates are removed). Example: info@apify.com

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

Parallel domain lookups. Example: 10

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

Upper limit of emails checked per run. Example: 1000

## Actor input object example

```json
{
  "emails": [
    "info@apify.com",
    "test@mailinator.com",
    "sales@gmial.com",
    "not-an-email"
  ],
  "concurrency": 10,
  "maxItems": 1000
}
```

# Actor output Schema

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

No description

## `summary` (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": [
        "info@apify.com",
        "test@mailinator.com",
        "sales@gmial.com",
        "not-an-email"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("fluyeporlaweb/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@apify.com",
        "test@mailinator.com",
        "sales@gmial.com",
        "not-an-email",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("fluyeporlaweb/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@apify.com",
    "test@mailinator.com",
    "sales@gmial.com",
    "not-an-email"
  ]
}' |
apify call fluyeporlaweb/email-validator --silent --output-dataset

```

## MCP server setup

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