# Bulk Email Verifier (`igeniaiservices/email-verifier`) Actor

Verify email lists in bulk — syntax, MX records, disposable & role detection, free-provider tagging, typo suggestions, and a 0–100 deliverability score. No external API, so it's fast and never breaks.

- **URL**: https://apify.com/igeniaiservices/email-verifier.md
- **Developed by:** [iGeni AI](https://apify.com/igeniaiservices) (community)
- **Categories:** Developer tools, Automation, E-commerce
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.50 / 1,000 emails

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.

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

## Bulk Email Verifier

Clean your email lists **fast and reliably** — no external API, no anti-bot walls, no per-check third-party fees. Paste up to 100,000 addresses and get back a clear verdict for each: **deliverable**, **risky**, or **undeliverable**, with a 0–100 score and the reasons.

### What it checks

| Check | What it catches |
|---|---|
| **Syntax** | Malformed addresses (RFC-style validation) |
| **MX records** | Domains that can't receive mail at all (dead / parked domains) |
| **Disposable** | Temp-mail providers (mailinator, guerrillamail, 10minutemail, …) |
| **Role accounts** | `info@`, `sales@`, `support@`, `noreply@` — deliverable but not a person |
| **Free providers** | gmail / outlook / yahoo / icloud … (tagged, not penalised) |
| **Typos** | `gmial.com` → suggests `gmail.com` (with a "did you mean") |
| **Suspicious locals** | Random-hash tracking addresses |

### Why this one

Most Trustpilot-of-email-verifier actors are thin wrappers over a paid API — you pay them, they pay someone else, and if that API hiccups your run fails. This actor does the checking **itself**: pure DNS + logic, so it's **fast, transparent, and it doesn't break** when a third party does. Every verdict comes with the exact reason, so you can trust it.

### Input

```json
{
    "emails": ["john.doe@gmail.com", "info@apify.com", "test@mailinator.com", "user@gmial.com"],
    "checkMx": true,
    "concurrency": 20
}
```

- `emails` — the list to verify (max 100,000)
- `checkMx` — look up MX records (on by default; turn off for a faster syntax-only pass)
- `concurrency` — addresses verified in parallel (default 20)

### Output (one record per email)

```json
{
    "email": "info@apify.com",
    "status": "risky",
    "score": 85,
    "domain": "apify.com",
    "syntaxValid": true,
    "mxFound": true,
    "isDisposable": false,
    "isRole": true,
    "isFreeProvider": false,
    "didYouMean": null,
    "reason": "role_account"
}
```

**Status meaning:**

- **deliverable** — valid syntax, domain accepts mail, no red flags
- **risky** — deliverable but flagged (role account, disposable, likely typo, placeholder)
- **undeliverable** — bad syntax or the domain has no mail servers
- **unknown** — MX check was skipped (`checkMx: false`)

### Use cases

- Clean a list before a campaign to protect your sender reputation and cut bounces
- De-dupe and tag leads (person vs. role, free vs. business)
- Validate signups in bulk

### Notes

This actor verifies **syntax, domain, and reputation** — the reliable layer of email validation. It does **not** open an SMTP connection to each mailbox (that's routinely blocked by mail servers and unreliable due to catch-all configs), so a `deliverable` result means "valid and the domain accepts mail," not a guaranteed inbox. That's the honest, dependable signal — and it's what actually protects your bounce rate.

# Actor input Schema

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

Email addresses to verify (up to 100,000 per run).

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

Look up each domain's MX records to confirm it can receive mail. Turn off for a faster syntax-only pass.

## `mxTimeoutMs` (type: `integer`):

Per-domain DNS timeout. On timeout the domain fails open (treated as deliverable).

## `concurrency` (type: `integer`):

How many addresses to verify in parallel.

## Actor input object example

```json
{
  "emails": [
    "john.doe@gmail.com",
    "info@apify.com",
    "test@mailinator.com",
    "user@gmial.com"
  ],
  "checkMx": true,
  "mxTimeoutMs": 5000,
  "concurrency": 20
}
```

# Actor output Schema

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

One record per email with status, score and flags.

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

Counts by status.

# 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.doe@gmail.com",
        "info@apify.com",
        "test@mailinator.com",
        "user@gmial.com"
    ]
};

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

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

```

## MCP server setup

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