# Email Validator: Syntax, Domain, MX, Disposable & Typo Check (`veedel_digital/email-verifier`) Actor

Validate email lists in bulk: syntax, typos (gmial.com), disposable and role addresses, free providers, domain and MX records, mail provider (Google, Microsoft, IONOS...). Fast pre-filter, no SMTP, pay per email.

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

## Pricing

from $0.30 / 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

### What does Email Validator do?

This Actor **validates email lists in bulk** without sending a single email. For every address you get a **status** (`valid`, `invalid`, `risky`, `unknown`), a **reason**, a **score** from 0 to 100 and the individual checks:

- **Syntax** check close to RFC 5321/5322, including international domains (`müller.de`) and `Name <email>` / `mailto:` input
- **Typo suggestions** for common providers: `gmial.com` → `gmail.com`, `hotmial.de` → `hotmail.de`, `firma.con` → `firma.com`
- **Domain and MX records**: domain exists, has mail servers, or explicitly accepts no mail (null MX)
- **Disposable / temporary email** domains (about 10,000 known services, subdomains included)
- **Role accounts** (`info@`, `sales@`, `kontakt@`, …) and **no-reply** addresses
- **Free providers** (Gmail, Outlook, GMX, WEB.DE, …) to separate business from private addresses
- **Mail provider** detected from the MX records: Google Workspace, Microsoft 365, IONOS, Strato, Hornetsecurity, Proofpoint and more

You get **one row per input row in the original order**, so the result lines up with your spreadsheet. Duplicates are marked and not charged again.

### Why use this email validator?

- **Clean lists before a campaign**: remove addresses whose domain doesn't exist or doesn't accept mail
- **Pre-filter before paid SMTP verification**: drop the obviously bad addresses here for a fraction of the price, then verify only the rest
- **Fix typos in sign-up and CRM data** with the suggested correction
- **Block disposable addresses** in lead lists and trial sign-ups
- **Segment B2B leads** by mail provider: Microsoft 365 vs. Google Workspace vs. local hosters
- **Fast and cheap**: no proxies, no browser, each domain is looked up only once per run

### What it does not do

This Actor does **not** connect to the recipient's mail server (no SMTP "mailbox exists" check), because cloud platforms block outgoing port 25. So it can tell you that `max@company.com` has a valid domain with working mail servers, but not whether the mailbox `max` exists. Use it as the first, cheap stage of list cleaning.

### Status and reasons

| Status    | Reason                   | Meaning                                                                                              | Score |
| --------- | ------------------------ | ---------------------------------------------------------------------------------------------------- | ----- |
| `valid`   | `OK`                     | Valid syntax, domain has mail servers                                                                | 100   |
| `valid`   | `ROLE_ACCOUNT`           | Valid, but a shared role address like `info@`                                                        | 80    |
| `risky`   | `NO_MX_RECORD`           | Domain has no MX record, only an A record. Mail servers may still deliver, but often nobody reads it | 50    |
| `risky`   | `POSSIBLE_TYPO`          | Domain is one keystroke away from a big provider, see `suggestion`                                   | 20    |
| `risky`   | `DISPOSABLE`             | Disposable / temporary email service                                                                 | 10    |
| `risky`   | `NO_REPLY_ADDRESS`       | `noreply@`, `do-not-reply@`, `mailer-daemon@` …                                                      | 10    |
| `invalid` | `INVALID_SYNTAX`         | Not an email address                                                                                 | 0     |
| `invalid` | `DOMAIN_NOT_FOUND`       | The domain does not exist                                                                            | 0     |
| `invalid` | `DOMAIN_ACCEPTS_NO_MAIL` | The domain publishes a null MX record (RFC 7505)                                                     | 0     |
| `invalid` | `NO_MAIL_SERVER`         | The domain has neither MX nor A records                                                              | 0     |
| `unknown` | `DNS_ERROR`              | DNS did not answer (timeout, server failure). Try again later                                        | –     |

### How to validate an email list

1. Click **Try for free**.
2. Paste your addresses into **Email addresses**, one per line (or upload them via the API).
3. Click **Start**.
4. Open the **Overview** table, or download everything as CSV, Excel or JSON. The **Summary** shows counts by status, reason and mail provider.

### How much does it cost?

This Actor uses **pay per event**: a fixed price **per unique validated address**, and **platform usage is included**. The current price is shown in the **Pricing** tab. **Free**: duplicates, rows that are not an email address at all (like a CSV header), and addresses whose domain could not be checked because of a DNS error.

### Input

```json
{
    "emails": ["info@apify.com", "someone@gmial.com", "test@mailinator.com", "not-an-email"]
}
```

### Output

```json
{
    "email": "someone@gmial.com",
    "normalizedEmail": "someone@gmial.com",
    "status": "risky",
    "reason": "POSSIBLE_TYPO",
    "score": 20,
    "suggestion": "someone@gmail.com",
    "domain": "gmial.com",
    "mailProvider": null,
    "mxRecords": [],
    "isValidSyntax": true,
    "isDisposable": true,
    "isRole": false,
    "isFreeProvider": false,
    "hasMx": false,
    "requiresSmtpUtf8": false,
    "isDuplicate": false,
    "error": null
}
```

### Related Actors

- [Domain & Email DNS Checker](https://apify.com/veedel_digital/domain-check): WHOIS/RDAP, MX, SPF, DMARC and DKIM for many domains
- [Website Contact & Imprint Extractor](https://apify.com/veedel_digital/contact-extractor): emails, phone numbers, social profiles and imprint data from websites
- [Website Lead Enricher](https://apify.com/veedel_digital/lead-enricher): company name, contacts, tech stack and DNS data from a list of domains

All Actors by Veedel Digital: [apify.com/veedel_digital](https://apify.com/veedel_digital)

### FAQ

#### Where does the disposable domain list come from?

From the open-source project [disposable-email-domains](https://github.com/disposable-email-domains/disposable-email-domains) (CC0 public domain), bundled with the Actor.

#### Why is info@ "valid" and not "risky"?

In B2B, and especially for small companies, `info@` is often the only published address and it is read. The `isRole` flag and the lower score let you filter role accounts if you don't want them.

#### Something does not work

Please open an issue in the **Issues** tab with an example address and the run ID. You can also start the Actor programmatically from the **API** tab.

# Actor input Schema

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

One address per line. Large lists are fine, each domain is looked up only once. Lines with several addresses separated by comma, semicolon or space are split. "Name <email>" and mailto: links are accepted.

## Actor input object example

```json
{
  "emails": [
    "info@apify.com",
    "someone@gmial.com",
    "test@mailinator.com",
    "hello@example.com",
    "not-an-email"
  ]
}
```

# Actor output Schema

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

Dataset with one row per input address

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

Counts by status, reason and mail provider

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

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

# Run the Actor and wait for it to finish
run = client.actor("veedel_digital/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": [
    "info@apify.com",
    "someone@gmial.com",
    "test@mailinator.com",
    "hello@example.com",
    "not-an-email"
  ]
}' |
apify call veedel_digital/email-verifier --silent --output-dataset

```

## MCP server setup

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