# Bulk Email Verifier: MX, Disposable, Role, Typo + Score (`exepal/bulk-email-verifier`) Actor

Verify email lists without sending mail: syntax, MX, disposable domains (214k), role accounts, free providers, typo fixes, SPF/DMARC and a 0-100 score. Paste emails or a dataset ID. $1 per 1,000; failed lookups are free.

- **URL**: https://apify.com/exepal/bulk-email-verifier.md
- **Developed by:** [Laxman Kafle](https://apify.com/exepal) (community)
- **Security:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

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

## Bulk Email Verifier: MX, Disposable, Role, Typo + Score

**Paste a list of emails, or point it at any dataset, and get a verdict for each address: likely, risky or undeliverable, with a 0 to 100 score and the reasons. No email is sent. $1 per 1,000 addresses, and lookups that fail are free.**

Use it to clean a lead list before a cold-email campaign, to drop disposable signups, or as the last step after scraping contacts. It pairs with [Website Contact Finder](https://apify.com/exepal/website-contact-finder): paste that run's dataset ID here.

### What it checks

| Check | What it means |
|---|---|
| Syntax | Is it a well-formed address? |
| MX records | Does the domain accept mail at all? Includes null-MX and the A-record fallback |
| Disposable | Is the domain on a list of 214,000 throwaway providers (Mailinator, 10minutemail, ...)? |
| Role account | info@, sales@, support@, noreply@ and similar shared inboxes |
| Free provider | Gmail, Outlook, Yahoo, ... (personal rather than company addresses) |
| Typo | gmial.com, hotmial.com, ... with the likely fix in `suggestion` |
| Domain security | SPF and DMARC on the domain, with an A to F grade |
| Mail provider | Google Workspace, Microsoft 365, Zoho, ... from the MX hosts |

These signals add up to a **score** (0 to 100) and a **deliverable** verdict: `likely` (70 and up), `risky`, or `undeliverable` (no mail server, null MX, reserved domain, bad syntax).

### Output

```json
{
  "email": "someone@gmial.com",
  "deliverable": "undeliverable",
  "score": 0,
  "suggestion": "someone@gmail.com",
  "flags": ["no-mx", "possible-typo"],
  "mx": { "present": false, "nullMx": false, "exchanges": [], "fallbackToA": false },
  "disposable": false,
  "role": false,
  "freeProvider": false,
  "domainSecurity": { "grade": "F", "spf": false, "dmarc": false }
}
```

When the input comes from a dataset, the row's `title`, `name`, `website`, `domain`, `phone` and `company` are carried into the output, so you get one clean lead list.

### Pricing

Pay per event: **$0.001 per unique address verified** ($1 per 1,000). Duplicates are removed before checking. If a DNS lookup fails even after retries, the address comes back as `unknown` with an `error` and you aren't charged.

### What it doesn't do

It does not connect to the mail server to ask whether the mailbox exists (no SMTP probe). That keeps it fast, cheap and safe for your IP reputation, but a `likely` address on a real company domain can still bounce if that one person has left. For most list cleaning, the checks above catch the bulk of the bad addresses: typos, dead domains, disposables and role inboxes.

### Also from Exepal

The same check is available to AI agents per call at `https://api.exepal.com/v1/email` and over MCP at `https://api.exepal.com/mcp`, with 20 free calls a day. See [exepal.com/docs](https://exepal.com/docs).

# Actor input Schema

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

Addresses to verify, one per line (comma or semicolon separated lines work too). Duplicates are removed.

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

Verify the emails in another run's dataset, e.g. Website Contact Finder or any scraper with an `email`, `bestEmail` or `emails` field. Business name, website and phone are carried through.

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

Stop after this many unique addresses.

## `onlyDeliverable` (type: `boolean`):

Keep only addresses with the verdict "likely". Every address checked is still billed.

## Actor input object example

```json
{
  "emails": [
    "contact@laxmankafle.com",
    "someone@gmial.com",
    "test@mailinator.com"
  ],
  "maxEmails": 10000,
  "onlyDeliverable": false
}
```

# Actor output Schema

## `results` (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": [
        "contact@laxmankafle.com",
        "someone@gmial.com",
        "test@mailinator.com"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("exepal/bulk-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": [
        "contact@laxmankafle.com",
        "someone@gmial.com",
        "test@mailinator.com",
    ] }

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

```

## MCP server setup

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