# Bulk Email Validator: Clean Lists Before You Send (`feedwise/bulk-email-verifier`) Actor

Clean email lists fast: syntax, typo fixes (gmial.com to gmail.com), disposable and role addresses, free providers, mail servers (MX), mail provider (Google, Microsoft 365...) and SPF/DMARC. Each email gets valid, risky or invalid with a reason. $0.30 per 1,000.

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

## Pricing

from $0.30 / 1,000 email checkeds

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?

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 Validator — clean email lists before you send

Paste a list (or any text) and get every address marked **valid**, **risky** or **invalid**, with a
plain reason. Clean lists bounce less, protect your sender reputation and save money on your email
tool.

Every email is checked for:

- **Syntax**: malformed addresses are invalid.
- **Typos**: `jane@gmial.com` gets `didYouMean: jane@gmail.com`; `.con` is caught too.
- **Domain and mail servers**: domains that don't exist or can't receive email are invalid (MX
  records, with the standard fallback to the domain's own address).
- **Disposable addresses**: about 9,000 throwaway-inbox domains (Mailinator, 10minutemail…).
- **Role addresses**: info@, sales@, support@ and similar shared inboxes.
- **Free providers**: Gmail, Yahoo, Outlook and 80+ others, so you can separate B2B from consumer leads.
- **Mail provider**: Google Workspace, Microsoft 365, Zoho, Proofpoint, Mimecast and more.
- **SPF and DMARC**: whether the domain publishes them.

Duplicates are removed before checking, and domain lookups are cached, so a 50,000-row list takes minutes.

### What "valid" means

The domain exists and accepts email, and the address isn't disposable, a role inbox or a likely
typo. This actor **does not log in to mail servers to test individual mailboxes** (that "SMTP check"
gets cloud IPs blocklisted and is unreliable on Google and Microsoft domains anyway). Use it to
remove everything that certainly or probably bounces, for a fraction of the price of SMTP verifiers.

### Input

```json
{
  "emails": ["help@allbirds.com", "jane.doe@gmial.com", "test@mailinator.com"],
  "checkDns": true,
  "onlyValid": false
}
```

Or paste a CSV or any text into `text`; every email inside is extracted.

### Output (one row per email)

```json
{
  "email": "jane.doe@gmial.com",
  "status": "risky",
  "reason": "possible typo, did you mean gmail.com?",
  "didYouMean": "jane.doe@gmail.com",
  "isDisposable": false,
  "isRoleAccount": false,
  "isFreeProvider": false,
  "domainExists": true,
  "acceptsMail": true,
  "mxRecords": ["…"],
  "mailProvider": "Other",
  "hasSpf": false,
  "hasDmarc": false
}
```

The run's `SUMMARY` record has the totals per status.

### Pricing

Pay per email checked. With `onlyValid` on, you pay only for the valid emails that are returned.

# Actor input Schema

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

One email per line (commas and spaces also work). Up to 100,000 per run; duplicates are removed for free.

## `text` (type: `string`):

Optional. Paste a CSV, spreadsheet column or any text; every email address in it is extracted and checked.

## `checkDns` (type: `boolean`):

Look up each domain's MX, SPF and DMARC records. Turn off for a syntax, typo, disposable and role check only.

## `onlyValid` (type: `boolean`):

Save (and pay for) only emails with status valid. Risky and invalid ones are counted in the SUMMARY but not saved.

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

How many emails to check at the same time. Lookups are cached per domain.

## Actor input object example

```json
{
  "emails": [
    "help@allbirds.com",
    "jason@basecamp.com",
    "someone@gmial.com",
    "test@mailinator.com",
    "bob@notarealdomain-zz9q.com"
  ],
  "checkDns": true,
  "onlyValid": false,
  "concurrency": 20
}
```

# Actor output Schema

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

One row per email: valid, risky or invalid, the reason, and every check behind it.

# 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": [
        "help@allbirds.com",
        "jason@basecamp.com",
        "someone@gmial.com",
        "test@mailinator.com",
        "bob@notarealdomain-zz9q.com"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("feedwise/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": [
        "help@allbirds.com",
        "jason@basecamp.com",
        "someone@gmial.com",
        "test@mailinator.com",
        "bob@notarealdomain-zz9q.com",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("feedwise/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": [
    "help@allbirds.com",
    "jason@basecamp.com",
    "someone@gmial.com",
    "test@mailinator.com",
    "bob@notarealdomain-zz9q.com"
  ]
}' |
apify call feedwise/bulk-email-verifier --silent --output-dataset

```

## MCP server setup

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