# Bulk Email Verifier — DNS MX & Disposable Check (MCP) (`apexsignal/bulk-email-mx-verifier`) Actor

High-speed bulk B2B email verification: RFC syntax check, live DNS MX record resolution, email provider classification (Google Workspace, Microsoft 365), disposable domain blocker, and role-account detection. Standby MCP ready.

- **URL**: https://apify.com/apexsignal/bulk-email-mx-verifier.md
- **Developed by:** [Burapa Jaiwat](https://apify.com/apexsignal) (community)
- **Categories:** Lead generation, Business, AI
- **Security:** Limited permissions
- **Stats:** 1 total users, 0 monthly users, 0.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.42 / 1,000 verified email records

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

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, DNS MX & Disposable Validator ($0.60/1k | MCP Ready)

High-throughput, deterministic B2B email verification and list hygiene engineered for **Outbound Sales, RevOps, Marketing Operations, and AI Agents (`/mcp`)**.

Verify thousands of email addresses at **$0.60 per 1,000 emails** with **In-Flight Domain MX Deduplication** — checking 5,000 emails across 200 corporate domains performs only 200 DNS queries, eliminating DNS rate limits and slashing verification latency.

***

### Use Cases

- **Pre-Campaign Bounce Prevention:** Strip out invalid syntax, dead domains (`UNDELIVERABLE_NO_MX`), and disposable burner addresses (`UNDELIVERABLE_DISPOSABLE`) before importing leads into Instantly, Smartlead, HubSpot, or Lemlist.
- **B2B vs Free Webmail Filtering:** Separate high-value corporate addresses (`DELIVERABLE_MX_VALID`) from free consumer webmail (`gmail.com`, `yahoo.com`, `outlook.com`) and generic role inboxes (`support@`, `info@`, `sales@`, `admin@`).
- **Mail Server Routing:** Group leads by underlying mail gateway (`Google Workspace`, `Microsoft 365`, `Proofpoint Enterprise`, `Mimecast`, `Zoho Mail`, `Proton Mail`) to optimize sender warm-up and deliverability.
- **Real-Time AI Agent Guardrail (`/mcp`):** Let AI SDR agents verify prospect email addresses in `< 100ms` via Apify Standby MCP before sending automated outreach.

***

### Input Parameters

| Field | Type | Required | Default | Description |
|---|---|---|---|---|
| `emails` | `string[]` | Yes | `["support@apify.com", "info@stripe.com", "test@mailinator.com"]` | List of email addresses to verify. Automatically trims whitespace, lowercases, and deduplicates entries before billing. |
| `maxItems` | `integer` | No | `50` | Maximum number of unique email addresses to verify (`1` to `50,000`). |

#### Example Input

```json
{
  "emails": [
    "jane.doe@apify.com",
    "support@apify.com",
    "burner@mailinator.com"
  ],
  "maxItems": 50
}
```

***

### Output Fields

| Field | Type | Description |
|---|---|---|
| `email` | `string` | Normalized lowercase email address. |
| `domain` | `string` | Extracted domain portion of the email address. |
| `deliverabilityStatus` | `string` | One of: `DELIVERABLE_MX_VALID`, `RISKY_ROLE_OR_FREE`, `UNDELIVERABLE_DISPOSABLE`, `UNDELIVERABLE_NO_MX`, `UNDELIVERABLE_SYNTAX`. |
| `qualityScore` | `integer` | Composite deliverability quality score (`0` to `100`). Corporate MX-valid personal emails score `95`. |
| `syntaxValid` | `boolean` | Whether the address passes strict RFC 5322 local-part and domain syntax rules. |
| `hasMxRecords` | `boolean` | Whether the domain has active DNS `MX` mail exchangers. |
| `mxProvider` | `string` | Identified email provider (`Google Workspace`, `Microsoft 365`, etc.). |
| `mxRecords` | `string[]` | Top priority DNS `MX` hostnames returned for the domain. |
| `isDisposable` | `boolean` | `true` if the domain belongs to a known temporary/burner email provider. |
| `isRoleAccount` | `boolean` | `true` if the local part is a shared role inbox (`support`, `sales`, `admin`, `billing`, `hr`, etc.). |
| `isFreeWebmail` | `boolean` | `true` if the domain is a public consumer webmail provider (`gmail.com`, `icloud.com`, etc.). |
| `verifiedAt` | `string` | ISO 8601 UTC timestamp of verification. |

#### Example Output

```json
{
  "email": "jane.doe@apify.com",
  "domain": "apify.com",
  "deliverabilityStatus": "DELIVERABLE_MX_VALID",
  "qualityScore": 95,
  "syntaxValid": true,
  "hasMxRecords": true,
  "mxProvider": "Google Workspace",
  "mxRecords": ["aspmx.l.google.com", "alt1.aspmx.l.google.com"],
  "isDisposable": false,
  "isRoleAccount": false,
  "isFreeWebmail": false,
  "verifiedAt": "2026-11-06T13:44:42.000Z"
}
```

***

### Pricing (Pay-Per-Event)

| Event Name | Price (USD) | When is it charged? |
|---|---:|---|
| `apify-actor-start` | `$0.00005` | Once when the Actor run starts after input validation passes. |
| `result-item` | `$0.00060` | Per unique verified email record (`$0.60` per 1,000 emails). Duplicate emails in the same input are deduplicated for free. |

***

### Standby MCP & AI Agent Integration

Enabled for **Apify Standby Mode** (`webServerMcpPath: "/mcp"`). AI Agents can call the `verify_emails_bulk` MCP tool or `POST /run` REST endpoint for sub-second verification.

***

### Part of the B2B Intelligence Suite

| Actor Slug | Primary Use Case | Input → Output |
|---|---|---|
| **`b2b-domain-contact-enricher`** | Fast company domain, DNS MX provider & tech stack enrichment | `domain` → Emails, Socials, MX Provider, Tech Stack |
| **`bulk-email-mx-verifier`** *(This Actor)* | High-speed bulk email syntax, DNS MX & disposable verification (`$0.60/1k`) | `emails[]` → Deliverability Status & Quality Score (`0–100`) |
| **`ats-career-job-listing-api`** | Real-time hiring signals from Greenhouse, Lever & Ashby career boards | `boardSlug` → Normalized Open Roles & Departments |
| **`b2b-company-lead-finder`** | Decision-maker email permutation & MX-verified company lead generation | `domains[] + contacts[]` → Verified Executive Emails & Firmographics |

***

### Data Privacy & Responsible Use

- **Zero Data Retention:** Email lists are processed in-memory and written strictly to your private Apify run dataset. No email addresses are logged or shared with third-party APIs.
- **Non-Intrusive Verification:** Uses passive RFC syntax inspection and public DNS `MX` resolution without sending unsolicited test emails to target inboxes.

***

### FAQ & Support

- **Are duplicate emails in my input charged twice?** No. Both our input validator and `CHARGE_LEDGER_V1` deduplicate email addresses automatically so you only pay once per unique email.
- **Support & Issues:** Report questions or feature requests in the **Issues** tab on the Apify Store page.

# Actor input Schema

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

List of email addresses to verify (e.g. \["support@apify.com", "john@stripe.com"]).

## `maxItems` (type: `integer`):

Maximum number of unique email addresses to process.

## Actor input object example

```json
{
  "emails": [
    "support@apify.com",
    "info@stripe.com",
    "test@mailinator.com"
  ],
  "maxItems": 50
}
```

# Actor output Schema

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

Structured items stored in the default 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": [
        "support@apify.com",
        "info@stripe.com",
        "test@mailinator.com"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("apexsignal/bulk-email-mx-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": [
        "support@apify.com",
        "info@stripe.com",
        "test@mailinator.com",
    ] }

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

```

## MCP server setup

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