# Email Validator API - Verify, Disposable Check, MX (`george.the.developer/email-validator-api`) Actor

Validate email addresses and check if an email is valid and deliverable: MX record verification, SMTP checks, disposable email detection, free-provider and role-based flags. Clean email lists before outreach. 400+ disposable domains covered.

- **URL**: https://apify.com/george.the.developer/email-validator-api.md
- **Developed by:** [George Kioko](https://apify.com/george.the.developer) (community)
- **Categories:** Marketing, Lead generation
- **Features:** Limited permissions, Single-tenant, Server interface
- **Stats:** 22 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $16.00 / 1,000 email validateds

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.
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 Validator API is an Apify Actor that checks whether an email address is valid. It runs a format test, a disposable domain lookup against 400+ throwaway domains, a role-based prefix check, an MX record lookup and an SMTP mailbox probe, then returns a 0 to 100 confidence score and flags free providers. Validate one address or up to 50 per request with no API key, or call it as a real time HTTP API in Standby mode.

Validate any email address in real-time: format check, MX record verification, SMTP mailbox probe, disposable/temporary email detection (400+ domains), free provider identification, and role-based address flagging. No API key required.

[![Email Validator on Apify](https://img.shields.io/badge/Apify-Email%20Validator%20API-blue)](https://apify.com/george.the.developer/email-validator-api)
[![GitHub](https://img.shields.io/github/stars/the-ai-entrepreneur-ai-hub/email-validator-apify?style=social)](https://github.com/the-ai-entrepreneur-ai-hub/email-validator-apify)

### How It Works

```
                    ┌─────────────────────────────────────────────┐
                    │            Email Validator API               │
                    └──────────────────┬──────────────────────────┘
                                       │
                    ┌──────────────────▼──────────────────────────┐
                    │  Step 1: FORMAT CHECK (+20 pts)              │
                    │  RFC 5321 regex validation                   │
                    │  ✗ Invalid → stop, return error              │
                    └──────────────────┬──────────────────────────┘
                                       │ ✓ Valid
                    ┌──────────────────▼──────────────────────────┐
                    │  Step 2: DISPOSABLE CHECK (-50 pts)          │
                    │  400+ temp/throwaway domains                 │
                    │  mailinator, guerrillamail, tempmail...      │
                    └──────────────────┬──────────────────────────┘
                                       │
                    ┌──────────────────▼──────────────────────────┐
                    │  Step 3: ROLE-BASED CHECK (-10 pts)          │
                    │  32 common role prefixes                     │
                    │  admin@, support@, noreply@, info@...        │
                    └──────────────────┬──────────────────────────┘
                                       │
                    ┌──────────────────▼──────────────────────────┐
                    │  Step 4: MX RECORD LOOKUP (+40 pts)          │
                    │  DNS query for mail exchange servers          │
                    │  Returns up to 5 MX records sorted by        │
                    │  priority                                    │
                    └──────────────────┬──────────────────────────┘
                                       │ MX found
                    ┌──────────────────▼──────────────────────────┐
                    │  Step 5: SMTP VERIFICATION (+40 pts)         │
                    │  Direct TCP connection to mail server         │
                    │  EHLO → MAIL FROM → RCPT TO                  │
                    │  250=valid, 550=invalid, 252=catch-all        │
                    └──────────────────┬──────────────────────────┘
                                       │
                    ┌──────────────────▼──────────────────────────┐
                    │  FINAL SCORE (0-100)                         │
                    │  valid = score ≥ 60 AND format ✓             │
                    │         AND MX found AND not disposable      │
                    └─────────────────────────────────────────────┘
```

### Features

- **5-layer validation pipeline** — Format → Disposable → Role → MX → SMTP
- **SMTP mailbox probe** — asks the mail server on port 25. Many providers refuse that from cloud servers, and then `valid` is `null` (unknown) and the email is not charged
- **400+ disposable domains** — Detects temp/throwaway emails (mailinator, guerrillamail, tempmail, etc.)
- **30+ free providers** — Flags Gmail, Yahoo, Outlook, ProtonMail, etc.
- **32 role-based prefixes** — Detects admin@, support@, noreply@, info@, etc.
- **MX record lookup** — Returns actual mail exchange servers with priority
- **Confidence score** — 0-100 point system with clear pass/fail threshold
- **Bulk validation** — Up to 50 emails per request
- **Instant API** — Real-time HTTP endpoint via Standby mode (<2s response)
- **Zero dependencies** — Uses only Node.js built-in modules (dns, net, http)

### Use Cases

- **Email list cleaning** — Remove invalid/disposable addresses before sending campaigns
- **Lead validation** — Verify prospect emails before adding to CRM
- **Signup fraud prevention** — Block disposable emails at registration
- **Deliverability optimization** — Improve sender reputation by removing bad addresses
- **B2B lead scoring** — Flag free providers vs business domains
- **Compliance** — Ensure email collection meets data quality standards

### Input

| Field | Type | Description |
|-------|------|-------------|
| `email` | String | Single email to validate (e.g., `user@gmail.com`) |
| `emails` | Array | Multiple emails to validate (max 50) |
| `mode` | String | `validate` (default), `disposable` (domain only check), `bulk` |

#### Example Input

```json
{
  "email": "hello@stripe.com"
}
```

### Output

#### Full Validation Response

```json
{
  "email": "hello@stripe.com",
  "valid": true,
  "status": "valid",
  "format_valid": true,
  "mx_found": true,
  "smtp_check": "valid",
  "is_disposable": false,
  "is_free": false,
  "is_role_based": true,
  "domain": "stripe.com",
  "mx_records": [
    { "priority": 1, "exchange": "aspmx.l.google.com" },
    { "priority": 5, "exchange": "alt1.aspmx.l.google.com" }
  ],
  "score": 90,
  "reason": "Valid email address"
}
```

`status` is `valid`, `invalid`, `unknown` or `skipped`. Unknown means no check could decide, for example when the mail server does not answer the mailbox probe, and then `valid` is `null` and the email is not charged. Skipped means a test address such as test@gmail.com, which is never checked or charged.

#### Disposable Email Response

```json
{
  "domain": "mailinator.com",
  "is_disposable": true,
  "is_free": false
}
```

#### Score Breakdown

```
 Score Component          │ Points │ Condition
──────────────────────────┼────────┼──────────────────────────
 Format valid             │   +20  │ Passes RFC 5321 regex
 MX records found         │   +40  │ DNS resolves mail servers
 SMTP: mailbox exists     │   +40  │ RCPT TO returns 250
 SMTP: catch-all server   │   +20  │ RCPT TO returns 252
 SMTP: no answer          │    0   │ valid null (unknown)
 SMTP: invalid mailbox    │   -20  │ RCPT TO returns 550/553
 Disposable domain        │   -50  │ Matched 400+ temp domains
 Role-based address       │   -10  │ admin@, support@, etc.
──────────────────────────┼────────┼──────────────────────────
 VALID threshold          │   ≥60  │ AND format ✓ AND MX ✓
                          │        │ AND not disposable
```

### API Endpoints (Standby Mode)

#### GET /validate — Single Email

```bash
curl "https://YOUR-STANDBY-URL/validate?email=user@gmail.com"
```

#### GET /disposable — Disposable Domain Check

```bash
curl "https://YOUR-STANDBY-URL/disposable?email=test@mailinator.com"
## or by domain
curl "https://YOUR-STANDBY-URL/disposable?domain=guerrillamail.com"
```

#### POST /validate/bulk — Batch Validation

```bash
curl -X POST "https://YOUR-STANDBY-URL/validate/bulk" \
  -H "Content-Type: application/json" \
  -d '{"emails":["user@gmail.com","fake@mailinator.com","ceo@stripe.com"]}'
```

**Response:**

```json
{
  "count": 3,
  "results": [
    { "email": "user@gmail.com", "valid": true, "score": 80, "is_free": true, "is_disposable": false },
    { "email": "fake@mailinator.com", "valid": false, "score": 0, "is_disposable": true },
    { "email": "ceo@stripe.com", "valid": true, "score": 90, "is_free": false, "is_role_based": false }
  ]
}
```

### Pricing

- **$0.02 per email with a definite answer** (valid true or false)
- Unknown answers (`valid` null) and test addresses are free, in single and bulk requests

### Integration Examples

#### Python

```python
import requests

## Single validation
response = requests.get(
    "https://YOUR-STANDBY-URL/validate",
    params={"email": "user@company.com"}
)
result = response.json()
print(f"Valid: {result['valid']}, Score: {result['score']}")
```

#### JavaScript

```javascript
// Bulk validation
const response = await fetch("https://YOUR-STANDBY-URL/validate/bulk", {
  method: "POST",
  headers: { "Content-Type": "application/json" },
  body: JSON.stringify({
    emails: ["user@gmail.com", "fake@tempmail.com", "ceo@stripe.com"]
  })
});
const { results } = await response.json();
const valid = results.filter(r => r.valid);
console.log(`${valid.length}/${results.length} emails are valid`);
```

#### CRM / Spreadsheet Workflow

```
1. Export lead list from CRM (CSV with email column)
2. POST emails to /validate/bulk (50 at a time)
3. Filter results: keep only valid=true AND score >= 60
4. Re-import cleaned list to CRM
5. Result: higher deliverability, lower bounce rate
```

### Disposable Email Domains (Partial List)

The API detects 400+ disposable/temporary email providers including:

`mailinator.com`, `guerrillamail.com`, `tempmail.com`, `yopmail.com`, `10minutemail.com`, `throwaway.email`, `sharklasers.com`, `dispostable.com`, `maildrop.cc`, `fakeinbox.com`, `emailondeck.com`, `getnada.com`, `mohmal.com`, `bugmenot.com`, `trashmail.com`, `spamgourmet.com`, `dropmail.me`, and 380+ more.

### Technical Architecture

```
 Client Request
       │
       ▼
 ┌─────────────────────────────────────────┐
 │  Apify Standby Container (Node.js 22)   │
 │                                          │
 │  ┌────────────────────────────────────┐  │
 │  │  HTTP Server (port from env)       │  │
 │  │  /validate    → single check       │  │
 │  │  /disposable  → domain check       │  │
 │  │  /validate/bulk → batch (≤50)      │  │
 │  └──────────┬─────────────────────────┘  │
 │             │                             │
 │  ┌──────────▼─────────────────────────┐  │
 │  │  Validation Pipeline               │  │
 │  │  1. Regex format check             │  │
 │  │  2. Disposable Set lookup (O(1))   │  │
 │  │  3. Role-based Set lookup (O(1))   │  │
 │  │  4. DNS MX query (async)           │  │
 │  │  5. SMTP TCP probe (port 25)       │  │
 │  └────────────────────────────────────┘  │
 │                                          │
 │  Zero external API calls                 │
 │  Zero npm dependencies (beyond Apify)    │
 └─────────────────────────────────────────┘
```

### Related Tools

- **[Company Enrichment API](https://apify.com/george.the.developer/company-enrichment-api)** — Turn any domain into company data
- **[Website Contact Scraper](https://apify.com/george.the.developer/website-contact-scraper)** — Extract all contact info from websites
- **[Website Intelligence API](https://apify.com/george.the.developer/website-intelligence-api)** — Deep tech detection and SEO analysis

Browse all tools by [george.the.developer on Apify](https://apify.com/george.the.developer).

***

### More lead-gen tools by this developer

- **[LinkedIn Company Employees Scraper](https://apify.com/george.the.developer/linkedin-company-employees-scraper)**, current employees of any LinkedIn company with decision maker flags, no login
- **[Shopify DTC Brand Discovery](https://apify.com/george.the.developer/shopify-dtc-brand-discovery)** — find Shopify stores by niche with tech stack, contacts, and pitch angles
- **[Company Enrichment API](https://apify.com/george.the.developer/company-enrichment-api)** — turn any domain into a company profile: tech stack, socials, emails, DNS
- **[Restaurant Lead Finder](https://apify.com/george.the.developer/restaurant-lead-finder)** — restaurant leads with contacts for POS, delivery, and marketing sellers

# Actor input Schema

## `email` (type: `string`):

Email address to validate

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

Array of email addresses for bulk validation (max 50)

## `mode` (type: `string`):

Validation mode: 'validate' for full check, 'disposable' for disposable-only check

## Actor input object example

```json
{
  "email": "test@gmail.com",
  "mode": "validate"
}
```

# Actor output Schema

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

Rows of this run's dataset in the Overview table view, with email, valid, format valid, mx found, disposable, free provider, role-based and domain.

# 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 = {};

// Run the Actor and wait for it to finish
const run = await client.actor("george.the.developer/email-validator-api").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 = {}

# Run the Actor and wait for it to finish
run = client.actor("george.the.developer/email-validator-api").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 '{}' |
apify call george.the.developer/email-validator-api --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,george.the.developer/email-validator-api"
        }
    }
}
```

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/EGYg3rCFcirARfKXs/builds/DtpkGDrT0XpCBiVS0/openapi.json