# Email Verifier & Validator (`technicaldost/email-verifier`) Actor

Bulk-verify email deliverability: syntax, MX records, disposable/role/free-provider detection, and a 0-100 deliverability score. Clean your lead lists before you send.

- **URL**: https://apify.com/technicaldost/email-verifier.md
- **Developed by:** [Technical Dost Solutions](https://apify.com/technicaldost) (community)
- **Categories:** Lead generation, Automation, MCP servers
- **Features:** Limited permissions
- **Stats:** 5 total users, 0 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $1.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.

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

Bulk-check email lists before your next lead-generation, outreach, or CRM cleanup campaign. The Actor validates address syntax, identifies common free and disposable providers, detects role-based mailboxes, resolves MX records, and assigns an easy-to-filter deliverability score and status.

Run it from n8n, Make, or Zapier, or on an Apify Schedule / API, to verify every new lead list before outreach.

The Actor uses Node.js DNS resolution and a built-in disposable-domain list. It requires no API key, paid data provider, or proxy.

### Input

| Field | Type | Required | Default | Description |
| --- | --- | --- | --- | --- |
| `emails` | array of strings | Yes | Sample list | Email addresses to validate. |
| `checkMx` | boolean | No | `true` | Resolve mail exchange records for syntactically valid domains. |

Example input:

```json
{
  "emails": [
    "jane.doe@gmail.com",
    "ceo@stripe.com",
    "noreply@disposablemail.com",
    "bad@@format"
  ],
  "checkMx": true
}
```

### Output

Each input email produces one dataset row containing:

- The original `email`, lowercase-and-trimmed `normalizedEmail`, `domain`, and `localPart`
- `syntaxValid`, `mxFound`, and the highest-priority `mxHost`
- `isFreeProvider`, `isRoleBased`, and `isDisposable` flags
- An integer `deliverabilityScore` from 0 to 100
- A `status` of `deliverable` (70–100), `risky` (40–69), or `undeliverable` (0–39)

Example output:

```json
{
  "email": "jane.doe@gmail.com",
  "syntaxValid": true,
  "normalizedEmail": "jane.doe@gmail.com",
  "domain": "gmail.com",
  "localPart": "jane.doe",
  "isFreeProvider": true,
  "isRoleBased": false,
  "isDisposable": false,
  "mxFound": true,
  "mxHost": "gmail-smtp-in.l.google.com",
  "deliverabilityScore": 100,
  "status": "deliverable"
}
```

### Scoring

Every address starts at 100 points. Invalid syntax subtracts 100, no MX record subtracts 60, a disposable domain subtracts 50, and a role-based local part subtracts 10. The final score is clamped to 0–100.

MX records confirm that a domain accepts email routing, but they cannot guarantee that a specific mailbox exists. Use the score as a practical screening signal rather than proof of inbox delivery.

### How to use Email Verifier & Validator

1. Open [Email Verifier & Validator](https://apify.com/technicaldost/email-verifier) on Apify Store and click **Try for free**.
2. Fill in the input (the form is prefilled with a working example) and click **Start**.
3. Watch results appear in the **Output** tab, then download them as JSON, CSV, Excel or HTML, or read them through the API.
4. Optional: save the input as a task and add a **schedule** to run it automatically, or connect it to your tools with integrations and webhooks.

### How much does Email Verifier & Validator cost?

This Actor uses **pay-per-event** pricing: you pay only for what it delivers, and platform usage is included.

| Event | Price |
|---|---|
| Result (one dataset item) | $0.001 each ($1.00 per 1,000) |
| Actor start | $5e-05 per run |

Set **Maximum cost per run** in the run options to cap your spend; the Actor stops when the limit is reached. Check the **Pricing** tab for current prices and plan discounts.

### Use Email Verifier & Validator with AI agents (MCP)

Give Claude, ChatGPT, Cursor, VS Code or any MCP client this Actor as a tool through the hosted [Apify MCP server](https://mcp.apify.com). The agent sees the input fields with descriptions and example values, runs the Actor, and reads the results.

**MCP server URL (this Actor only):**

```
https://mcp.apify.com/?tools=technicaldost/email-verifier
```

**Claude Code:**

```bash
claude mcp add --transport http apify "https://mcp.apify.com/?tools=technicaldost/email-verifier" --header "Authorization: Bearer YOUR_APIFY_TOKEN"
```

**Cursor, VS Code, Claude Desktop and other clients** (`mcp.json` or the client's MCP settings):

```json
{
  "mcpServers": {
    "apify": {
      "url": "https://mcp.apify.com/?tools=technicaldost/email-verifier",
      "headers": { "Authorization": "Bearer YOUR_APIFY_TOKEN" }
    }
  }
}
```

Clients that support sign-in (such as Claude.ai connectors) can use the URL without a token and log in to Apify instead. Get your token in [Apify Console → Settings → API & Integrations](https://console.apify.com/settings/integrations), or generate a ready config for your client at [mcp.apify.com](https://mcp.apify.com). In the agent the tool is named `technicaldost--email-verifier`; ask it, for example, to *"run Email Verifier & Validator with {"emails": \["jane.doe@gmail.com", "ceo@stripe.com", "noreply@disposablemail.com", "bad@@format"], "checkMx": true}"*.

AI agents without an Apify account can also run and pay for this Actor per request with [x402 agentic payments](https://docs.apify.com/platform/integrations/x402).

### Run Email Verifier & Validator via API

Run the Actor and get its results in one call (replace `YOUR_APIFY_TOKEN`):

```bash
curl -X POST "https://api.apify.com/v2/acts/technicaldost~email-verifier/run-sync-get-dataset-items?token=YOUR_APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"emails": ["jane.doe@gmail.com", "ceo@stripe.com", "noreply@disposablemail.com", "bad@@format"], "checkMx": true}'
```

**Python** (`pip install apify-client`):

```python
from apify_client import ApifyClient

client = ApifyClient("YOUR_APIFY_TOKEN")
run = client.actor("technicaldost/email-verifier").call(run_input={"emails": ["jane.doe@gmail.com", "ceo@stripe.com", "noreply@disposablemail.com", "bad@@format"], "checkMx": true})
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item)
```

**JavaScript / TypeScript** (`npm install apify-client`):

```js
import { ApifyClient } from 'apify-client';

const client = new ApifyClient({ token: 'YOUR_APIFY_TOKEN' });
const run = await client.actor('technicaldost/email-verifier').call({"emails": ["jane.doe@gmail.com", "ceo@stripe.com", "noreply@disposablemail.com", "bad@@format"], "checkMx": true});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items);
```

Long runs: start them with `POST /v2/acts/technicaldost~email-verifier/runs` and fetch the dataset when the run finishes, or receive a webhook.

### Related Actors

- [Bulk Email Deliverability Auditor - SPF, DKIM, DMARC](https://apify.com/technicaldost/bulk-email-deliverability-auditor) — Audit SPF, DKIM, DMARC and MX for thousands of domains at once. Returns a graded deliverability score, the par
- [IndiaMART Supplier Verifier & Price Intelligence](https://apify.com/technicaldost/indiamart-supplier-verifier-price-intelligence) — Find Indian suppliers, compare MOQ-adjusted prices, and score verification signals

### FAQ

#### Can I use Email Verifier & Validator with AI agents like Claude or ChatGPT?

Yes. Connect the Apify MCP server with `?tools=technicaldost/email-verifier` (see above) and the agent can run the Actor and read its results on its own.

#### Can I call Email Verifier & Validator from my own code?

Yes. Use the REST API, or the official Python and JavaScript clients shown above. Results are available as JSON, CSV, Excel, XML or HTML.

#### How do I run it on a schedule?

Save your input as a task in Apify Console and add a schedule (for example, daily). Use webhooks or integrations to send each run's results onward.

#### Is it legal to use this Actor?

It works with publicly available data. Make sure your use complies with the source website's terms and with data protection laws such as GDPR, especially for personal data.

#### Something doesn't work or I need a feature. What should I do?

Open an issue in the **Issues** tab on this Actor's page with an example input, and we'll look into it.

# Actor input Schema

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

Email addresses to validate. Add one address per line.

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

Resolve each valid domain's mail exchange records.

## Actor input object example

```json
{
  "emails": [
    "jane.doe@gmail.com",
    "ceo@stripe.com",
    "noreply@disposablemail.com",
    "bad@@format"
  ],
  "checkMx": true
}
```

# Actor output Schema

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

Verification results (email, status, deliverabilityScore)

# 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": [
        "jane.doe@gmail.com",
        "ceo@stripe.com",
        "noreply@disposablemail.com",
        "bad@@format"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("technicaldost/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": [
        "jane.doe@gmail.com",
        "ceo@stripe.com",
        "noreply@disposablemail.com",
        "bad@@format",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("technicaldost/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": [
    "jane.doe@gmail.com",
    "ceo@stripe.com",
    "noreply@disposablemail.com",
    "bad@@format"
  ]
}' |
apify call technicaldost/email-verifier --silent --output-dataset

```

## MCP server setup

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