# Bulk Email Verifier: MX, Disposable & Role Checks (`usta/bulk-email-verifier`) Actor

For email-marketing operators and lead-generation agencies: check a pasted list for mail-server records, throwaway inbox domains, shared role mailboxes, free providers and likely typos, and get one keep / review / drop verdict per address. Does not connect to mailboxes.

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

## Pricing

$1.00 / 1,000 result rows

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 List Checker: Mail Server, Disposable, Role Flags

This **email verifier** is an **email validator** for **bulk email verification**: paste a list you already hold and get one keep / review / drop verdict per address, with mail-server, throwaway-domain, role-mailbox, free-provider and typo flags.

You paste the addresses. Each one comes back only in its own result row. The tool does not look anyone up, does not send mail, and does not connect to mailboxes.

### Input

| Field | What it does |
|---|---|
| **Email addresses** | The list you already hold. One address per item, or a newline/comma-separated block. |
| **Email addresses as text** | Optional second paste box for the same list as a block of text. Combined with the list field when both are filled. |
| **Maximum rows** | Hard ceiling on rows returned, and therefore on the cost of the run. Default 1,000. Maximum 100,000. |
| **Suggest typo fixes** | Default on. Compares each domain to 30 common free inbox providers (`gmial.com` → `gmail.com`). |
| **Proxy configuration** | Optional Apify proxy. Off by default. Mail-server checks are DNS lookups and do not go through an HTTP proxy. |

### Pricing

**Pay per result. $0.001 per row. No start fee.**

Every dataset row bills from row one, including a drop row for a malformed string. A run that returns no rows costs nothing. **Maximum rows** is the spend cap.

### Output (one row per pasted address)

One example row from a real local run on 2026-09-20 against the bundled example input (9 addresses, 5 DNS lookups):

```json
{
  "email": "ada@gmail.com",
  "syntax_ok": true,
  "domain": "gmail.com",
  "mx_found": true,
  "mx_host": "gmail-smtp-in.l.google.com.",
  "accepts_mail_fallback_a_record": false,
  "disposable": false,
  "role_based": false,
  "free_provider": true,
  "typo_suggestion": null,
  "duplicate_in_list": false,
  "verdict": "keep",
  "reason": "format ok, domain accepts mail, not a throwaway"
}
```

| Field | What it holds |
|---|---|
| `email` | The address as pasted, trimmed, with the domain in lower case |
| `syntax_ok` | Whether it looks like `local@domain` |
| `domain` | The domain, or `null` when syntax failed |
| `mx_found` | Whether DNS returned a usable MX record. `null` if the lookup timed out |
| `mx_host` | Best-priority MX host, or `null` |
| `accepts_mail_fallback_a_record` | True when there is no MX but the domain still has an A record |
| `disposable` | True when the domain is on the bundled throwaway list (8,915 domains, CC0) |
| `role_based` | True for shared mailboxes such as `support@` or `info@` |
| `free_provider` | True for the 30 common free inbox domains |
| `typo_suggestion` | A likely intended provider, or `null` |
| `duplicate_in_list` | True when the same address appears more than once in this run |
| `verdict` | `keep`, `review`, or `drop` |
| `reason` | The verdict in plain words |

A DNS timeout never drops an address. The verdict is `review` and the reason is `could not check mail server`.

### What this does not do

- It does **not** connect to mailboxes over SMTP. It does not prove an inbox exists, is full, or will accept a message.
- It does not send email, bounce-test, or catch-all probe.
- It does not scrape websites or search the web for the person behind an address.
- It does not write the pasted list to logs or to the run status record. Each address appears only in its own dataset row.
- It does not invent mail-server names. A field that could not be read is `null`.
- A `keep` is not a promise the message will land. It means format, domain mail-server, and throwaway checks passed.

### Limits

- `maxItems` is 1–100,000 (default 1,000). Further addresses are not checked.
- DNS timeout is 5 seconds per domain. Unique domains are looked up once and cached.
- The throwaway list is the copy bundled on 2026-09-20. It is not refreshed during a run.
- On this machine on 2026-09-20 the 9-address example input returned 9 rows (1 keep, 4 review, 4 drop) from 5 DNS lookups. That is the measured run, not a speed claim for a larger list.

### Refunds and support

Refunds: if a run returns zero rows for a valid input, email operations@ustechautomations.com within 7 days and we refund that run. Support: same address, replies within 2 business days.

# Actor input Schema

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

The list you already hold. One address per item. You can also paste a newline-separated or comma-separated block here. Each address is echoed only in its own result row.

## `emailsText` (type: `string`):

Optional. Same list as a newline-separated (or comma-separated) block. Combined with the list field when both are filled.

## `maxItems` (type: `integer`):

Hard ceiling on rows returned, and therefore on the cost of the run. Every row bills at the listed price from row one; there is no start fee.

## `checkTypos` (type: `boolean`):

When true, compare each domain to the 30 most common free inbox providers and fill typo\_suggestion (for example gmial.com to gmail.com).

## `proxyConfiguration` (type: `object`):

Optional Apify proxy. Leave off for a local run. This tool looks up mail servers over DNS, which does not go through an HTTP proxy.

## Actor input object example

```json
{
  "emails": [
    "support@stripe.com",
    "someone@mailinator.com",
    "jane@gmial.com"
  ],
  "maxItems": 1000,
  "checkTypos": true,
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}
```

# Actor output Schema

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

No description

## `csv` (type: `string`):

No description

## `report` (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@stripe.com",
        "someone@mailinator.com",
        "jane@gmial.com"
    ],
    "maxItems": 1000,
    "checkTypos": true
};

// Run the Actor and wait for it to finish
const run = await client.actor("usta/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@stripe.com",
        "someone@mailinator.com",
        "jane@gmial.com",
    ],
    "maxItems": 1000,
    "checkTypos": True,
}

# Run the Actor and wait for it to finish
run = client.actor("usta/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@stripe.com",
    "someone@mailinator.com",
    "jane@gmial.com"
  ],
  "maxItems": 1000,
  "checkTypos": true
}' |
apify call usta/bulk-email-verifier --silent --output-dataset

```

## MCP server setup

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