# Email Checker: Syntax, MX, Disposable and Typos (No SMTP) (`opendatadesk/email-checker`) Actor

Check e-mail addresses without probing mailboxes. Validates syntax, looks up MX records, flags disposable domains and role addresses, and suggests typo fixes. Every address is returned.

- **URL**: https://apify.com/opendatadesk/email-checker.md
- **Developed by:** [Open Data Desk](https://apify.com/opendatadesk) (community)
- **Categories:** Lead generation, Automation, Developer tools
- **Features:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$0.50 / 1,000 e-mails

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 Checker: Syntax, MX, Disposable and Typos (No SMTP)

Check a list of e-mail addresses without probing anyone's mailbox. The Actor validates syntax, looks up MX records in DNS, flags disposable domains and role addresses such as info@, and suggests a fix when the domain looks like a typo. Every address is returned, including the ones that fail.

This is cheaper and more honest than a "bounce" checker that pretends to know whether a mailbox exists. We never open an SMTP connection.

### What does the Email Checker do?

Typical uses:

- Clean a list before you import it into a newsletter tool or a CRM.
- Catch typo domains such as `gmial.com` or `gmail.con`.
- Drop or flag disposable inboxes and role addresses.
- Run a bulk check from another Actor's dataset.

### What data do you get?

Each input address becomes one row.

| Field | What it is |
| --- | --- |
| `inputIndex` | Position in your input, starting at 0 |
| `email`, `emailNormalized` | The original address and a lower-case trimmed copy |
| `localPart`, `domain` | The two sides of the `@` |
| `syntaxOk` | Whether the address looks well formed |
| `hasMx`, `mxHosts` | Whether the domain has MX records, and the hosts |
| `isDisposable` | Whether the domain is a known disposable inbox |
| `isRoleAddress` | Whether the local part is a role such as info, sales or admin |
| `typoSuggestion` | A likely domain if a typo is suspected, otherwise `null` |
| `issues` | A list of problems |
| `status` | `ok`, `invalid_syntax`, `disposable`, `typo_suspected`, `no_mx`, `mx_lookup_failed`, or `skipped_limit` |

The original address is never rewritten. A typo suggestion is only a hint.

#### Example output

One address from a test run. The Actor also flags invalid syntax, disposable domains and likely typos.

```json
{
    "inputIndex": 0,
    "email": "alex@example.com",
    "emailNormalized": "alex@example.com",
    "localPart": "alex",
    "domain": "example.com",
    "syntaxOk": true,
    "isRoleAddress": false,
    "isDisposable": false,
    "typoSuggestion": null,
    "issues": [],
    "status": "ok",
    "hasMx": true,
    "mxHosts": [
        ""
    ],
    "mxError": null
}
```

### Nothing is silently dropped

Invalid, disposable and typo-suspect addresses stay in the results with a status. If you set `Max addresses to check` lower than the size of your list, the remaining addresses are still written with status `skipped_limit`.

### How to use it

1. Paste addresses in `E-mail addresses`, or give records / a dataset ID.
2. Leave `Look up MX records` on unless you only want syntax and disposable checks.
3. Set `Max addresses to check` and click Start.
4. Download the result as JSON, CSV or Excel, or read it with the API.

### What we do not do

- We do not connect to a mail server, send a probe, or try to find out whether a mailbox exists.
- We do not guarantee that an address with MX records can receive mail, or that a `no_mx` domain never can (some domains receive mail on an A record).
- Catch-all domains can look fine and still bounce later.

### Limits

- Disposable-domain detection uses a bundled public list (MIT licence, see `src/disposable-domains.LICENSE`). The list is a snapshot, not a live feed.
- Typo suggestions cover well-known providers. An unusual private domain will not get a suggestion.

### How much does it cost?

You pay for each address that is written, including invalid and skipped ones. The price per 1,000 addresses is shown at the top of this page, and you can set a maximum cost per run.

### Data and privacy

E-mail addresses are personal data. The Actor does not keep a copy after the run ends, beyond what Apify stores for your run in the usual way, and it does not log the addresses themselves. You are responsible for how you use the list.

### Issues and requests

If a domain is wrongly flagged, or a typo is missed, please open an issue on the Issues tab. You can send the domain only, without the person's name.

# Actor input Schema

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

One address per line. Every address is written back, including invalid, disposable and typo-suspect ones. Mailboxes are never probed over SMTP.

## `records` (type: `array`):

Optional JSON objects. The e-mail is taken from a column named email, or from the column you set below.

## `datasetId` (type: `string`):

Optional. Read e-mail addresses from an existing Apify dataset.

## `emailField` (type: `string`):

Column to use when reading records or a dataset. Leave empty to auto-detect.

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

Checks DNS for a mail server. This does not open an SMTP connection or test whether the mailbox exists.

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

Checks stop after this many addresses. Any remaining addresses are still written, with status skipped_limit.

## Actor input object example

```json
{
  "emails": [
    "alex@example.com",
    "not-an-email",
    "hello@mailinator.com",
    "jane@gmial.com"
  ],
  "checkMx": true,
  "maxItems": 100
}
```

# Actor output Schema

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

Dataset of checked addresses. Each input address is written back, including invalid and disposable ones.

## `summary` (type: `string`):

A short JSON summary of the run, including counts.

# 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": [
        "alex@example.com",
        "not-an-email",
        "hello@mailinator.com",
        "jane@gmial.com"
    ],
    "maxItems": 100
};

// Run the Actor and wait for it to finish
const run = await client.actor("opendatadesk/email-checker").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": [
        "alex@example.com",
        "not-an-email",
        "hello@mailinator.com",
        "jane@gmial.com",
    ],
    "maxItems": 100,
}

# Run the Actor and wait for it to finish
run = client.actor("opendatadesk/email-checker").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": [
    "alex@example.com",
    "not-an-email",
    "hello@mailinator.com",
    "jane@gmial.com"
  ],
  "maxItems": 100
}' |
apify call opendatadesk/email-checker --silent --output-dataset

```

## MCP server setup

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

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/Q1zJQAOUG4vhvkM6a/builds/pf3DvELrUZofG8qlq/openapi.json
