# Bulk Email Verifier & Validator | Email Checker API & MCP (`zenisbit.com/bulk-email-verifier`) Actor

Bulk email verifier and validator that cleans any email list and cuts bounce rates. Verify email addresses, check deliverability, and get a deliverable/risky/undeliverable verdict with a 0–100 quality score, plus catch-all, disposable and role detection. Import a pasted list, CSV or Google Sheet.

- **URL**: https://apify.com/zenisbit.com/bulk-email-verifier.md
- **Developed by:** [Zenisbit](https://apify.com/zenisbit.com) (community)
- **Categories:** Lead generation, Automation, Jobs
- **Stats:** 21 total users, 3 monthly users, 96.6% runs succeeded, 2 bookmarks
- **User rating**: 5.00 out of 5 stars

## Pricing

from $4.50 / 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.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/platform/actors/running/actors-in-store#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

## **Email Verifier & Validator — Bulk Email Verification & List Cleaning**

**Bulk email verifier and validator** that checks any list of email addresses and tells you which are safe to send to. Verify emails, check deliverability, and clean your list — every address comes back with a clear **status** (`safe`, `invalid`, `catch_all`, `role_account`, `disposable`, `spamtrap`, and more), a 0–100 quality score, and deliverability flags like `is_deliverable` and `is_safe_to_send`. Paste a list or import a CSV or Google Sheet, and export the results to CSV, Excel, JSON, or straight into your CRM.

> ⚠️ **Free Apify plan: 50 free email verifications in total (lifetime).** Upgrade to any paid Apify plan to verify unlimited addresses — and higher plan tiers get a per-email discount.

### **Why verify your email list?**

Sending to bad email addresses hurts everything: hard bounces pile up, your sender reputation drops, and your good emails start landing in spam. This email verification Actor checks each address for you — mailbox by mailbox — so you can remove the junk before you hit send, cut your bounce rate, and protect your domain.

### ✅ **Why this email verifier is more accurate**

Most bulk email checkers run raw SMTP probes from datacenter IP addresses. Mailbox providers block port 25 from those IPs, so **Gmail, Yahoo, and Outlook addresses come back as false "catch-all" or "unknown"** — and you either bin good contacts or trust bad ones.

This Actor verifies on managed verification infrastructure instead, so you get:

- **Accurate results for Gmail, Yahoo, and Outlook**, not false catch-alls.
- **No proxies to configure** and no port-25 blocking to work around.
- **True catch-all detection** — know when a domain accepts everything (and is genuinely risky), rather than guessing.

The result: you act on accurate verdicts instead of guesses — fewer bounces, a cleaner list, and a protected sender reputation.

### 🔧 **How bulk email verification works**

1. **You provide the emails** — paste them directly, or import a CSV file or Google Sheet and name the column that holds the addresses.
2. **Quick clean-up** — duplicates are removed and clearly malformed addresses are flagged as invalid at no cost, so you only pay to verify real candidates.
3. **Deep verification** — each remaining address is checked against the receiving mail server: does the domain exist, is there a valid mail (MX) setup, does the mailbox actually accept mail, is it a catch-all, disposable, or role account?
4. **You get clean results** — one row per address with a clear status, a 0–100 quality score, and deliverability flags, written to your dataset.

### ✨ **Features**

- **Deliverability status** for every address — `safe`, `invalid`, `disabled`, `disposable`, `inbox_full`, `catch_all`, `role_account`, `spamtrap`, or `unknown`.
- **One-glance verdict** — `is_safe_to_send` gives a single true/false you can filter on, no status-parsing needed.
- **Deliverability flags** — `is_deliverable`, `can_connect_smtp`, and `mx_accepts_mail` for precise filtering.
- **Quality score** (0–100) so you can set your own threshold for what's "good enough".
- **Catch-all detection** — know when a domain accepts everything (and is therefore risky).
- **Spam-trap detection** — flag known spam-trap addresses before they damage your sender reputation or get you blacklisted.
- **Disabled-mailbox detection** — tell a deactivated account apart from a plain invalid, so you stop emailing dead mailboxes.
- **Role, disposable & free-mailbox flags** — spot `info@`, throwaway domains, and free providers.
- **Free syntax pre-check** — obviously invalid addresses are caught locally and never billed.
- **Duplicate removal** — the same address is never verified (or charged) twice.
- **Flexible input** — a pasted list, a CSV file, or a Google Sheet, with column mapping.
- **Live progress** — a running progress indicator updates as your list is verified.
- **Run summary** — a per-status verdict breakdown for the whole run.

### 💼 **Use Cases**

- **Clean a cold-outreach list** before a campaign to cut bounce rates and protect your domain.
- **Validate signups** exported from your product or CRM to keep your database healthy.
- **Vet a purchased or scraped list** before trusting it.
- **Periodically re-check** an existing list, since addresses go stale over time.

### 📥 **Input**

| Field                      | Description                                                                                     |
| -------------------------- | ----------------------------------------------------------------------------------------------- |
| **Emails**                 | Paste the addresses to verify, one per line. Great for quick checks and small lists.            |
| **CSV / Google Sheet URL** | A public CSV link or a Google Sheet shared with "Anyone with the link" — ideal for large lists. |
| **Email column name**      | The column in your file that contains the addresses (required when using a file).               |

You can supply a pasted list, a file, or both. At least one is required.

### 📤 **Output**

One row per address, ready to export. Booleans are `null` when the information isn't available for that address.

| Field              | Type            | Description                                                                                                       |
| ------------------ | --------------- | ----------------------------------------------------------------------------------------------------------------- |
| `email`            | string          | The address that was checked.                                                                                     |
| `status`           | enum            | `safe`, `invalid`, `disabled`, `disposable`, `inbox_full`, `catch_all`, `role_account`, `spamtrap`, or `unknown`. |
| `overall_score`    | integer (0–100) | Quality score; higher is safer to send to.                                                                        |
| `is_safe_to_send`  | boolean         | The address is safe to send to.                                                                                   |
| `is_deliverable`   | boolean         | Mail can be delivered to the address.                                                                             |
| `is_valid_syntax`  | boolean         | The address is syntactically valid.                                                                               |
| `is_disabled`      | boolean         | The mailbox is disabled.                                                                                          |
| `is_disposable`    | boolean         | A temporary / throwaway address.                                                                                  |
| `is_role_account`  | boolean         | A role account (`info@`, `support@`, `sales@`, …).                                                                |
| `is_catch_all`     | boolean         | The domain accepts every address (catch-all).                                                                     |
| `has_inbox_full`   | boolean         | The mailbox is full (a deliverability warning sign).                                                              |
| `is_spamtrap`      | boolean         | A known spam-trap address.                                                                                        |
| `is_free_email`    | boolean         | On a free provider (Gmail, Yahoo, …).                                                                             |
| `can_connect_smtp` | boolean         | The mail server accepted an SMTP connection.                                                                      |
| `mx_accepts_mail`  | boolean         | The domain's MX records accept mail.                                                                              |
| `username`         | string          | The local part before the `@`.                                                                                    |
| `domain`           | string          | The email's domain (e.g. `gmail.com`).                                                                            |
| `mx_records`       | string\[]        | The receiving mail servers for the domain.                                                                        |

### 💳 **Pricing**

Pay per email that receives a real verification result — your exact rate depends on your Apify plan tier (higher tiers get a discount); see the pricing shown above. Addresses removed as duplicates or caught by the free syntax pre-check are **not** charged, so you only pay for genuine checks. That's a fraction of Hunter or ZeroBounce, with accuracy that cheap raw-SMTP tools can't match.

### 🚧 **Limits**

- **Free Apify plan:** **50 free verifications in total** per account (lifetime, across all runs). Any paid Apify plan removes the limit, and higher plan tiers get a per-email discount.
- On a paid plan, handle lists of virtually any size — up to **500,000 emails per run**, verified in consecutive batches within a single run.
- "Unknown" results can happen when a mail server is slow or temporarily unreachable; re-running those later often resolves them.

### 📞 **Questions or Support?**

Something not working as expected, or a feature you'd like to see? Reach out through the Actor's support contact on Apify — we respond fast and we're happy to help.

# Actor input Schema

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

Paste or type the email addresses to verify, one per line. Best for quick checks and small lists.

## `fileUrl` (type: `string`):

Optional: upload a CSV file, or paste a public CSV link or a shared Google Sheet containing a column of emails. Use this for large lists.

## `emailColumn` (type: `string`):

The exact name of the column that holds the email addresses (case-insensitive). Required when a file URL is set.

## Actor input object example

```json
{
  "emails": [
    "deliverable@example.com",
    "risky@example.com",
    "undeliverable@example.com"
  ],
  "emailColumn": "email"
}
```

# Actor output Schema

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

Open the dataset to view or export each email with its verification result.

## `summary` (type: `string`):

Deliverable / risky / undeliverable totals and rates for the whole 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": [
        "deliverable@example.com",
        "risky@example.com",
        "undeliverable@example.com"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("zenisbit.com/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": [
        "deliverable@example.com",
        "risky@example.com",
        "undeliverable@example.com",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("zenisbit.com/bulk-email-verifier").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print("💾 Check your data here: https://console.apify.com/storage/datasets/" + run["defaultDatasetId"])
for item in client.dataset(run["defaultDatasetId"]).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": [
    "deliverable@example.com",
    "risky@example.com",
    "undeliverable@example.com"
  ]
}' |
apify call zenisbit.com/bulk-email-verifier --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "command": "npx",
            "args": [
                "mcp-remote",
                "https://mcp.apify.com/?tools=zenisbit.com/bulk-email-verifier",
                "--header",
                "Authorization: Bearer <YOUR_API_TOKEN>"
            ]
        }
    }
}

```

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/acts/8zU3ceKru5cSY2Dp1/builds/kclgcMhAfNmpizPmg/openapi.json