# Email Verifier (Syntax, MX, Disposable, Role) (`skilled_glee/email-verifier`) Actor

Check email lists without sending mail: syntax, domain MX records, null MX, disposable domains, role accounts, free providers and common typos, with a pass/risky/fail verdict and reason codes. Does not connect to mail servers and does not confirm that a mailbox exists.

- **URL**: https://apify.com/skilled_glee/email-verifier.md
- **Developed by:** [EchoEmpire Machine Foundry (EchoEmpire LLC)](https://apify.com/skilled_glee) (community)
- **Categories:** Lead generation, Developer tools, Automation
- **Security:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$1.00 / 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

## Email Verifier (Syntax, MX, Disposable, Role)

Email list in, one row per address out: is it well-formed, can its domain receive mail (MX records), is it a disposable domain, a role account (`info@`, `sales@` …), a free provider, or a likely typo (`gmial.com`). Each row gets a `pass` / `risky` / `fail` verdict with reason codes.

### Read this first: what this Actor does NOT do

- It does **not** connect to any mail server (no SMTP, no `RCPT TO` probing) and sends no email.
- It therefore **cannot tell whether a specific mailbox exists**, is full, or will accept a message, and it cannot detect catch-all (accept-all) domains. Every row has `"mailboxVerified": false` to make that explicit.
- `pass` means: the address is well-formed, its domain publishes MX records, and it is not on the disposable list or a role account. A `pass` address can still bounce.

If you need mailbox-level confirmation, use a dedicated SMTP verification service. Use this Actor to cheaply clean a list first: drop `fail` rows, review `risky` rows, then send what is left to a paid mailbox checker or your ESP.

| | |
|---|---|
| Input | `emails[]` (1–10,000 per run) |
| Output per email | `verdict`, `reasons[]`, `syntaxValid`, `syntaxError`, `normalizedEmail`, `domain`, `dnsStatus`, `hasMx`, `mxHosts[]`, `mxProvider`, `disposable`, `role`, `freeProvider`, `didYouMean`, `mailboxVerified` (always `false`) |
| Pricing | $0.001 per email checked ($1 / 1,000). Rows whose DNS lookup failed (`unknown`) are not billed. |
| Access | DNS over HTTPS (Cloudflare, Google fallback). No mail server is contacted. |
| Call it | REST `skilled_glee~email-verifier` · MCP `https://mcp.apify.com/?tools=skilled_glee/email-verifier` |

Pipeline role (n8n / agents): **Lead gen → Verify**: find → [Contact Details Extractor](https://apify.com/skilled_glee/contact-details-extractor) → Email Verifier → CRM. Full catalog: [EchoEmpire Machine Foundry llms.txt](https://foundry.echoempire.org/llms.txt).

### Input

```json
{
  "emails": ["support@apify.com", "jane.doe@gmail.com", "someone@gmial.com", "test@mailinator.com", "bad-address@", "user@no-such-domain-ee-test-1234.com", "info@example.com"]
}
```

### Output

Rows from a real run (2026-10-29; the last two rows are abridged):

```json
{"email": "jane.doe@gmail.com", "normalizedEmail": "jane.doe@gmail.com", "domain": "gmail.com", "syntaxValid": true, "syntaxError": null, "dnsStatus": "mx_found", "hasMx": true, "mxHosts": ["gmail-smtp-in.l.google.com", "alt1.gmail-smtp-in.l.google.com"], "mxProvider": "google", "disposable": false, "role": false, "freeProvider": true, "didYouMean": null, "verdict": "pass", "reasons": [], "mailboxVerified": false}
{"email": "info@example.com", "domain": "example.com", "dnsStatus": "null_mx", "hasMx": false, "role": true, "verdict": "fail", "reasons": ["null_mx", "role_account"], "mailboxVerified": false}
{"email": "test@mailinator.com", "dnsStatus": "mx_found", "disposable": true, "verdict": "risky", "reasons": ["disposable_domain"], "mailboxVerified": false}
```

#### Verdicts

| `verdict` | Meaning |
|---|---|
| `pass` | Well-formed, domain has MX records, not disposable, not a role account, no typo hint. **Not** a mailbox confirmation. |
| `risky` | Domain can receive mail, but: `role_account`, `disposable_domain`, `possible_typo`, or `no_mx_a_record_only` (no MX, mail would go to the domain's A record). |
| `fail` | `syntax_*`, `domain_not_found` (NXDOMAIN), `null_mx` (domain says it accepts no mail, RFC 7505), or `no_mail_route` (no MX, A or AAAA). |
| `unknown` | DNS lookup failed after retries (`dns_error`). Not billed. |

#### `dnsStatus`

`mx_found` · `a_record_fallback` · `null_mx` · `domain_not_found` · `no_mail_route` · `dns_error` · `null` (syntax failed, no lookup).

Other fields: `mxProvider` is a label from the MX host names (`google`, `microsoft`, `zoho`, `proton`, `mimecast`, `proofpoint`, … or `other`). `role` matches the local part (before any `+tag`) against common role names. `disposable` uses the CC0 [disposable-email-domains](https://github.com/disposable-email-domains/disposable-email-domains) list (bundled, ~10k domains, subdomains included). `didYouMean` covers common misspellings of big free providers.

`SUMMARY` in the default key-value store has verdict counts, emails charged and whether a spending limit stopped the run.

### Pricing (pay per event)

| Event | When | Price |
|---|---|---|
| `email-checked` | Once per unique email with a `pass`, `risky` or `fail` verdict saved to the dataset | $0.001 |

No start fee. Duplicates are checked and billed once; `unknown` rows are free. Example: 5,000 unique emails = $5.00.

### Limits

- 10,000 emails per run; DNS answers are cached per domain within a run.
- Disposable and role lists are heuristics: new throwaway domains appear daily, and some companies use role-like addresses for real people.
- Results reflect DNS at run time.

# Actor input Schema

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

1-10,000 email addresses. Duplicates (case-insensitive) are checked once. A leading 'mailto:' is ignored.

## Actor input object example

```json
{
  "emails": [
    "jane.doe@gmail.com",
    "info@example.com"
  ]
}
```

# Actor output Schema

## `results` (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": [
        "jane.doe@gmail.com",
        "info@example.com"
    ]
};

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

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

```

## MCP server setup

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

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/ofLmEnE1nBDMHBdaP/builds/S55JKzbBwIFX1CS61/openapi.json