# Bulk Email List Hygiene Check (Syntax · MX · Disposable · Role) (`nexgenwatch/bulk-email-list-verifier`) Actor

Clean an email list before you send — one email_verification_check row per address, answered from syntax and DNS alone: is the address well-formed, does the domain publish MX records (or an RFC-7505 null MX that says "no mail here").

- **URL**: https://apify.com/nexgenwatch/bulk-email-list-verifier.md
- **Developed by:** [NexGen Watch](https://apify.com/nexgenwatch) (community)
- **Categories:** Automation, Developer tools, Lead generation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $33.50 / 1,000 email verification checks

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
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 List Hygiene Check (Syntax · MX · Disposable · Role)

**Clean an email list before you send** — one `email_verification_check` row per address, answered from **syntax and DNS alone**: is the address well-formed, does the domain publish MX records (or an RFC-7505 null MX that says "no mail here"), does its primary mail host actually resolve, is the domain a known **disposable / temporary-mailbox provider**, and is the local part a **role account** (info@, support@ …) or a **free consumer provider** (gmail.com …). No third-party verification API, no key, nothing retained.

**What it deliberately does not claim.** It never says an address is *deliverable*. Confirming that a specific mailbox exists needs an SMTP conversation on port 25, and the platform blocks outbound port 25 — so instead of a guess dressed up as a verdict, every row carries `mailbox_confirmed: null` and a `mailbox_note` saying so. The definitive verdicts are `INVALID_SYNTAX`, `NO_MX`, `NULL_MX`, `DISPOSABLE`, `MX_UNRESOLVED` and `MX_VALID` — each one **billed once**, because each one is a real answer. `DNS_FAULT` (the resolver did not answer) and `UNPARSEABLE` are surfaced and **never billed**, and a batch with no definitive verdict fails loud and bills nothing.

Output is one `email_verification_check` row per result; billing is pay-per-event, the value event being one email verification check (a $0.02 start fee per run, then $0.05 per email verification check).

No login, no API key and no CAPTCHA solving are involved: the source is read logged-out with an identified contact User-Agent.

### 📊 Sample Output

[![Bulk Email List Hygiene Check (Syntax · MX · Disposable · Role) sample output — a table of real email verification check rows (input, domain, disposable, free_provider) from run sdoJjtAhN6YdcOzwM on build 0.1.10](https://api.apify.com/v2/key-value-stores/80Y7h3rmVN5CWK7Mw/records/bulk-email-list-verifier-sample)](https://apify.com/nexgenwatch/bulk-email-list-verifier?fpr=2ayu9b)

Real rows from run `sdoJjtAhN6YdcOzwM` on build 0.1.10 (2026-09-24), the same input as the Quick start below — every value is as the source published it (emails masked, long text shortened):

| input | domain | disposable | free_provider | mailbox_note | verdict |
|---|---|---|---|---|---|
| \[email on record] | apify.com | False | False | mailbox not probed: SMTP (port 25) is blocked on the platform; this ve | MX_VALID |
| \[email on record] | example.com | False | False | mailbox not probed: SMTP (port 25) is blocked on the platform; this ve | NULL_MX |
| not-an-email |  |  |  | mailbox not probed: SMTP (port 25) is blocked on the platform; this ve | INVALID_SYNTAX |
| \[email on record] | gmail.com | False | True | mailbox not probed: SMTP (port 25) is blocked on the platform; this ve | MX_VALID |
| \[email on record] | mailinator.com | True | False | mailbox not probed: SMTP (port 25) is blocked on the platform; this ve | DISPOSABLE |

The run finished with the status message: `NORMAL: 5 resolved (0 not-found, 0 ambiguous, 0 service-fault, 0 unparseable) of 5 | answers billable=5 | email_verification_check charged=5`

### ✅ What you get

Each row is flat JSON with these fields (from the dataset schema and the sample run; a field the source does not publish for a given row is `null`):

- `record_type` (string/null) — e.g. `email_verification_check`
- `input` (string/null) — e.g. `[email on record]`
- `domain` (string/null) — e.g. `apify.com`
- `mx_host` (string/null) — e.g. `aspmx.l.google.com`
- `mx_count` — e.g. `5`
- `mx_resolves` — e.g. `True`
- `disposable` — e.g. `False`
- `free_provider` — e.g. `False`
- `role_account` — e.g. `True`
- `mailbox_confirmed` — null in every sample row
- `mailbox_note` — e.g. `mailbox not probed: SMTP (port 25) is blocked on the platform; this verdict is a`
- `source` (string/null) — e.g. `syntax + DNS (MX, A/AAAA of the primary MX) + bundled disposable/free-provider/r`
- `verdict` (string/null) — e.g. `MX_VALID`
- `unbilled_reason` (string/null) — null in every sample row
- `smtp_code` (string/null) — null in every sample row
- `catch_all` (boolean/null) — null in every sample row

### ⚙️ Sample inputs

**1. Quick start — the Store example (this is what the sample above came from)**

```json
{
  "emails": [
    "support@apify.com",
    "noreply@example.com",
    "not-an-email",
    "jane.doe@gmail.com",
    "info@mailinator.com"
  ]
}
```

The sample run charged exactly: 1 × $0.02 apify-actor-start + 5 × $0.05 email_verification_check = **$0.27** on the Free tier — every delivered row was billed.

This actor takes no size cap or filter beyond the input above, so the Store example is the one input to run; put it on a schedule to keep the data current.

### 🧾 JSON sample record

One real record from run `sdoJjtAhN6YdcOzwM`, exactly as it lands in the dataset (emails masked, long text shortened):

```json
{
  "record_type": "email_verification_check",
  "input": "[email on record]",
  "domain": "apify.com",
  "mx_host": "aspmx.l.google.com",
  "mx_count": 5,
  "mx_resolves": true,
  "disposable": false,
  "free_provider": false,
  "role_account": true,
  "mailbox_confirmed": null,
  "mailbox_note": "mailbox not probed: SMTP (port 25) is blocked on the platform; this verdict is about the address form and the domain",
  "source": "syntax + DNS (MX, A/AAAA of the primary MX) + bundled disposable/free-provider/role lists; no SMTP, no third-party API",
  "verdict": "MX_VALID",
  "unbilled_reason": null
}
```

### 🔧 How it works

**Transport.** Plain HTTPS from the Apify platform, no proxy. Every request carries an identified contact User-Agent.

**Charging.** Each email verification check is charged at the moment it is pushed (`email_verification_check`); a row that fails to charge is not delivered, so the dataset count always equals the charged count.

1

·

·

\=

;

\=

3

·

\=

\=

4

·

6

;

;

**What is not done.** No login, no cookie or CAPTCHA bypass, no private or personal-account data, no browser automation.

### 💰 Pricing example

| Event | Free | Bronze | Silver | Gold |
|---|---|---|---|---|
| Actor Start (`apify-actor-start`) | $0.02 | $0.02 | $0.02 | $0.02 |
| Email verification check (`email_verification_check`) | $0.05 | $0.045 | $0.04 | $0.0335 |

Worked at the live Free-tier price:

- 5 email verification checks: $0.02 start + 5 × $0.05 = **$0.27**
- 25 email verification checks: $0.02 start + 25 × $0.05 = **$1.27**
- 100 email verification checks: $0.02 start + 100 × $0.05 = **$5.02**

A run that delivers zero rows charges the $0.02 start fee only. A BLOCKED run (source refused) fails loud and charges no value event. The start fee is charged once per GB of run memory; the default run memory is 4096 MB.

Yield on the sample run: `NORMAL: 5 resolved (0 not-found, 0 ambiguous, 0 service-fault, 0 unparseable) of 5 | answers billable=5 | email_verification_check charged=5`.

### ⚖️ Legal & ToS

This actor reads public data only. It collects only what the source publishes to any visitor, identifies itself with a contact User-Agent, and does not access accounts, private data or anything behind authentication. Use the output in line with the source's terms and your local law; the intended use is B2B research and monitoring.

### ❓ FAQ

**Q: Do I need an API key or a login?**\
A: No. the input schema has no key field and the actor carries no secrets.

**Q: Why did my run return 0 rows?**\
A: Read the run's status message. GENUINE_EMPTY means the source was read and had nothing in scope for your input; BLOCKED means the source refused and the run failed without billing a value event — retry later or narrow the input. A zero-row run bills the start fee only.

**Q: How fresh is the data?**\
A: Every run reads the source live at run time; nothing is cached between runs. Put it on a schedule for a continuous feed.

**Q: What formats can I export?**\
A: The dataset downloads as JSON, CSV, Excel, XML or RSS from the run's Dataset tab or the Apify API, and any run can push to a webhook or integration.

**Q: How is this different from the other NexGen Watch actors actors?**\
A: Same output shape and billing model; this one covers Bulk Email List Hygiene Check (Syntax · MX · Disposable · Role). The siblings under **Related Actors** cover the other sources or slices — run several on one schedule for a combined feed.

**Q: Are there rate limits?**\
A: The actor paces itself against the source; there is no per-buyer limit beyond your Apify plan's concurrency.

### 🆘 Troubleshooting

- **Run FAILED with BLOCKED** → the source refused the request or changed its page shape → nothing was billed beyond the start fee; retry after a while, and if it persists open an Issue with the run id.
- **Fewer rows than expected** → the source had fewer items in scope → widen the input.
- **Input validation error on start** → a field is outside the schema's allowed values → start from the Quick start block and change one field at a time.
- **Run TIMED-OUT** → a very wide request on a slow day → raise the run timeout in Run options or narrow the input; what was delivered before the timeout is still in the dataset.

### 🔗 Related Actors

- [BTS International Report Departures (route operations)](https://apify.com/nexgenwatch/bts-intl-departure-operations?fpr=2ayu9b) — Structured international airline departures performed between U.S. gateway airports and foreign airports, read directly from the official BTS Socrata…
- [BTS International Report Seats (route capacity)](https://apify.com/nexgenwatch/bts-intl-scheduled-seats?fpr=2ayu9b) — Structured international nonstop seat capacity from the U.S
- [BTS T-100 Airport Traffic](https://apify.com/nexgenwatch/bts-t100-airport-traffic?fpr=2ayu9b) — Structured monthly airport traffic and capacity records from the U.S. DOT Bureau of Transportation Statistics (BTS) T-100 program, read directly from…
- [Census Address Geography Check](https://apify.com/nexgenwatch/census-address-geography-check?fpr=2ayu9b) — A definitive check: does this business/property address resolve to an official U.S. Census geography, and which one?
- [ChEMBL Biotherapeutic Sequence Master](https://apify.com/nexgenwatch/chembl-biotherapeutic-sequence-master?fpr=2ayu9b) — One structured record per ChEMBL biotherapeutic — the molecule id, the HELM notation, the biocomponent array, and the description. A master index ove…
- [ChEMBL Clinical-Stage Indication Screen](https://apify.com/nexgenwatch/chembl-clinical-stage-indication-screen?fpr=2ayu9b) — One structured clinical compound record per molecule at or above the clinical phase you set — max_phase, first approval year, molecule type, route fl…
- 🏢 **About NexGenData** — NexGen Watch is NexGenData's fleet of more than 300 public data actors built on official sources, pay-per-result. Browse the catalog at [apify.com/nexgenwatch](https://apify.com/nexgenwatch?fpr=2ayu9b).

### ⭐ Found this useful?

If this actor saved you a manual check, a quick **[review on the Apify Store](https://apify.com/nexgenwatch/bulk-email-list-verifier?fpr=2ayu9b)** helps other teams find it. Feature request or a source that changed? Open it from the **Issues** tab — every one is read.

# Actor input Schema

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

Email addresses to check — syntax, the domain's MX records and whether its mail host resolves, known disposable providers, role-account and free-provider flags. No mailbox probe (the platform blocks outbound SMTP), so a valid-domain verdict is MX_VALID, never 'deliverable'. Inputs are used only for the lookups and are NOT retained beyond the run. Batch capped at 10,000.

## `userAgent` (type: `string`):

Override the transparent crawler UA.

## Actor input object example

```json
{
  "emails": [
    "support@apify.com",
    "noreply@example.com",
    "not-an-email",
    "jane.doe@gmail.com",
    "info@mailinator.com"
  ]
}
```

# 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": [
        "support@apify.com",
        "noreply@example.com",
        "not-an-email",
        "jane.doe@gmail.com",
        "info@mailinator.com"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("nexgenwatch/bulk-email-list-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",
        "noreply@example.com",
        "not-an-email",
        "jane.doe@gmail.com",
        "info@mailinator.com",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("nexgenwatch/bulk-email-list-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",
    "noreply@example.com",
    "not-an-email",
    "jane.doe@gmail.com",
    "info@mailinator.com"
  ]
}' |
apify call nexgenwatch/bulk-email-list-verifier --silent --output-dataset

```

## MCP server setup

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