# Bulk Email Verifier ✅📧 (`contactminerlabs/bulk-email-verifier`) Actor

🔍 Verify Bulk Email Lists

Enter your email list to check email validity, MX records, mailbox providers & domain configuration. Identify invalid or risky addresses and clean your contacts for better deliverability. Perfect for email marketing, lead generation, sales outreach & CRM data cleaning ⚡📊

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

## Pricing

from $0.00005 / actor start

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 – Clean Email Lists: MX, Mailbox Provider (Google Workspace / Microsoft 365), SPF, DMARC, Disposable, Role & Typos 📧

**Bulk Email Verifier** checks **thousands of emails in minutes** and tells you, for each one, if it is **ok, risky, invalid or unknown**, with a **score from 0 to 100**, the **reason**, the **mailbox provider** (Google Workspace, Microsoft 365, Zoho, OVHcloud, GoDaddy…), the **security gateway** (Proofpoint, Mimecast…), **SPF and DMARC** of the domain, **disposable, free-provider and role addresses** (info@, sales@…), and **typo suggestions** (`john@gmial.com` → `john@gmail.com`).

Paste a list, give a **CSV / Google Sheets link**, or plug in the **dataset of any other actor** (lead and email scrapers): the other columns (name, company, website…) are kept next to each result. **No email is ever sent.**

Perfect for **cold email and outbound teams, sales and lead generation agencies, marketers cleaning newsletters, CRM admins, recruiters, and anyone who wants fewer bounces and a better sender reputation**.

### ✨ Why this Bulk Email Verifier?

- 🎯 **Clear verdict** – `ok`, `risky`, `invalid` or `unknown`, a 0–100 `score` and a readable `reason` for every email
- 🏢 **Mailbox provider** – Google Workspace, Gmail, Microsoft 365, Outlook.com, Zoho, Proton, Yahoo, iCloud, OVHcloud, IONOS, GoDaddy, Namecheap, Titan, Rackspace, Amazon WorkMail… (30+): split your sending by provider
- 🛡️ **Security gateway** – Proofpoint, Mimecast, Barracuda, Cisco, Sophos, Trend Micro… (stricter filtering)
- 🔐 **SPF & DMARC** – presence and DMARC policy (`none`, `quarantine`, `reject`): signs of a real, well-run business domain
- 🗑️ **Disposable inboxes** (yopmail, mailinator, 10minutemail… 170+ domains), **no-reply / system addresses**, **role addresses** (info@, sales@, support@…), **free providers** (Gmail, Yahoo, Hotmail…)
- ✍️ **Typo fixes** – `gmial.com`, `hotmial.com`, `yaho.com`, `.con`… with a `didYouMean` suggestion
- 🚫 **Bounces caught** – bad syntax, domain does not exist, no mail server, "null MX" (domain that refuses all emails)
- 🔗 **Works with your other actors** – give a dataset ID: every email of every row is checked, the row is kept (`source`)
- 📄 **CSV & Google Sheets** – paste a public link; the "email" column is found automatically, the other columns are kept
- 💸 **Pay only for good emails** – choose "Only ok emails": invalid and risky ones are not delivered, not charged
- 🧹 **Clean list included** – a ready-to-import CSV of the ok emails (`CLEAN_EMAILS`), plus a `SUMMARY` (counts by status, reason, provider)
- ⚡ **Fast** – each domain is checked once, whatever its number of emails; up to 500,000 emails per run; duplicates removed
- 📤 **Export anywhere** – JSON, CSV, Excel, XML, HTML, API, Zapier, Make, n8n, Google Sheets, HubSpot

### 🔍 What does it check?

| Field | Description |
| --- | --- |
| `email` / `normalizedEmail` | As given / cleaned (lower case, `mailto:` and `<>` removed, international domains converted) |
| `status` | `ok` · `risky` · `invalid` · `unknown` |
| `score` | 0–100 (100 = best) |
| `reason` | Why (e.g. `domain does not exist`, `disposable inbox`, `possible typo of gmail.com`) |
| `didYouMean` | Suggested correction of a typo |
| `isValidSyntax` | Address well formed |
| `domain` / `domainExists` / `acceptsEmail` | Domain checks |
| `mxRecords` / `mailServer` | Mail servers of the domain |
| `mailboxProvider` / `securityGateway` | Who hosts the mailbox / filters the emails |
| `hasSpf` / `hasDmarc` / `dmarcPolicy` | Email security of the domain |
| `isDisposable` / `isFreeProvider` / `isRoleAddress` / `isNoReply` | Type of address |
| `sourceType` / `source` | Where the email came from (`list`, `file`, `dataset`) and the other fields of its row |
| `checkedAt` | Date and time of the check |

**Statuses:**

- ✅ `ok` – well-formed address on a domain that receives emails
- ⚠️ `risky` – may not reach a person: disposable, no-reply, possible typo, domain without MX record
- ❌ `invalid` – will bounce: bad syntax, domain does not exist, no mail server, null MX
- ❔ `unknown` – the domain did not answer (rare; run again later)

### 🛠 How to verify emails (4 steps)

1. **Paste your emails** (one per line, or use **Bulk edit**) – or give a **public CSV / Google Sheets link** – or the **ID of a dataset** of another actor
2. Choose **which rows to deliver**: all, ok + risky, or only ok
3. Keep **SPF and DMARC** on for the full domain check
4. Click **Start**

Download your results in **JSON, CSV, Excel, XML or HTML**, or the ready **clean list** (`CLEAN_EMAILS`). Two views: **Results** and **Domain details**.

### 💡 Tips

🔹 **Cold email**: send only to `ok` emails; keep `risky` ones for a manual review; never send to `invalid`
🔹 **Split by provider**: Google Workspace and Microsoft 365 filter differently – use `mailboxProvider` to plan your sending
🔹 **Fix, don't drop**: check `didYouMean` – `bob@gmial.com` is a real lead with a typo
🔹 **Role addresses** (info@, sales@) are fine for small businesses, less for personal outreach – filter with `isRoleAddress`
🔹 **Chain it**: run a lead scraper, then give its dataset ID here to clean the emails before your CRM
🔹 **Google Sheets**: share the sheet ("Anyone with the link") and paste its link – the right tab is read with its `gid`

### 🎯 Use cases

📬 **Cold email & outbound** – fewer bounces, protected domains and sender reputation
🧲 **Lead generation agencies** – deliver clean, verified lists to clients
📰 **Newsletters & marketing** – clean old lists before a campaign
🗂️ **CRM hygiene** – find dead domains, typos and disposable sign-ups
🧑‍💼 **Recruiting & sales ops** – check contacts before outreach
🔬 **Market research** – which providers and security gateways companies of a list use

### 📥 Input

Input example:

```
{
  "EMAILS": ["info@apify.com", "john.doe@gmial.com"],
  "FILE_URL": "https://docs.google.com/spreadsheets/d/.../edit#gid=0",
  "DATASET_ID": "",
  "OUTPUT": "all",
  "CHECK_DOMAIN_SECURITY": true,
  "KEEP_SOURCE_FIELDS": true,
  "MAX_EMAILS": 0
}
```

| Field | Type | Description |
| --- | --- | --- |
| `EMAILS` | string\[] | 📧 Emails to check (one or more per line) |
| `FILE_URL` | string | 📄 Public CSV / TXT link (Google Sheets, Drive, Dropbox, direct link) |
| `DATASET_ID` | string | 🔗 Dataset of another actor of your account |
| `OUTPUT` | string | 🎯 `all`, `ok_and_risky` or `ok_only` (only delivered rows are charged) |
| `CHECK_DOMAIN_SECURITY` | boolean | 🛡️ Also check SPF and DMARC (default on) |
| `KEEP_SOURCE_FIELDS` | boolean | 🗂️ Keep the other fields of the file / dataset row (default on) |
| `MAX_EMAILS` | integer | 🔢 Maximum emails to check (0 = all) |

### 🧾 Output example

```
{
  "email": "John.Doe@Acme.com",
  "normalizedEmail": "john.doe@acme.com",
  "status": "ok",
  "reason": "domain receives emails",
  "score": 100,
  "isValidSyntax": true,
  "domain": "acme.com",
  "domainExists": true,
  "acceptsEmail": true,
  "mxRecords": ["aspmx.l.google.com", "alt1.aspmx.l.google.com"],
  "mailServer": "aspmx.l.google.com",
  "mailboxProvider": "Google Workspace",
  "securityGateway": null,
  "isDisposable": false,
  "isFreeProvider": false,
  "isRoleAddress": false,
  "isNoReply": false,
  "hasSpf": true,
  "hasDmarc": true,
  "dmarcPolicy": "reject",
  "didYouMean": null,
  "checkedAt": "2026-10-29T10:30:12.213Z",
  "sourceType": "file",
  "source": { "First name": "John", "Company": "Acme" }
}
```

### ❓ FAQ

**Is any email sent?**
No. Only public DNS records of each domain are read (mail servers, SPF, DMARC). No message is sent and no mail server is contacted.

**Does it check that the mailbox itself exists?**
No – and we say it clearly. Testing a mailbox means connecting to the company's mail server and pretending to send an email (SMTP); cloud platforms block it, many servers (Microsoft 365, Yahoo, catch-all domains) accept every address anyway, and repeated probes can get IPs blacklisted. This actor checks everything that can be checked reliably: syntax, domain, mail servers, provider, security, disposable, role, typos. `ok` means "well-formed address on a domain that receives emails".

**What is a "null MX"?**
A record by which a domain says "I never receive emails" (RFC 7505). Every email to it bounces: status `invalid`.

**Why `risky` for an address without MX record?**
The domain has no mail server record, only a website address. Some servers still accept emails this way, but often they bounce.

**Which file formats?**
CSV (comma, semicolon or tab) and plain text. If a column is called `email` / `e-mail` / `mail` / `courriel`…, that column is read and the other columns are kept; otherwise every email of the file is read.

**How many emails per run?**
Up to 500,000. Each domain is checked once, so lists with many emails on the same domains are very fast.

**Is it legal?**
The actor only reads public DNS records and sends nothing. You are responsible for how you use your lists: follow anti-spam and privacy laws (GDPR, CAN-SPAM, CASL…), identify yourself and always include an unsubscribe option.

### 💰 Pricing

Simple pay-per-result model: you only pay for the rows delivered – one row per email. With **"Only ok emails"**, invalid and risky emails are not delivered and not charged.

**Price: $0.79 per 1,000 emails** 💵

### ⚠️ Disclaimer

This tool is **not affiliated with, endorsed by, or sponsored by any email provider or security vendor listed** (Google, Microsoft, Zoho, Proofpoint, Mimecast…). Results are based on public DNS records at the time of the check.

### 🔗 Related actors

- [Instagram Email Scraper – Advanced, Cheapest & Reliable 📧⚡📷](https://apify.com/contactminerlabs/instagram-email-scraper---advanced-cheapest-reliable)
- [Facebook Email Scraper – Advanced, Cheapest & Reliable 📧⚡📷](https://apify.com/contactminerlabs/facebook-email-scraper---advanced-cheapest-reliable)
- [Twitter Email Scraper – Advanced, Cheapest & Reliable 📧⚡📷](https://apify.com/contactminerlabs/twitter-email-scraper---advanced-cheapest-reliable)
- [Discord Email Scraper – Advanced, Cheapest & Reliable 📧⚡📷](https://apify.com/contactminerlabs/discord-email-scraper---advanced-cheapest-reliable)
- [LinkedIn Email Scraper – Advanced, Cheapest & Reliable 📧⚡📷](https://apify.com/contactminerlabs/linkedin-email-scraper---advanced-cheapest-reliable)
- [Substack Email Scraper – Advanced, Cheapest & Reliable 📧⚡](https://apify.com/contactminerlabs/substack-email-scraper---advanced-cheapest-reliable)

### 📫 Support

😊 Leave us a ⭐⭐⭐⭐⭐ review if you like Bulk Email Verifier!
🌍 Questions, custom needs or issues? Contact us through Apify or via [ContactMinerLabs 🌩️](https://apify.com/contactminerlabs).

# Actor input Schema

## `EMAILS` (type: `array`):

Paste your emails, one per line (or several per line separated by commas). Click "+ Add" or use "Bulk edit" to paste a whole list. Duplicates are removed automatically.

## `FILE_URL` (type: `string`):

Link to a public CSV or TXT file: Google Sheets share link, Google Drive, Dropbox or any direct link. If the file has an "email" column, the other columns (name, company...) are kept next to each result.

## `DATASET_ID` (type: `string`):

ID of a dataset of your account (e.g. the results of a lead or email scraper run: Storage > Datasets). Every email of every row is checked, and the row's other fields (name, website...) are kept.

## `OUTPUT` (type: `string`):

All emails or only the good ones. You only pay for the rows delivered: with "Only ok emails" the invalid and risky ones are not charged.

## `CHECK_DOMAIN_SECURITY` (type: `boolean`):

Also reads the SPF and DMARC records of each domain (signs of a real, well-configured business domain). Slightly slower.

## `KEEP_SOURCE_FIELDS` (type: `boolean`):

For a file or a dataset: keep the other fields of the row (name, company, website...) in a "source" field next to the result, ready to import into your CRM.

## `MAX_EMAILS` (type: `integer`):

Check at most this many emails (0 = all, up to 500,000 per run).

## Actor input object example

```json
{
  "EMAILS": [
    "info@apify.com",
    "john.doe@gmial.com"
  ],
  "OUTPUT": "all",
  "CHECK_DOMAIN_SECURITY": true,
  "KEEP_SOURCE_FIELDS": true,
  "MAX_EMAILS": 0
}
```

# Actor output Schema

## `overview` (type: `string`):

No description

## `cleanCsv` (type: `string`):

No description

## `summary` (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@apify.com",
        "john.doe@gmial.com"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("contactminerlabs/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": [
        "info@apify.com",
        "john.doe@gmial.com",
    ] }

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

```

## MCP server setup

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