# Email Validator & Verifier: Bulk, MX, Disposable, Typos (`swiftkit/email-check`) Actor

Bulk email verifier to clean email lists fast: syntax, domain and MX, disposable, role accounts, typo fixes (gmial.com → gmail.com), domain age, parked domains, SPF/DMARC and duplicates. CSV link input. No test emails sent.

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

## Pricing

from $0.50 / 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: Syntax, MX, Disposable, Typos

Clean an email list in seconds. For every address you get a clear **valid / risky / invalid**
result and the reason, plus useful flags:

- **Syntax** check (what real mail systems accept)
- **Domain and MX** check: does the domain exist and accept email?
- **Disposable / throwaway** detection (9,000+ known domains)
- **Role accounts** like info@, sales@, support@
- **Free providers** like Gmail, Outlook, Yahoo
- **Typo fixes**: `jane@gmial.com` → `jane@gmail.com`, `.con` → `.com`
- **Mail provider** behind the domain (Google, Microsoft, Zoho…)
- **Domain age** from the official registry: brand-new domains are flagged
- **Parked domains** ("for sale" parking pages) and **SPF/DMARC** setup
- **Duplicates**: `j.o.h.n+news@gmail.com` and `john@gmail.com` are the same inbox

**No test emails are sent and no mail server is contacted.** That keeps it fast, cheap and
safe for your sender reputation.

### Who it's for

- **Marketers:** clean a list before importing it into your email tool.
- **Sign-up forms and CRMs:** catch typos and throwaway addresses.
- **Sales teams:** separate personal, role and company addresses.
- **Developers and AI agents:** one call, consistent JSON.

### Input

Paste emails, one per line, send them through the API, or give a **CSV link** (for example a Google
Sheet published as CSV). Every email in the file is checked.

### Output

```json
{
  "email": "jane@gmial.com",
  "result": "risky",
  "reason": "possible_typo",
  "didYouMean": "jane@gmail.com",
  "user": "jane",
  "domain": "gmial.com",
  "isDisposable": false,
  "isRoleAccount": false,
  "isFreeProvider": false,
  "mxFound": true,
  "mxRecords": ["…"],
  "mailProvider": "Other",
  "canonical": "jane@gmial.com",
  "isDuplicate": false,
  "domainAgeDays": 8542,
  "isParked": false,
  "hasSpf": true,
  "hasDmarc": false
}
```

| result | meaning |
|---|---|
| `valid` | Correct syntax and the domain accepts email. |
| `risky` | Deliverable domain, but a typo, parked domain, disposable or role address, or a domain registered in the last 30 days. |
| `invalid` | Bad syntax, domain doesn't exist, or the domain accepts no email. |
| `unknown` | DNS didn't answer in time. Try again later. |

A `SUMMARY` record counts each result.

### Pricing

You pay **per email checked**. See the Pricing tab.

### Limits, honestly

- This tool does **not** log in to mail servers to test whether a specific mailbox exists.
  `valid` means the address is well formed and its domain accepts mail, not that the mailbox
  is guaranteed to exist.
- The disposable list is the public-domain
  [disposable-email-domains](https://github.com/disposable-email-domains/disposable-email-domains)
  list, refreshed regularly.
- We process only the emails you send and don't store or reuse them.

### Questions?

Open an issue on the Issues tab.

# Actor input Schema

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

One email per line. Paste your list or send it through the API.

## `csvUrl` (type: `string`):

A link to a CSV or text file (e.g. a Google Sheet published as CSV). Every email in it is checked.

## `checkDomainAge` (type: `boolean`):

Look up when each company domain was registered (official RDAP). Very new domains are flagged as risky.

## `maxConcurrency` (type: `integer`):

Parallel checks. The default is fine for most lists.

## Actor input object example

```json
{
  "emails": [
    "john@stripe.com",
    "info@example.com",
    "jane@gmial.com"
  ],
  "checkDomainAge": true,
  "maxConcurrency": 20
}
```

# Actor output Schema

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

One row per email.

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

Counts of valid, risky, invalid and unknown.

# 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@stripe.com",
        "info@example.com",
        "jane@gmial.com"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("swiftkit/email-check").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@stripe.com",
        "info@example.com",
        "jane@gmial.com",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("swiftkit/email-check").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@stripe.com",
    "info@example.com",
    "jane@gmial.com"
  ]
}' |
apify call swiftkit/email-check --silent --output-dataset

```

## MCP server setup

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

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/vJwBjcrPie7zxZx62/builds/WGef0ElF3yxPQeT27/openapi.json