# Bulk Email Verifier — Syntax, MX, Disposable, Role & Typo Check (`sanmarino-tools/bulk-email-verifier`) Actor

Clean email lists in bulk: syntax, MX records, disposable domains, role addresses (info@, sales@…) and typos in common domains (gmial.com → gmail.com). No SMTP probing, one DNS query per domain, duplicates not charged.

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

## Pricing

from $0.30 / 1,000 checked emails

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 Verifier — Syntax, MX, Disposable, Role & Typo Check (no SMTP)

Clean an email list in bulk before you import it or send to it. Fast, cheap, no API keys, and it never talks to anyone's mail server.

### What it checks

| Check | How | What you get |
|---|---|---|
| **Syntax** | practical RFC 5321/5322 rules; international domains (`caffè.it`) converted to punycode | normalized address, or the exact reason it is malformed |
| **Mail server (MX)** | DNS lookup of the domain's MX records; falls back to A/AAAA as RFC 5321 allows; recognizes *null MX* (RFC 7505) | top mail servers, or `domain_not_found` / `null_mx` / `no_mail_server` |
| **Disposable domains** | public, community-maintained list (disposable-email-domains, CC0), bundled with its date and checksum; subdomains included | `disposable: true` |
| **Role addresses** | `info@`, `sales@`, `noreply@`, `amministrazione@`, `segreteria@`… English and Italian, `+tags` ignored | `role: true` |
| **Typos in common domains** | `gmial.com`, `gmail.con`, `hotmial.it`, `libreo.it`… against a list of widely used providers; real look-alike domains (`tim.it`, `ymail.com`) and national domains of the same provider (`hotmail.gr`, `yahoo.dk`, `outlook.pt`) are never "corrected" | `suggestion: "mario@gmail.com"` |

One DNS query per domain, however many times it appears in your list. Duplicates (case, spaces, punycode) are removed and **not charged**.

### What it does NOT do — read this

This Actor does **not** connect to mail servers: **no SMTP** handshake, no "RCPT TO" probing. So it cannot tell you whether a specific mailbox exists. That is why no result is ever labelled "valid": the best result is **`plausible`** — the address is well formed, its domain accepts mail, and none of the checks raised a flag.

Why no SMTP: probing mailboxes is slow, frequently blocked or answered with a catch-all "yes", and it can get the prober's IP blacklisted. Pure DNS checks are fast, cheap and never touch the recipient. If you need mailbox-level certainty, use a double opt-in or an SMTP-based service on the addresses this Actor marks `plausible`.

### Results

| `status` | Meaning | Charged |
|---|---|---|
| `invalid` | malformed, domain does not exist, or domain accepts no mail | yes |
| `disposable` | disposable / temporary mailbox domain (some typo domains such as `gmial.com` are on the list too: the suggestion is still given) | yes |
| `risky` | deliverable domain, but: role address, likely typo, no MX (A record only), or non-ASCII local part | yes |
| `plausible` | all checks passed | yes |
| `unknown` | DNS did not answer in time — try again later | **no** |

The reasons are in `reasons`, as machine-readable codes: syntax codes such as `missing_at_sign`, `invalid_dots_in_local_part`, `invalid_tld`; DNS codes `domain_not_found`, `null_mx`, `no_mail_server`, `implicit_mx`, `dns_unavailable`; and `disposable_domain`, `role_address`, `possible_typo`, `non_ascii_local_part`.

### Input

```json
{
  "emails": [
    "mario.rossi@gmail.com",
    "info@example-company.it",
    "someone@gmial.com",
    "test@mailinator.com"
  ]
}
```

### Output (one dataset item per unique address)

```json
{
  "input": "someone@gmail.con",
  "email": "someone@gmail.con",
  "status": "invalid",
  "reasons": ["domain_not_found", "possible_typo"],
  "domain": "gmail.con",
  "mx": { "status": "domain_not_found", "servers": [] },
  "disposable": false,
  "role": false,
  "freeProvider": false,
  "suggestion": "someone@gmail.com"
}
```

A run summary (counts per result, duplicates, charged events, disposable-list date) is saved in the key-value store as `SUMMARY`.

### Pricing

Pay per event: a small fee per address checked. Addresses whose DNS did not answer (`unknown`), duplicates and empty entries are not charged. The Actor respects your spending limit: it checks only as many addresses as your limit allows and stops cleanly.

### Privacy

- Your addresses stay in your run and in your own dataset. The Actor keeps no copy.
- Nothing you enter is written to the logs — no addresses, no domains: only counts.
- Only the **domain** part of each address is looked up in public DNS. The full address never leaves the run.

### Limits, stated plainly

- No mailbox-level check (see above). A `plausible` address can still bounce.
- Catch-all domains and full mailboxes cannot be detected without SMTP.
- The disposable list is a snapshot of a public list; new throwaway domains appear every week. The date of the snapshot is in every run's `SUMMARY`.
- Typo suggestions cover widely used providers only; they are suggestions, never automatic corrections.

***

### In italiano

Verifica in blocco una lista di indirizzi email: sintassi, server di posta del dominio (MX), domini usa-e-getta, caselle di ruolo (info@, amministrazione@…) ed errori di battitura nei domini più diffusi (gmial.com → gmail.com). **Non contatta i server di posta (niente SMTP)**: per questo non dice mai «valida», ma al massimo `plausible`. Campi e valori dei risultati sono in inglese. Indirizzi doppi e verifiche non riuscite per il DNS non si pagano. Nei log non compare nessun indirizzo.

# Actor input Schema

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

One address per line. Duplicates (case, spaces) are removed and not charged. Only the domain part is looked up in DNS; no mail server is contacted.

## Actor input object example

```json
{
  "emails": [
    "mario.rossi@gmail.com",
    "info@example.com",
    "someone@gmial.com",
    "test@mailinator.com"
  ]
}
```

# Actor output Schema

## `results` (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": [
        "mario.rossi@gmail.com",
        "info@example.com",
        "someone@gmial.com",
        "test@mailinator.com"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("sanmarino-tools/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": [
        "mario.rossi@gmail.com",
        "info@example.com",
        "someone@gmial.com",
        "test@mailinator.com",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("sanmarino-tools/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": [
    "mario.rossi@gmail.com",
    "info@example.com",
    "someone@gmial.com",
    "test@mailinator.com"
  ]
}' |
apify call sanmarino-tools/bulk-email-verifier --silent --output-dataset

```

## MCP server setup

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