# Email & Domain Validator (DNS-only) (`m8forever/email-domain-validator`) Actor

Bulk-validate email syntax, DNS/MX, disposable domains, role accounts and typos. No SMTP probing, nothing stored — privacy-first list cleaning.

- **URL**: https://apify.com/m8forever/email-domain-validator.md
- **Developed by:** [Hanxiao Yang](https://apify.com/m8forever) (community)
- **Categories:** Developer tools, Lead generation, Automation
- **Security:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $0.20 / 1,000 validated 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 & Domain Validator (DNS-only, Privacy-first)

**Keywords:** email validator, MX record check, disposable email detection, role account filter, typo domain suggestion, bulk email cleaner, no SMTP verification.

Clean email lists **without SMTP probing**. For each address: syntax, DNS/MX, disposable domain, role account (`info@`…), and typo suggestions (`gmial.com` → `gmail.com`). Nothing stored beyond your run dataset.

### Why this Actor

- **No SMTP** — never touches mail servers (safer for IP reputation)
- Fast DNS cache per domain; thousands of addresses in seconds
- Privacy-first: process in memory, write only to your Apify dataset
- Clear verdicts: `valid` · `risky` · `disposable` · `undeliverable` · `invalid` · `unknown`

### Example input

```json
{
  "emails": [
    "hello@gmail.com",
    "info@example.com",
    "test@gmial.com",
    "user@mailinator.com"
  ],
  "resolver": "system",
  "concurrency": 20
}
```

You can also paste a list into `emailsText` (newline or comma separated). Use `resolver: "doh"` (Cloudflare DoH) if system DNS is unreliable.

### Output fields

| Field | Meaning |
|---|---|
| `syntaxValid` / `syntaxError` | RFC-style syntax |
| `domainExists`, `hasMx`, `nullMx`, `mxHosts`, `hasA` | Live DNS |
| `acceptsMailLikely` | MX or A-record fallback |
| `isDisposable` / `isRoleAccount` | disposable list / role local-parts |
| `suggestedDomain` | common-provider typo fix |
| `verdict` | overall label |

### Pricing (pay per event)

- **Validated email** — $0.0002 per result (~$0.20 / 1,000)
- Actor start ~$0.00005

### Limitations

Cannot prove an individual mailbox exists (no SMTP). Disposable lists are never complete. Only process lists you are allowed to handle.

### Use cases & scheduling

- **Clean a list before a campaign** — paste emails into `emailsText`, export rows where `verdict` is `valid`.
- **Sign-up form hygiene** — detect disposable/temporary email domains and typos (`gmial.com` → `gmail.com`).
- **Filter role accounts** — drop `info@`, `sales@`, `support@` from outreach lists.
- **Recurring CRM hygiene** — schedule weekly against a fresh export so new bad domains are flagged early.
- **Bulk MX record check** — see which domains have MX, null MX, or only an A record.

Tip: create an [Apify Schedule](https://docs.apify.com/platform/schedules) for the Actor or one of the tasks below to turn it into a recurring monitor, and add a webhook/integration to get results in Slack, email or Google Sheets.

### Ready-made example tasks

One-click, pre-filled inputs you can run or copy:

- [dns-mx-email-check-demo](https://apify.com/m8forever/email-domain-validator/tasks/dns-mx-email-check-demo)
- [disposable-email-detector](https://apify.com/m8forever/email-domain-validator/tasks/disposable-email-detector)
- [email-typo-fix-and-role-account-filter](https://apify.com/m8forever/email-domain-validator/tasks/email-typo-fix-and-role-account-filter)

### FAQ

**Does it check if the mailbox really exists?**\
No. There is no SMTP probing, so it cannot confirm an individual inbox — it checks syntax, DNS/MX, disposable and role patterns.

**Why no SMTP?**\
SMTP probing hurts IP reputation and is often blocked or inaccurate on catch-all servers. DNS-only is fast and safe.

**system vs doh resolver?**\
`system` uses the platform DNS; `doh` uses Cloudflare DNS-over-HTTPS when system DNS is unreliable.

**Is my list stored?**\
Only in your own run dataset. Process only lists you are allowed to handle.

# Actor input Schema

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

List of email addresses.

## `emailsText` (type: `string`):

Newline- or comma-separated emails.

## `maxEmails` (type: `integer`):

Max emails

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

DNS concurrency

## `dnsTimeoutSecs` (type: `integer`):

DNS timeout (s)

## `resolver` (type: `string`):

Use DoH if the run environment has unreliable DNS.

## Actor input object example

```json
{
  "emails": [
    "someone@example.com",
    "info@gmial.com"
  ],
  "maxEmails": 100000,
  "concurrency": 20,
  "dnsTimeoutSecs": 5,
  "resolver": "system"
}
```

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

// Run the Actor and wait for it to finish
const run = await client.actor("m8forever/email-domain-validator").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": [
        "someone@example.com",
        "info@gmial.com",
    ] }

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

```

## MCP server setup

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

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/LSQnNribXK8K5RsbQ/builds/WOE2uCwtLYLqR9xcu/openapi.json