# Bulk Email Verifier – Mailbox-Level Checks, $0.60 per 1,000 (`locomint/bulk-email-verifier`) Actor

Verify email lists without sending a message: syntax, domain and MX checks, disposable and free-provider detection, role flag, live mailbox check with catch-all detection, 0-100 score. Up to 50,000 addresses per run, flat $0.60 per 1,000. Nothing stored.

- **URL**: https://apify.com/locomint/bulk-email-verifier.md
- **Developed by:** [Umaid Ali](https://apify.com/locomint) (community)
- **Categories:**
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.30 / 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?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## Bulk Email Verifier – mailbox-level, no message sent

Clean an email list before you send. Every address gets a clear verdict, a reason and
a 0–100 score. Up to 50,000 addresses per run, **flat $0.60 per 1,000**, nothing stored.

| Status | Meaning |
|---|---|
| `deliverable` | The recipient's mail server confirmed the mailbox exists |
| `undeliverable` | No mail server for the domain, or the server rejected the mailbox |
| `invalid` | Not a valid email address |
| `disposable` | Throwaway / temporary mailbox service |
| `risky` | Catch-all domain: accepts every address, so the mailbox cannot be confirmed |
| `unknown` | The mail server would not answer (greylisting, timeout) – retry later |

### What is checked

1. **Syntax** – RFC-style local part and domain, TLD sanity, normalisation.
2. **Domain & mail server** – MX records (falls back to the A record), null-MX detection.
3. **Disposable domains** – 150+ throwaway services; conservative, so real leads are never lost.
4. **Free providers** – gmail, outlook, yahoo, icloud, proton, gmx… flagged, not penalised.
5. **Role accounts** – `info@`, `sales@`, `support@`… flagged; deliverable role mailboxes score 85.
6. **Live mailbox check** – a polite SMTP conversation with the recipient's server
   (EHLO, MAIL FROM, RCPT TO, QUIT), run from our own verification servers.
   **No message is ever sent.** At most 2 connections per mail server at a time.
7. **Catch-all detection** – one random-address probe per domain, cached for the run.

Your list is processed in memory and never stored by us. The dataset lives in your
Apify account under your control.

***

### ▶️ How to use it

1. Paste addresses into **Email addresses**, one per line (up to 50,000).
2. Leave **Live mailbox check** on for decisive results.
3. Run. Filter the dataset by `status` or `score` and export CSV / Excel / JSON, or call
   it from your CRM or signup flow via the API.

### ⚙️ Input

| Field | Type | Default | Notes |
|---|---|---|---|
| `emails` | string\[] | – | Up to 50,000; duplicates removed |
| `smtpCheck` | boolean | true | Live mailbox check + catch-all detection |
| `concurrency` | integer | 20 | Parallel checks (max 2 per mail server) |
| `timeoutSeconds` | integer | 10 | Per check |

### 🧾 Output

```json
{
  "email": "Info@Acme.example",
  "normalized": "info@acme.example",
  "status": "deliverable",
  "reason": "mailbox_exists",
  "score": 85,
  "syntax_valid": true,
  "domain": "acme.example",
  "mx_found": true,
  "mx_host": "mx1.acme.example",
  "disposable": false,
  "free_provider": false,
  "role_account": true,
  "catch_all": false,
  "smtp_checked": true,
  "smtp_code": 250,
  "verified_at": "2026-09-07T10:00:00+00:00"
}
```

Reasons you will see: `mailbox_exists`, `mailbox_not_found`, `no_mail_server`,
`bad_syntax`, `disposable_domain`, `catch_all_domain`, `temporary_4xx`,
`mail_server_unreachable`.

***

### 💰 Pricing

Flat **$0.60 per 1,000 addresses**, every row included. Cheaper than the market
leader, and you keep the full breakdown of every check.

***

### 🛡️ Honest limits

- Some large providers (notably Yahoo and some corporate gateways) accept every
  address at the SMTP level or refuse probes; those come back `risky` or `unknown`.
- Greylisting servers answer "try later" (4xx) – reported as `unknown`. Re-run those
  addresses after a few minutes for a decisive answer.
- Disposable detection is list-based and deliberately conservative.

***

### 🧑‍💻 Support

Issues tab, or hello@locomint.io. Pairs with the *Google Maps* and *Website* actors by
this developer – scrape the contacts, then verify them here.

# Actor input Schema

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

One address per line. Up to 50,000 per run. Duplicates are removed.

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

Ask the recipient's mail server whether the mailbox exists (no message is sent). Turns 'domain accepts mail' into 'this address exists'. Also detects catch-all domains.

## `concurrency` (type: `integer`):

Addresses checked at the same time. Per mail server it is always at most 2, to stay polite.

## `timeoutSeconds` (type: `integer`):

How long to wait for DNS and mail-server answers before giving up on one address.

## Actor input object example

```json
{
  "emails": [
    "support@apify.com",
    "no-such-mailbox-2931@apify.com",
    "someone@mailinator.com",
    "not an email"
  ],
  "smtpCheck": true,
  "concurrency": 20,
  "timeoutSeconds": 10
}
```

# Actor output Schema

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

One row per address: status (valid / undeliverable / invalid / disposable / risky / unknown), reason, 0-100 score, and every check that was run.

# 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",
        "no-such-mailbox-2931@apify.com",
        "someone@mailinator.com",
        "not an email"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("locomint/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": [
        "support@apify.com",
        "no-such-mailbox-2931@apify.com",
        "someone@mailinator.com",
        "not an email",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("locomint/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": [
    "support@apify.com",
    "no-such-mailbox-2931@apify.com",
    "someone@mailinator.com",
    "not an email"
  ]
}' |
apify call locomint/bulk-email-verifier --silent --output-dataset

```

## MCP server setup

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