# Email Validator: Syntax, MX, Disposable, Typo & Role Checks (`leadgenguy/email-validator`) Actor

Bulk-check email lists without sending anything: syntax, mail server, disposable domains, role addresses, typos, SPF/DMARC and provider. Honest verdicts. $0.30 per 1,000.

- **URL**: https://apify.com/leadgenguy/email-validator.md
- **Developed by:** [Mokssh jaiin](https://apify.com/leadgenguy) (community)
- **Categories:** Lead generation, Automation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

Pay per event

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 Validator: Syntax, MX, Disposable, Typo & Role Checks — $0.30 per 1,000

Clean an email list **without sending a single email**. For every address the Actor checks the syntax, whether the domain can receive mail, whether it is a throwaway provider, a shared role address (`info@`, `sales@`), or a typo of a popular domain (`gmial.com` becomes `gmail.com`), and reports the mail provider and SPF/DMARC setup. Fast, private, and priced at $0.30 per 1,000.

### What it can and cannot tell you

It checks **everything that can be known without contacting the mailbox's server**. It **cannot confirm that a specific mailbox exists**: that needs an SMTP probe, which is unreliable (most big providers hide the answer) and gets IPs blocked, so this Actor does not do it. The best verdict is `looks_valid`, meaning the address is well-formed and its domain accepts email. For campaigns, treat `looks_valid` as "safe to send in small batches" and watch your bounce rate.

| Verdict | Meaning |
|---|---|
| `looks_valid` | Syntax is valid and the domain accepts email |
| `risky` | Role address, probable typo, or a domain with no mail server listed |
| `disposable` | Temporary / throwaway email provider |
| `undeliverable_domain` | The domain has no mail server at all |
| `invalid` | Bad syntax |
| `unknown` | Our DNS lookup failed (try again). **Free**, never charged |

### Pricing

| Event | Price |
|---|---|
| Email checked | $0.30 per 1,000 ($0.0003 each) |
| Actor start | $0.00005 |

Free Apify accounts are limited to **100 emails per run**.

### Input

```json
{ "emails": ["john.smith@stripe.com", "info@apify.com", "someone@gmial.com", "test@mailinator.com"] }
```

### Output

```json
{
  "email": "someone@gmial.com", "domain": "gmial.com", "verdict": "risky", "score": 25,
  "reasons": ["no mail server listed, only a website address", "looks like a typo of gmail.com"],
  "syntaxValid": true, "disposable": false, "roleAccount": false, "freeProvider": false,
  "suggestion": "someone@gmail.com",
  "mail": { "hasMailServer": false, "provider": null, "primaryMx": null, "spf": false, "dmarc": false }
}
```

A summary of verdict counts is saved in the run's key-value store under `SUMMARY`.

### Honest limits

- The disposable list covers hundreds of well-known providers but new ones appear daily.
- `score` is a rule-based indication, not a probability that the mailbox exists.

### Feedback and reviews

Found a bug, or need a check added? Open an issue on this Actor's **Issues** tab and it will be looked at quickly. If this Actor saved you time, a short and honest review helps other people find it. Thank you!

### Legal

The Actor only reads public DNS records. It never contacts the mailboxes you list. Email addresses can be personal data: you are responsible for lawful use (GDPR, CAN-SPAM, CASL and similar).

# Actor input Schema

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

Up to 100,000 per run (free Apify plans: 100 per run). Duplicates are removed.

## Actor input object example

```json
{
  "emails": [
    "jane@company.com"
  ]
}
```

# Actor output Schema

## `jobs` (type: `string`):

All scraped jobs as a 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": [
        "john.smith@stripe.com",
        "info@apify.com",
        "someone@gmial.com",
        "test@mailinator.com"
    ]
};

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

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

```

## MCP server setup

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