# Email Verifier Lite: Bulk Syntax, MX & Disposable Check (`juicy_fillet/email-verifier-lite`) Actor

Clean email lists cheaply: syntax check, MX/DNS records, disposable/temporary domains (120k+), role accounts, free providers and typo fixes (gmial.com to gmail.com), with a status and 0-100 score. No SMTP.

- **URL**: https://apify.com/juicy_fillet/email-verifier-lite.md
- **Developed by:** [Xander Yushchak](https://apify.com/juicy_fillet) (community)
- **Categories:** Lead generation, Automation
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.75 / 1,000 results

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

## Email Verifier Lite: bulk syntax, MX and disposable email check

**Clean an email list fast and cheaply before you pay for full verification or hit send.** For every address you get a status, a 0-100 quality score and the reasons: whether the syntax is valid, whether the domain exists and has mail (MX) servers, whether it's a **disposable / temporary** address, a **role account** (info@, sales@...), a **free provider** (Gmail, Yahoo, Outlook...), and a **typo suggestion** (`gmial.com` → `gmail.com`, `hotmail.con` → `hotmail.com`).

> **Important:** this actor does **not** connect to mail servers (no SMTP). It can't confirm that a specific mailbox exists, only that the address is well-formed and its domain can receive email. Use it as a cheap pre-filter. It removes the obvious junk so you only send good-looking addresses to a full SMTP verifier, or straight to your campaign if a lighter check is enough.

### What it checks

| Check | How |
|-------|-----|
| Syntax | RFC 5321/5322-style rules: one `@`, allowed characters, length limits, no double or edge dots, valid domain labels and TLD. International domains (`münchen.de`) are converted to punycode. |
| Cleanup | Trims spaces, takes the address out of `"Name" <email>` and `mailto:` links, lower-cases it into `normalized`. Duplicates are removed. |
| Domain and MX | Live DNS lookup of MX records, plus A/AAAA records when there's no MX. Detects non-existent domains and "null MX" domains that say they accept no mail. Uses the system resolver, with Cloudflare DNS-over-HTTPS as a fallback. Each domain is looked up once per run. |
| Disposable | Bundled list of 121,000+ throwaway domains (Mailinator, 10minutemail, Guerrilla Mail...), including their subdomains. |
| Role account | 100+ shared-inbox names like info, sales, support, admin, billing, hr, noreply, postmaster. |
| Free provider | 150+ consumer mailbox providers: Gmail, Yahoo, Outlook/Hotmail, iCloud, AOL, Proton, GMX, Yandex, ISP mail... Useful to separate B2B from B2C leads. |
| Typo | Suggests the intended address when the domain is one or two keystrokes away from a popular provider, or has a mistyped TLD (`.con`, `.cmo`). |

### Statuses and score

| status | meaning | typical score |
|--------|---------|---------------|
| `valid_format_has_mx` | Well-formed and the domain has mail servers | 65-95 (lower for role accounts and likely typos) |
| `no_mx` | Domain doesn't exist, has no MX, or declares a null MX | 0-25 |
| `disposable` | Temporary / throwaway email domain | 10 |
| `invalid_syntax` | Not a valid email address | 0 |
| `unknown` | DNS didn't answer (rare). Retry later. | 40 |

**Rule of thumb:** keep score ≥ 80, review 50-79 (role accounts, typos), drop < 50.

### Input example

```json
{
  "emails": [
    "john.doe@gmail.com",
    "Info@Apify.com",
    "someone@gmial.com",
    "test@mailinator.com",
    "\"Jane Roe\" <jane.roe+news@outlook.com>",
    "not-an-email@"
  ]
}
```

You can paste one address per line, or comma/semicolon-separated lists.

### Output example

```json
{
  "email": "someone@gmial.com",
  "normalized": "someone@gmial.com",
  "status": "no_mx",
  "score": 25,
  "reason": "no MX record; domain has only an A/AAAA record (mail delivery unlikely)",
  "isValidSyntax": true,
  "syntaxError": null,
  "localPart": "someone",
  "domain": "gmial.com",
  "hasMx": false,
  "mxRecords": [],
  "hasARecord": true,
  "domainExists": true,
  "nullMx": false,
  "isDisposable": false,
  "isRoleAccount": false,
  "isFreeProvider": false,
  "hasPlusTag": false,
  "didYouMean": "someone@gmail.com",
  "dnsError": null,
  "checkedAt": "2026-10-05T23:40:12Z"
}
```

A `SUMMARY` record in the run's key-value store has counts by status.

### Pricing

Pay per result: **$0.75 per 1,000 emails checked** (plus a tiny per-run start fee). Duplicates are removed before checking, so you don't pay for them twice. Runs are fast: thousands of addresses per minute, because each domain is looked up only once.

### FAQ

**Does it tell me if the mailbox really exists?** No. Only an SMTP check, which talks to the recipient's mail server, can get close to that, and even it's unreliable on catch-all domains and big providers like Gmail and Outlook. This actor never contacts mail servers. That's why it's fast, cheap and won't get your IP blocklisted. Run it first, then send only the `valid_format_has_mx` addresses to a full verifier if you need mailbox-level certainty.

**Why is a real company address marked role account?** Addresses like info@ or sales@ usually reach shared inboxes. They're valid, but they reply less and complain more in cold outreach, so the score is lower. Filter on `isRoleAccount` however you like.

**Is my list stored anywhere?** Only in your own Apify run storage. Domains are looked up through DNS; full addresses are never sent to any third party.

**Where does the disposable list come from?** It's bundled from the open-source [`disposable-email-domains`](https://github.com/ivolo/disposable-email-domains) list (npm package version 1.0.62, MIT license): 121,570 domains plus 399 wildcard domains that also cover all their subdomains.

### Use it with n8n, Make or Zapier

Call the actor from n8n, Make or Zapier whenever a form submission, CRM contact or Google Sheets row arrives. Then route the row by `status` or `score`: add it to your list, flag it for review or reject it. For big lists, upload a CSV column into the `emails` field and export the results as CSV or Excel.

### More scrapers from this developer

- [Company Jobs Scraper](https://apify.com/juicy_fillet/ats-jobs-scraper): hiring signals from Greenhouse, Lever, Ashby and more
- [SEC Form D Funding](https://apify.com/juicy_fillet/sec-form-d-funding): startups that just raised money, with contacts to verify
- [App Store Reviews](https://apify.com/juicy_fillet/app-store-reviews): iOS app reviews by country
- [Bluesky Scraper](https://apify.com/juicy_fillet/bluesky-scraper): posts, profiles and search from Bluesky

# Actor input Schema

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

One email per line. You can also paste comma- or semicolon-separated lists, 'Name <email>' and mailto: links; they're cleaned automatically.

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

Check at most this many emails (after removing duplicates). Leave empty to check all. You only pay for emails checked.

## `dedupe` (type: `boolean`):

Check each address once, even if it appears several times in the list (comparison ignores letter case).

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

How many domains are looked up at the same time. Each domain is looked up only once per run, however many emails use it.

## Actor input object example

```json
{
  "emails": [
    "john.doe@gmail.com",
    "info@apify.com",
    "someone@gmial.com",
    "test@mailinator.com",
    "not-an-email@",
    "jane@no-such-domain-xyz123.com"
  ],
  "dedupe": true,
  "concurrency": 20
}
```

# Actor output Schema

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

All results saved by this run, in the default dataset.

# 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": [
        "john.doe@gmail.com",
        "info@apify.com",
        "someone@gmial.com",
        "test@mailinator.com",
        "not-an-email@",
        "jane@no-such-domain-xyz123.com"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("juicy_fillet/email-verifier-lite").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": [
        "john.doe@gmail.com",
        "info@apify.com",
        "someone@gmial.com",
        "test@mailinator.com",
        "not-an-email@",
        "jane@no-such-domain-xyz123.com",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("juicy_fillet/email-verifier-lite").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": [
    "john.doe@gmail.com",
    "info@apify.com",
    "someone@gmial.com",
    "test@mailinator.com",
    "not-an-email@",
    "jane@no-such-domain-xyz123.com"
  ]
}' |
apify call juicy_fillet/email-verifier-lite --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,juicy_fillet/email-verifier-lite"
        }
    }
}
```

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/TngAzxY7EEqsz44wy/builds/PZtD3lOa1evlJIWxl/openapi.json