# Email Verifier - MX, Disposable & Role Check (`zhucl1006/email-verifier-mx-disposable`) Actor

Bulk email verification: syntax, domain & MX records, disposable/temporary domains, role addresses (info@, sales@), free providers, typo suggestions and a 0-100 score. $2 per 1,000 emails. Works with any list or a dataset from our contact scrapers.

- **URL**: https://apify.com/zhucl1006/email-verifier-mx-disposable.md
- **Developed by:** [leo zhu](https://apify.com/zhucl1006) (community)
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.00 / 1,000 email verifieds

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 Verifier - MX, Disposable & Role Check

Clean an email list before outreach. For every address you get a **status** (`valid` / `acceptable` / `risky` / `invalid` / `unknown`), a **0-100 score** and the reasons:

- **Syntax** check (RFC-style local part and domain, IDN domains).
- **Domain & MX records** - does the domain exist and accept email? (null MX, no mail server, non-existent domain = `invalid`). Shows the mail provider (Google Workspace, Microsoft 365, Zoho...).
- **Disposable / temporary domains** (~10,000 known domains, e.g. mailinator) = `risky`.
- **Role addresses** (info@, sales@, support@...) flagged.
- **Free providers** (gmail, outlook, yahoo...) flagged.
- **Typo suggestions** (`john@gmial.com` -> `john@gmail.com`).

### Important: no SMTP mailbox check on Apify

Checking whether a single mailbox exists (and catch-all detection) needs an outbound connection to port 25. **Port 25 is blocked on the Apify platform**, so this Actor does **not** confirm individual mailboxes there and never claims to. Every result has `smtpAvailable: false` and `smtpResult: "notChecked"`, and a good address gets `acceptable` (syntax + mail server OK), not `valid`. The status `valid` / catch-all detection only appears if you run the Actor locally where port 25 is open (Docker / `apify run`). No email is ever sent.

### Pricing (pay per event)

| Emails verified | Cost |
|---|---|
| 1,000 | $2.00 |
| 10,000 | $20.00 |
| 100,000 | $200.00 |

Plus $0.00005 per run start. Duplicates are verified and charged once. The Free plan's $5 monthly credit covers about 2,400 emails. If **Maximum cost per run** is reached the Actor stops cleanly; unverified addresses are saved to `NOT_PROCESSED_EMAILS` and not charged.

### Use with our contact scrapers

Find emails, then verify them:

1. Run **Website Contact Extractor** (any websites) or **Google Maps Contact Enricher** (Google Maps results).
2. Paste that run's dataset into **Dataset ID** here (field `emails`, or `primaryEmail`).
3. Keep `acceptable`/`valid`, review `risky`, drop `invalid`.

### Output example

```json
{"email": "test@mailinator.com", "status": "risky", "score": 10, "disposable": true, "role": false,
 "mxStatus": "mx", "emailProvider": null, "smtpAvailable": false, "smtpResult": "notChecked",
 "reasons": ["Disposable / temporary email domain"]}
```

### Feedback

Problem with a run? Use **Share run with developer** or open an issue. Useful? Please leave a review.

# Actor input Schema

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

Email addresses, one per line. Duplicates are verified and charged once.

## `datasetId` (type: `string`):

Verify emails from an Apify dataset, e.g. output of Website Contact Extractor or Google Maps Contact Enricher.

## `emailField` (type: `string`):

Field with an email or a list of emails (e.g. "emails" or "primaryEmail").

## `maxEmails` (type: `integer`):

0 = no limit.

## `smtpCheck` (type: `boolean`):

Only works where outbound port 25 is open. On the Apify platform port 25 is normally blocked, so this is skipped automatically and reported in each result (smtpAvailable=false).

## `maxConcurrency` (type: `integer`):

Domains looked up in parallel.

## `heloHost` (type: `string`):

Hostname announced in SMTP checks. Only used when port 25 is reachable.

## Actor input object example

```json
{
  "emails": [
    "info@joesstonecrab.com",
    "test@mailinator.com",
    "john@gmial.com",
    "someone@nonexistent-domain-xyz987.com"
  ],
  "emailField": "emails",
  "maxEmails": 0,
  "smtpCheck": true,
  "maxConcurrency": 20,
  "heloHost": "verify.example.com"
}
```

# Actor output Schema

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

No description

## `runSummary` (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": [
        "info@joesstonecrab.com",
        "test@mailinator.com",
        "john@gmial.com",
        "someone@nonexistent-domain-xyz987.com"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("zhucl1006/email-verifier-mx-disposable").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": [
        "info@joesstonecrab.com",
        "test@mailinator.com",
        "john@gmial.com",
        "someone@nonexistent-domain-xyz987.com",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("zhucl1006/email-verifier-mx-disposable").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": [
    "info@joesstonecrab.com",
    "test@mailinator.com",
    "john@gmial.com",
    "someone@nonexistent-domain-xyz987.com"
  ]
}' |
apify call zhucl1006/email-verifier-mx-disposable --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,zhucl1006/email-verifier-mx-disposable"
        }
    }
}
```

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/ODvmGew1faUgC9fye/builds/cycheDzpGSav30q3x/openapi.json