# Email Verifier & List Cleaner (`tindacloud/email-verifier`) Actor

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

## Pricing

from $0.40 / 1,000 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

## Email Verifier & List Cleaner

Check a list of email addresses **before you send anything**: syntax, whether the domain exists, whether it accepts mail, and whether it is a throwaway or a team inbox.

Built to sit right after a scraper. You pull 5,000 addresses off the web, run them through here, and keep the ones worth sending to.

### What each address gets

| Check | What it tells you |
|---|---|
| Syntax | Malformed addresses, stray characters, double @ |
| Domain resolves | The domain exists at all |
| MX records | The domain actually accepts mail, and which server handles it |
| Mail provider | Google Workspace, Microsoft 365, Zoho, Naver Works… |
| Disposable | mailinator.com and ~3,000 other throwaway domains |
| Role account | info@, sales@, support@ — goes to a team, not a person |
| Free provider | Gmail, Yahoo, Naver — useful to drop for B2B |
| Typo suggestion | `gmial.com` → `gmail.com` |

Each row ends with a **status**: `valid`, `risky` or `invalid`, plus the reason in plain words.

### Input

| Field | What it does |
|---|---|
| `emails` | The addresses to check |
| `datasetId` + `datasetEmailField` | Or read them straight from another Actor's output |
| `onlyValid` | Return only clean addresses — you pay only for those |
| `skipRoleAccounts`, `skipFreeProviders`, `skipDisposable` | Drop what you don't want |

### Output

```json
{
  "email": "cto@apify.com",
  "status": "valid",
  "reason": "syntax ok and the domain accepts mail",
  "isSyntaxValid": true,
  "domain": "apify.com",
  "domainExists": true,
  "hasMx": true,
  "mxRecords": [
    "aspmx.l.google.com",
    "alt2.aspmx.l.google.com",
    "alt1.aspmx.l.google.com",
    "aspmx2.googlemail.com",
    "aspmx3.googlemail.com"
  ],
  "mxProvider": "Google Workspace",
  "isDisposable": false,
  "isRoleAccount": false,
  "isFreeProvider": false,
  "suggestion": null,
  "checkedAt": "2026-09-20T12:35:48.645Z"
}
```

### Speed and cost

8 addresses took **5 seconds**. DNS lookups are cached per domain, so a list of 5,000 addresses across 300 domains only does 300 lookups.

### Honest note about SMTP

Paid verifiers open an SMTP conversation with the mail server to ask whether a specific mailbox exists. **This Actor does not do that** — outbound SMTP is blocked on the platform it runs on.

What that means in practice: it reliably removes malformed addresses, dead domains, domains that accept no mail, throwaway domains and team inboxes — which is the bulk of the junk in any scraped list. It cannot tell you that a particular person's mailbox is full or was deleted. If you need that last step, use this first to cut the list down, then pay a mailbox-level verifier for what remains.

### Related Actors

- [Website Contact & Email Scraper](https://apify.com/tindacloud/website-contact-scraper) — find the addresses in the first place
- [Domain, DNS & WHOIS Intelligence](https://apify.com/tindacloud/domain-dns-intelligence) — check the company behind the domain
- [LinkedIn Company Scraper](https://apify.com/tindacloud/linkedin-company-scraper) — company size, industry and HQ

# Actor input Schema

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

Addresses to check. Paste a list or connect another Actor's output below.

## `datasetId` (type: `string`):

Take the addresses from an existing dataset — for example the output of the Website Contact & Email Scraper.

## `datasetEmailField` (type: `string`):

Which field of that dataset holds the address (or a list of addresses).

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

Drop everything that is risky or invalid — you pay only for the addresses you keep.

## `skipRoleAccounts` (type: `boolean`):

Remove info@, sales@, support@ and similar team inboxes.

## `skipFreeProviders` (type: `boolean`):

Remove Gmail, Yahoo, Naver and other personal mailboxes — useful for B2B lists.

## `skipDisposable` (type: `boolean`):

Remove throwaway domains such as mailinator.com.

## `maxResults` (type: `integer`):

Total limit.

## Actor input object example

```json
{
  "emails": [
    "john@stripe.com",
    "info@gmail.com",
    "test@mailinator.com",
    "someone@gmial.com"
  ],
  "datasetEmailField": "email",
  "onlyValid": false,
  "skipRoleAccounts": false,
  "skipFreeProviders": false,
  "skipDisposable": false,
  "maxResults": 100000
}
```

# Actor output Schema

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

All results in a table view.

# 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@gmail.com",
        "test@mailinator.com",
        "someone@gmial.com"
    ]
};

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

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

```

## MCP server setup

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