# Email Validator (syntax, MX, disposable, typo, role) (`northpine-studio/email-validator-dns`) Actor

Bulk email list cleaner using syntax and DNS checks: invalid format, dead domains, missing MX, 9,000+ disposable domains, role accounts (info@, support@), free providers and typo suggestions (gmial.com). No SMTP probing, no API keys.

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

## Pricing

$3.00 / 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

## Email Validator: bulk list cleaning with syntax, MX, disposable and typo checks

Clean an email list before you send. For every address you get a verdict, a 0-100 score, and the
reasons: bad format, domain that does not exist, domain that accepts no mail, missing MX, one of
**9,000+ disposable-mail domains**, role accounts (`info@`, `support@`), free providers, and
**typo suggestions** (`jane@gmial.com` -> `jane@gmail.com`). No API keys, no browser.

### Be clear about what this is (and is not)

This Actor checks **syntax and DNS only**. It does **not** open SMTP connections to the recipient's mail
server, so it cannot tell you whether a specific mailbox exists, and it cannot detect catch-all domains.
That is deliberate: SMTP probing is unreliable from shared cloud IPs and can get IPs blocklisted.
Use it as a fast, cheap first pass that removes the obviously bad addresses; use an SMTP-based verifier
afterwards if you need mailbox-level certainty.

### Output fields

`email`, `valid`, `verdict` (`deliverable-domain`, `risky`, `invalid`, `unknown`), `score`, `reason`, `flags`,
`syntaxValid`, `normalized` (lower-cased; Gmail dots and `+tags` removed), `localPart`, `domain`,
`domainStatus` (`mx`, `a-fallback`, `null-mx`, `no-domain`, `dns-error`), `mxHosts`, `disposable`,
`roleAccount`, `freeProvider`, `suggestion`.

- `invalid`: bad syntax, non-existent domain, or a null MX (RFC 7505: the domain declares it accepts no mail).
- `risky`: syntax and domain fine but disposable, role account, likely typo, or no MX (falls back to A record).
- `unknown`: DNS timed out or failed. Retry later.
- `deliverable-domain`: format valid and the domain accepts mail. Not a promise the mailbox exists.

### Input

`emails` (list) and `concurrency` (1-50). Example: `{ "emails": ["hello@apify.com", "test@mailinator.com"] }`

### Pricing

Pay per event: **$0.0006 per address checked** (about $0.60 per 1,000), plus normal platform usage.
Duplicates in your input are removed before charging.

### Data and licences

The disposable-domain list is the open-source *disposable-email-domains* blocklist, released under CC0 1.0
(public domain). DNS lookups use the standard resolver. Local role-account and free-provider lists are our own.

Built by Northpine Studio. Found a false positive? Tell us in the Issues tab and we will fix the list or rule.

# Actor input Schema

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

Addresses to check. Duplicates are removed. Each unique address is one billable check.

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

Addresses checked in parallel (1-50).

## Actor input object example

```json
{
  "emails": [
    "hello@apify.com",
    "test@mailinator.com",
    "jane@gmial.com"
  ],
  "concurrency": 20
}
```

# Actor output Schema

## `results` (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": [
        "hello@apify.com",
        "test@mailinator.com",
        "jane@gmial.com"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("northpine-studio/email-validator-dns").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": [
        "hello@apify.com",
        "test@mailinator.com",
        "jane@gmial.com",
    ] }

# Run the Actor and wait for it to finish
run = client.actor("northpine-studio/email-validator-dns").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": [
    "hello@apify.com",
    "test@mailinator.com",
    "jane@gmial.com"
  ]
}' |
apify call northpine-studio/email-validator-dns --silent --output-dataset

```

## MCP server setup

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

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/neOgAbpTkRRyQxhFK/builds/KMkipqdBrIRUsJL41/openapi.json