# Email List Validator - MX, Disposable, Typos (`staymeter-labs/email-list-validator`) Actor

Clean and verify an email list in bulk. Syntax check, live MX/DNS lookup, disposable-domain, role-account and free-provider detection, typo suggestions (gmial.com), Gmail normalisation and duplicate removal. No login, no API key, no proxies.

- **URL**: https://apify.com/staymeter-labs/email-list-validator.md
- **Developed by:** [Staymeter Labs](https://apify.com/staymeter-labs) (community)
- **Categories:** Lead generation, Developer tools
- **Features:** Limited permissions
- **Stats:** 3 total users, 2 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

Pay per usage

This Actor is paid per platform usage. The Actor is free to use, and you only pay for the Apify platform usage, which gets cheaper the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-usage

## 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 List Validator — bulk email verifier with MX check, disposable & typo detection

**Clean and verify an email list in bulk**: syntax check, live MX / DNS lookup, disposable-domain detection, role-account (`info@`, `support@`) flags, typo suggestions (`gmial.com` → `gmail.com`) and smart duplicate removal. Remove bounces before you send. No login, no API key, no proxies — results in seconds, export as JSON, CSV or Excel.

### How to use in 3 steps

1. **Paste your emails** — one per line (`Name <a@b.com>` and `mailto:` forms work too) — or give a link to a CSV / text file in *Or load from a file URL* (e.g. a published Google Sheets CSV link); every address found in the file is checked.
2. **Choose options** — keep *Check MX / DNS* on, and pick whether you want all results, only valid ones, or only the problems.
3. **Run and export** — each address gets a `status` (`valid`, `risky`, `invalid`, `unknown`), a 0–100 `score` and a plain-English `reason`.

### What you get

- **Syntax validation** following the real rules (local part, dots, length, IDN domains converted to punycode).
- **Live DNS check** over DNS-over-HTTPS: does the domain exist, does it have mail servers (MX), or at least an A/AAAA record? A "null MX" (domain that explicitly accepts no mail) is detected as invalid.
- **Disposable / temporary domains** from the community-maintained, CC0 [disposable-email-domains](https://github.com/disposable-email-domains/disposable-email-domains) list (~5,000 domains, downloaded fresh on every run), including subdomains.
- **Mail provider detection** — `mailProvider` tells you whether a company domain runs on Google Workspace, Microsoft 365, Zoho, Proofpoint, Mimecast and more (from its MX records).
- **SPF / DMARC check** (optional, `checkEmailAuth`) — `hasSpf` and `dmarcPolicy` (`none` / `quarantine` / `reject`) show whether a company domain actively manages its mail; domains with neither are a weaker B2B lead signal.
- **Role accounts** such as `info@`, `admin@`, `noreply@`.
- **Free-provider flag** (Gmail, Outlook, Yahoo…) — handy for splitting B2B from consumer leads.
- **Typo suggestions** for common providers (`bob@gmial.com` → `bob@gmail.com`, `.con` → `.com`).
- **Smart de-duplication** — case-insensitive, and Gmail dots and `+tags` count as the same mailbox (`Jane.Doe+promo@gmail.com` = `janedoe@gmail.com`).
- **Fast** — DNS answers are cached per domain, so 10,000 addresses on 800 domains need only 800 lookups.

### Output

| Field | Example |
|---|---|
| `email` | `jane.doe@gmail.com` (domain lower-cased, IDN as punycode) |
| `status` | `valid` / `risky` / `invalid` / `unknown` |
| `score` | `100` |
| `reason` | `Syntax and mail server look fine` |
| `isDisposable`, `isRole`, `isFreeProvider` | `false`, `false`, `true` |
| `suggestion` | `bob@gmail.com` or `null` |
| `normalizedEmail` | `janedoe@gmail.com` |
| `mailProvider` | `google`, `microsoft365`, `zoho`… or `null` (unknown, or no MX) |
| `hasSpf`, `dmarcPolicy` | `true`, `reject` — only with *Check SPF / DMARC* on, otherwise `null` |
| `domain`, `mxFound`, `mxHosts` | `gmail.com`, `true`, `["gmail-smtp-in.l.google.com", …]` |

```json
{
  "email": "bob@gmial.com",
  "status": "risky",
  "score": 15,
  "reason": "Disposable email domain; Possible typo, did you mean bob@gmail.com?",
  "isDisposable": true,
  "isRole": false,
  "isFreeProvider": false,
  "suggestion": "bob@gmail.com",
  "normalizedEmail": "bob@gmial.com",
  "domain": "gmial.com",
  "mxFound": true,
  "mailProvider": null,
  "hasSpf": null,
  "dmarcPolicy": null,
  "mxHosts": []
}
```

`status`: **valid** = syntax and DNS fine; **risky** = deliverable domain but disposable, role account or likely typo; **invalid** = bad syntax or the domain cannot receive mail; **unknown** = DNS lookup failed, retry later. `mxHosts` is empty when the domain accepts mail via an A/AAAA record only. `mxFound` is `null` when *Check MX* is off.

### Input examples

Check a pasted list:

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

Only the addresses worth sending to:

```json
{ "emails": ["a@company.com", "b@company.org"], "outputFilter": "valid" }
```

Load a CSV from a link:

```json
{ "emailsUrl": "https://docs.google.com/spreadsheets/d/e/<id>/pub?output=csv" }
```

B2B list with SPF / DMARC signals:

```json
{ "emails": ["ceo@stripe.com", "sales@example.org"], "checkEmailAuth": true }
```

Fast syntax-only pass, keep duplicates:

```json
{ "emails": ["a@b.com", "A@B.com"], "checkMx": false, "removeDuplicates": false }
```

### Use cases

- Clean a purchased or exported list before a cold-email or newsletter campaign.
- Protect sender reputation: drop bounces, disposable sign-ups and typos.
- Score sign-up forms or CRM exports in bulk; schedule via API.
- Find typo fixes (`suggestion`) and recover otherwise-lost leads.

### FAQ

**Does it check that the mailbox exists?** No. It does not open SMTP connections (most providers block or mis-answer those probes, and it risks your IP reputation). `valid` means the syntax is right and the domain can receive mail. Treat it as a strong pre-filter, not a delivery guarantee.

**Is it catch-all aware?** No — that needs SMTP probing.

**How many emails per run?** Up to 100,000.

**Can I upload a CSV?** Put the file somewhere with a public link (Google Sheets *publish to web → CSV*, or an Apify key-value store record URL) and paste the link into *Or load from a file URL*. Addresses are pulled out of any column.

**Is a typo domain flagged even when it does not exist?** Yes — `bob@gmail.con` is `invalid` and the reason says `did you mean bob@gmail.com?`.

**Which DNS is used?** Cloudflare's public DNS-over-HTTPS JSON API, with Google Public DNS as fallback.

**Why is a domain "unknown"?** Both DNS resolvers failed or timed out; run those addresses again.

### Use it from AI agents

Works through the Apify MCP server: *"Validate these 500 leads and give me only the deliverable ones."*

### Limits

No mailbox-level (SMTP) verification, no catch-all detection, no inbox-provider reputation data. Results reflect DNS at run time.

### Pricing

Free to use — you only pay Apify's standard platform usage, which is tiny because this Actor only does small DNS requests (no browser, no proxies).

# Actor input Schema

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

Emails to check. Paste one per line; 'Name <a@b.com>' and 'mailto:' forms are accepted. Up to 100,000 per run.

## `emailsUrl` (type: `string`):

Optional link to a CSV or text file (e.g. a Google Sheets 'publish as CSV' link or an Apify key-value store file). Every email address found in the file is added to the list above.

## `checkMx` (type: `boolean`):

Look up the domain's mail servers (MX, falling back to A). Turn off for a fast syntax-only pass.

## `checkEmailAuth` (type: `boolean`):

Also look up each domain's SPF and DMARC records (adds hasSpf and dmarcPolicy). Domains without them are often unmanaged or low-quality, handy for B2B list scoring. Needs 'Check MX / DNS' on.

## `removeDuplicates` (type: `boolean`):

Skip repeated addresses (case-insensitive; Gmail dots and +tags are treated as the same mailbox).

## `outputFilter` (type: `string`):

Return every address, only the usable ones (valid), or only the ones to clean out (invalid + risky).

## Actor input object example

```json
{
  "emails": [
    "jane.doe@gmail.com",
    "info@example.com",
    "someone@mailinator.com",
    "bob@gmial.com",
    "not-an-email"
  ],
  "checkMx": true,
  "checkEmailAuth": false,
  "removeDuplicates": true,
  "outputFilter": "all"
}
```

# Actor output Schema

## `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@example.com",
        "someone@mailinator.com",
        "bob@gmial.com",
        "not-an-email"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("staymeter-labs/email-list-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@example.com",
        "someone@mailinator.com",
        "bob@gmial.com",
        "not-an-email",
    ] }

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

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,staymeter-labs/email-list-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/VW29Stgn0NbFXaPvI/builds/cVNDkPq9vLe6VPYi5/openapi.json
