# Email List Verifier (syntax, MX, disposable, role, typo check) (`larkmoor/email-list-verifier`) Actor

Clean an email list before you send: syntax, domain exists, MX records, mail provider, disposable domains, role addresses, free-mail providers and typo suggestions (gmial.com to gmail.com), with a status (valid, risky, invalid, unknown) and a 0-100 score per address.

- **URL**: https://apify.com/larkmoor/email-list-verifier.md
- **Developed by:** [Larkmoor Data](https://apify.com/larkmoor) (community)
- **Categories:** Marketing, Lead generation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.26 / 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.
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

## Email List Verifier (syntax, MX, disposable, role, typo check)

Clean an email list before you send: syntax check, domain exists, mail servers (MX) present, mail provider (Google Workspace, Microsoft 365...), disposable/temporary domains, role addresses (info@, sales@), free-mail providers and typo suggestions (gmial.com → gmail.com), with a status (valid_syntax_mx / risky / invalid / unknown) and a 0–100 score per address. DNS-based, so it is fast, safe for your sender reputation and works on lists of any size.

### What you can use it for

- Before a campaign: drop invalid and disposable addresses so bounces don't hurt your sender reputation
- Lead lists: flag role addresses (info@, sales@) and free-mail signups, keep the business ones
- Signup forms and CRMs: catch typos (gmial.com) and dead domains at import time
- Data cleaning at scale: 100k addresses in one run

### Why this one

- Checks what can be checked reliably without touching the mailbox: syntax (RFC-style), domain existence, MX mail servers, mail provider, 90+ disposable domains, 60+ free providers, 50+ role names, common typos
- DNS answers are cached per domain, so big lists from the same companies verify in seconds
- Clear status (valid_syntax_mx / risky / invalid / unknown) plus a 0–100 score and a plain-language reason for every address
- Pay only for results: **$0.30 per 1,000 emails**. No subscription.

### Input

- **Emails** (`emails`): One email per line (duplicates are removed).
- **Only return these statuses** (`onlyStatuses`): Empty = return every email with its status.
- **Max emails** (`maxResults`) Default: `100000`.

### Output

One row per email in the dataset (JSON, CSV, Excel, or through the API). Sample:

```json
[
 {
  "email": "hello@apify.com",
  "normalized": "hello@apify.com",
  "valid": true,
  "status": "valid_syntax_mx",
  "reason": "syntax ok, domain has mail servers (role address)",
  "local": "hello",
  "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"
  ],
  "mailProvider": "Google Workspace",
  "isFreeProvider": false,
  "isDisposable": false,
  "isRole": true,
  "suggestion": null,
  "score": 70
 },
 {
  "email": "someone@gmial.com",
  "normalized": "someone@gmial.com",
  "valid": false,
  "status": "invalid",
  "reason": "domain has no mail server (no MX)",
  "local": "someone",
  "domain": "gmial.com",
  "domainExists": true,
  "hasMx": false,
  "mxRecords": null,
  "mailProvider": null,
  "isFreeProvider": false,
  "isDisposable": false,
  "isRole": false,
  "suggestion": "someone@gmail.com",
  "score": 5
 }
]
```

### Tips

- This is a DNS-level verifier: it does not confirm that the specific mailbox exists (mailbox pinging from cloud servers is blocked by Gmail, Microsoft and most providers and gives unreliable answers). `valid_syntax_mx` means the address is well-formed and its domain has mail servers; the mailbox itself is not checked (the `mailboxChecked` column is always false).
- Use onlyStatuses: \["valid_syntax_mx"] to get a pre-cleaned list directly (then run it through your ESP's bounce handling as usual).

### Integrations and API

Run it on a schedule, trigger it from the API or a webhook, and send results to Google Sheets, Zapier, Make, Slack, a database or your own code with the platform's standard integrations.

### Data and fair use

This tool reads only public sources (official APIs, public feeds or pages the publisher makes available to everyone) and respects robots.txt and rate limits. You are responsible for using the data in line with the source's terms and applicable law.

### How much it costs

You pay per result (pay-per-event), nothing per month and nothing when a run returns nothing. The price is **$0.30 per 1,000 emails** on the Free plan, with automatic discounts on paid plans (Bronze −5%, Silver −10%, Gold −15%, Platinum −20%).

Worked examples:

- 100 emails → **$0.03**
- 1,000 emails → **$0.30**
- 10,000 emails → **$3.00**
- Plus $0.001 per run start.

Platform usage (compute, storage) is included in the price: the actor runs at a small memory setting by default, so a typical run of 1,000 emails finishes in well under a minute.

### FAQ

**Does it check whether the mailbox exists?**

No. It checks syntax, that the domain exists, that it has mail servers (MX), disposable/role/free-provider lists and common typos. It never contacts the mailbox, so a `valid_syntax_mx` address can still bounce (catch-all domains, deleted mailboxes). It is a fast, cheap pre-send clean that removes the addresses that are guaranteed to bounce.

**Why not call it 'deliverable'?**

Because without a mailbox-level check nobody can promise deliverability, and we would rather be honest than sell a word.

**Why are some fields empty?**

A field is `null` when the source does not publish it for that row. The output keeps every column so your spreadsheet or integration always sees the same shape.

**Can I run it on a schedule?**

Yes. Use Apify Schedules (daily, hourly, cron) and connect the run to Make, Zapier, n8n, Google Sheets, a webhook or the API. Each run writes a dataset you can download as JSON, CSV or Excel.

**Is there a free trial?**

The Apify Free plan includes $5 of monthly platform credit, enough to try this actor on a few hundred results at no cost. There is no subscription for the actor itself.

**Can an AI agent use this?**

Yes. The actor is available through Apify's MCP server and the API, so LLM agents (Claude, ChatGPT, LangChain, CrewAI) can call it as a tool with the same input.

**What happens if something fails?**

Runs log every skipped item with a reason. If the source is down, the actor stops cleanly and you are only charged for the results it returned.

### Changelog

- **2026-10-18** — Lower price with Bronze/Silver/Gold discounts; smaller default memory (cheaper runs); clean table view of results; FAQ and cost examples; statuses renamed to be honest: `valid_syntax_mx` instead of `valid`; new `mailboxChecked` column (always false, the mailbox is not contacted); default limit 1,000.

### Support

Found a problem or need a field added? Open an issue on the Issues tab; it is read and answered.

# Actor input Schema

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

One email per line (duplicates are removed).

## `onlyStatuses` (type: `array`):

Empty = return every email with its status. valid_syntax_mx = syntax OK and the domain has mail servers (the mailbox itself is not checked); risky = disposable, role, free-mail or likely typo; invalid = bad syntax, no domain or no MX; unknown = DNS lookup failed.

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

Max emails. Default: 100000. (min 1)

## Actor input object example

```json
{
  "emails": [
    "hello@apify.com",
    "someone@gmial.com",
    "test@mailinator.com",
    "nobody@this-domain-does-not-exist-12345.com"
  ],
  "maxResults": 1000
}
```

# Actor output Schema

## `results` (type: `string`):

All results as JSON items in the run's default dataset (also downloadable as CSV/Excel from the dataset).

# 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": [
        "hello@apify.com",
        "someone@gmial.com",
        "test@mailinator.com",
        "nobody@this-domain-does-not-exist-12345.com"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("larkmoor/email-list-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": [
        "hello@apify.com",
        "someone@gmial.com",
        "test@mailinator.com",
        "nobody@this-domain-does-not-exist-12345.com",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("larkmoor/email-list-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": [
    "hello@apify.com",
    "someone@gmial.com",
    "test@mailinator.com",
    "nobody@this-domain-does-not-exist-12345.com"
  ]
}' |
apify call larkmoor/email-list-verifier --silent --output-dataset

```

## MCP server setup

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