# Bulk Email Validator — MX, Format & Disposable Check (`maged120/email-validator`) Actor

Validate email addresses in bulk. Checks format validity, domain existence, MX record resolution, and disposable email domain detection — clean your mailing list before sending.

- **URL**: https://apify.com/maged120/email-validator.md
- **Developed by:** [Maged](https://apify.com/maged120) (community)
- **Categories:** Automation, Developer tools
- **Stats:** 20 total users, 0 monthly users, 100.0% runs succeeded, 1 bookmarks
- **User rating**: No ratings yet

## Pricing

from $12.00 / 1,000 results

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?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Email Verifier & Validator

**Bulk email verification** that goes past a format check: it confirms the domain can receive mail and, wherever possible, whether the **individual mailbox actually exists** — returning a clear **deliverable / risky / undeliverable** verdict and a confidence score for every address.

### What does Email Verifier do?

Paste a list of email addresses and get back, for each one: whether the syntax is valid, whether the domain has mail servers, whether it is a **disposable** or **role-based** address, who runs the mailbox, a **"did you mean"** typo correction, and — the hard part — whether the specific mailbox is real. It runs entirely on the Apify platform, so you get API access, scheduling, integrations, and dataset exports (JSON, CSV, Excel, HTML) out of the box.

Unlike a plain regex checker, this Actor verifies the two largest consumer providers — **Gmail** and **Outlook / Hotmail / Live** — directly at the source, which is exactly where ordinary SMTP verification fails.

### Why use it?

- **Clean your lists before you send.** Remove invalid and dead addresses to protect your sender reputation and lower bounce rates.
- **Stop fake sign-ups.** Catch disposable and mistyped addresses at the point of entry.
- **Better lead data.** Flag role-based inboxes (`info@`, `sales@`) and catch-all domains so your sales team focuses on real people.
- **Fix typos automatically.** `gmial.com` → `gmail.com` suggestions recover addresses you would otherwise lose.

### How to use it

1. Open the **Input** tab.
2. Paste your email addresses into **Emails to Verify** (one per line).
3. Leave **Verify Mailbox Exists** on for the deepest check, or turn it off for a faster syntax + domain pass.
4. Click **Start**. Results stream into the **Output** tab as each address is checked.

### Input

| Field | Type | Description |
|---|---|---|
| `emails` | array | The addresses to verify (up to 10,000 per run). |
| `verifyMailbox` | boolean | Confirm each mailbox exists, not just the domain. Default `true`. |
| `proxyConfiguration` | object | Optional. Off by default; enable to distribute large runs. |

```json
{
    "emails": ["someone@gmail.com", "info@apify.com", "typo@gmial.com"],
    "verifyMailbox": true
}
```

### Output

One row per address. You can download the dataset in JSON, CSV, Excel, or HTML.

```json
{
    "email": "someone@gmail.com",
    "normalizedEmail": "someone@gmail.com",
    "status": "deliverable",
    "subStatus": "mailbox_exists",
    "score": 95,
    "isValidSyntax": true,
    "domain": "gmail.com",
    "hasMxRecord": true,
    "mxRecord": "gmail-smtp-in.l.google.com",
    "mxProvider": "Google Workspace",
    "isDisposable": false,
    "isRoleBased": false,
    "isFreeProvider": true,
    "isCatchAll": false,
    "mailboxExists": true,
    "verifyMethod": "gmail",
    "didYouMean": null,
    "checkedAt": "2026-08-22T00:00:00+00:00"
}
```

#### Fields

| Field | Description |
|---|---|
| `status` | `deliverable`, `risky`, `undeliverable`, or `unknown`. |
| `subStatus` | Reason code, e.g. `mailbox_exists`, `mailbox_not_found`, `catch_all`, `disposable`, `no_mx_record`, `invalid_syntax`. |
| `score` | Confidence 0–100. |
| `mailboxExists` | `true` / `false` / `null` when it can't be determined. |
| `isDisposable` | Temporary / throwaway domain. |
| `isRoleBased` | Shared inbox such as `info@` or `support@`. |
| `isFreeProvider` | Free consumer provider (Gmail, Outlook, Yahoo…). |
| `isCatchAll` | Domain accepts mail for any address (mailbox can't be confirmed). |
| `mxProvider` | Who runs the mail server (Google Workspace, Microsoft 365, …). |
| `didYouMean` | Suggested domain correction for likely typos. |

#### Understanding the verdict

- **deliverable** — the address is valid and the mailbox exists.
- **risky** — reachable but uncertain: catch-all domain or disposable provider. Send with caution.
- **undeliverable** — invalid syntax, no mail server, or the mailbox does not exist.
- **unknown** — the mailbox could not be confirmed (e.g. a provider that hides mailbox existence). Everything else about the address still checks out.

### How much does it cost?

Verification is fast and lightweight — most runs cost a fraction of a cent per address in platform compute. Turning **Verify Mailbox Exists** off makes runs cheaper and faster when you only need syntax and domain validation.

### Tips

- For the cleanest lists, keep mailbox verification on and drop everything marked `undeliverable`; review `risky` addresses separately.
- Schedule a run to re-verify your list periodically — mailboxes go dead over time.
- Use the API to verify addresses on sign-up in real time.

### FAQ & support

- **Is this legal?** The Actor only checks whether an address can receive mail; it never sends email or stores your list. Use it on data you are permitted to process.
- **Why is a Gmail address `unknown` sometimes?** Providers occasionally rate-limit checks; re-running usually resolves it.
- **Found a problem or need a custom field?** Open the **Issues** tab.

# Actor input Schema

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

The email addresses you want to verify. One result is returned per address, with a deliverability verdict and full breakdown.

## `verifyMailbox` (type: `boolean`):

Confirm whether each individual mailbox actually exists, not just the domain. Turn off for a faster, lighter check (syntax + domain + disposable/role only).

## `proxyConfiguration` (type: `object`):

Optional. Not required for normal use — enable only if you verify very large lists and want to distribute requests.

## Actor input object example

```json
{
  "emails": [
    "someone@gmail.com",
    "info@apify.com",
    "nope@thisdomaindoesnotexist1234.com"
  ],
  "verifyMailbox": true,
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}
```

# Actor output Schema

## `dataset` (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": [
        "someone@gmail.com",
        "info@apify.com",
        "nope@thisdomaindoesnotexist1234.com"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("maged120/email-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": [
        "someone@gmail.com",
        "info@apify.com",
        "nope@thisdomaindoesnotexist1234.com",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("maged120/email-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": [
    "someone@gmail.com",
    "info@apify.com",
    "nope@thisdomaindoesnotexist1234.com"
  ]
}' |
apify call maged120/email-validator --silent --output-dataset

```

## MCP server setup

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