# Email Verifier & Domain Validator — MX, SPF & DMARC (`vanborn_labs/email-domain-validator`) Actor

Email verifier and domain validator: syntax, typo suggestions, MX/A lookup, disposable and free-provider detection, role accounts, SPF and DMARC. Paste a list or a CSV URL. No SMTP mailbox probe (port 25 is unreliable on cloud hosts). No proxy. $0.50 per 1,000 results.

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

## Pricing

from $0.50 / 1,000 validated email or domains

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 & Domain Validator — MX, SPF & DMARC

Bulk **email verifier** and **domain validator** in one run: **syntax**, **typo suggestions**, **MX / A lookup**, **disposable** and **free-provider** detection, **role accounts**, plus **SPF** and **DMARC**. Paste a list or point at a **CSV URL**. No login, no proxy. **$0.50 per 1,000 results.**

This actor does **not** open port 25 or run an SMTP RCPT probe. Outbound SMTP is unreliable or blocked on typical cloud and Apify IPs, and a connect without a real mailbox conversation would not prove the inbox exists. You still get a clear `valid` / `risky` / `invalid` verdict from syntax and DNS.

### What it does

- ✉️ **RFC-style syntax** for emails and domains (including common `Name <addr@domain>` pastes).
- 🔤 **Typo suggestions** for slips such as `gmial.com`, `gmail.con`, `hotmial.com` or `outlok.com`.
- 📬 **Live MX and A lookup** over DNS-over-HTTPS (Cloudflare, with Google as fallback) so results stay accurate even when a local resolver is filtered.
- 🗑️ **Disposable / throwaway** domain detection (public-domain blocklist, CC0) and **free-provider** flags (Gmail, Outlook, Yahoo, and similar).
- 🏷️ **Role-account** detection (`info@`, `support@`, `admin@`, `noreply@`, …).
- 🛡️ **SPF** and **DMARC** (including the DMARC policy) for the domain.
- 📄 **Bulk input**: string lists plus an optional CSV URL, with auto-detected columns and **dedupe**.
- 🎯 A **max results** cap so you never pay more than you planned.

### Use cases

- **Clean a lead list** after a scrape: drop invalid syntax, flag throwaways and typo domains before you import the rest into a CRM or outreach tool.
- **Audit a sending domain**: confirm MX, SPF and DMARC before you warm up a mailbox or switch providers.
- **Enrich a domain list**: A/MX/SPF/DMARC in structured JSON for security reviews or vendor questionnaires.
- **Pipelines**: hook the dataset into Make, Zapier, n8n or the Apify API.

### Pricing

**$0.50 per 1,000 results** (one charged event per unique email or domain) plus a tiny $0.00005 start fee per run. Duplicates and failed CSV downloads are not charged as results. Use **Max results** to cap a run. No proxy fees. No SMTP fees.

### Input

```json
{
  "emails": [
    "support@github.com",
    "not-an-email",
    "user@mailinator.com",
    "jane@gmial.com",
    "contact@stripe.com"
  ],
  "domains": ["example.com"],
  "suggestTypos": true,
  "maxItems": 20
}
```

From a CSV:

```json
{
  "csvUrl": "https://example.com/leads.csv",
  "csvEmailColumn": "email",
  "maxItems": 100
}
```

### Output example

```json
{
  "kind": "email",
  "input": "jane@gmial.com",
  "normalized": "jane@gmial.com",
  "verdict": "risky",
  "score": 40,
  "reasons": ["typosquat_listed_as_disposable", "possible_typo", "no_mx"],
  "validSyntax": true,
  "domain": "gmial.com",
  "typoSuggestedDomain": "gmail.com",
  "typoSuggestedEmail": "jane@gmail.com",
  "isRole": false,
  "isFreeProvider": false,
  "isDisposable": true,
  "disposableNote": "This domain is on the disposable/throwaway blocklist. When a typo suggestion is also present (e.g. gmial.com → gmail.com), that usually means a typo-squat listed because it impersonates a mailbox provider, not a temporary-mail service.",
  "hasMx": false,
  "hasSpf": false,
  "hasDmarc": false,
  "smtpChecked": false,
  "smtpStatus": "skipped"
}
```

### Verdicts

- **valid** — syntax is fine, the domain resolves, mail can be routed (MX present for emails), and it is not a throwaway or obvious typo.
- **risky** — disposable domain, typo suggestion, typo-squat, or an email domain with no MX. Review before you send.
- **invalid** — malformed address or the domain does not exist in DNS (NXDOMAIN).

Typo-squat domains such as `gmial.com` (suggestion: `gmail.com`) often appear on the disposable/throwaway blocklist because they impersonate a mailbox provider, not because they are a temp-mail service. The verdict stays **risky**. The output then includes `typoSuggestedDomain`, the reason `typosquat_listed_as_disposable`, and a `disposableNote` explaining the overlap. A genuine throwaway (e.g. `mailinator.com`) is flagged `disposable_domain` without a typo suggestion.

### Notes

- DNS is queried with public DNS-over-HTTPS. No residential proxy is used or required.
- A `valid` verdict means the *domain* can receive mail, not that a specific mailbox is occupied. We do not claim ZeroBounce-style inbox verification.
- The disposable list is the [disposable-email-domains](https://github.com/disposable-email-domains/disposable-email-domains) blocklist (CC0 1.0).
- Make sure your use of any personal email addresses complies with applicable law (e.g. GDPR, CAN-SPAM) and your own outreach policy.

### FAQ

**Is this inbox verification like ZeroBounce?** No. A `valid` verdict means the *domain* can receive mail (syntax + DNS / MX), not that a specific mailbox is occupied. We do not probe SMTP on port 25, because that is unreliable on cloud hosts.

**What do the verdicts mean?** `valid` — syntax and routing look fine, not a throwaway or obvious typo. `risky` — disposable, typo suggestion, typo-squat, or an email domain with no MX. `invalid` — malformed address or the domain does not exist in DNS.

**Are typo-squat domains marked disposable?** Domains such as `gmial.com` may appear on the disposable blocklist because they impersonate a mailbox provider. The verdict stays `risky`, with a typo suggestion and a note explaining the overlap.

**Do I need a proxy?** No. DNS is queried with public DNS-over-HTTPS.

**How are duplicates billed?** Unique emails and domains are charged once. Duplicates are skipped and not charged.

### Related Van Born Labs actors

- [YouTube Video Details & Outlier Score Scraper](https://apify.com/vanborn_labs/youtube-video-details-outlier-score) — views, likes, subscribers and viral outlier score.
- [YouTube Comments Scraper](https://apify.com/vanborn_labs/youtube-comments-scraper-fast) — comments and replies, likes, pinned and hearted flags.
- [ATS Career Jobs Scraper](https://apify.com/vanborn_labs/ats-career-jobs-scraper) — Greenhouse, Lever, Ashby, Workable, SmartRecruiters and Recruitee.
- [Google News RSS Scraper](https://apify.com/vanborn_labs/google-news-rss-scraper) — headlines by keyword, topic or site.

# Actor input Schema

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

Email addresses to validate (one per line). Duplicates are skipped.

## `domains` (type: `array`):

Domain names to check for A, MX, SPF and DMARC records (no mailbox).

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

HTTP(S) URL of a CSV file with an email and/or domain column. Combined with the lists above, then deduped.

## `csvEmailColumn` (type: `string`):

Column name for emails. Leave empty to auto-detect (email, e-mail, mail, …).

## `csvDomainColumn` (type: `string`):

Column name for domains. Leave empty to auto-detect (domain, website, url, …).

## `suggestTypos` (type: `boolean`):

Suggest a corrected domain for common typos such as gmial.com or gmail.con.

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

Hard cap on validated (and charged) unique emails and domains in this run.

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

Parallel DNS-over-HTTPS lookups.

## Actor input object example

```json
{
  "emails": [
    "support@github.com",
    "not-an-email",
    "user@mailinator.com",
    "jane@gmial.com",
    "contact@stripe.com"
  ],
  "domains": [
    "example.com"
  ],
  "suggestTypos": true,
  "maxItems": 20,
  "maxConcurrency": 10
}
```

# Actor output Schema

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

One item per unique email or domain: verdict, syntax, typo suggestion, MX/A, disposable, role, free provider, SPF and DMARC.

## `runSummary` (type: `string`):

JSON counters for this run stored in the default key-value store as RUN_SUMMARY.

# 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": [
        "support@github.com",
        "not-an-email",
        "user@mailinator.com",
        "jane@gmial.com",
        "contact@stripe.com"
    ],
    "domains": [
        "example.com"
    ],
    "maxItems": 20
};

// Run the Actor and wait for it to finish
const run = await client.actor("vanborn_labs/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": [
        "support@github.com",
        "not-an-email",
        "user@mailinator.com",
        "jane@gmial.com",
        "contact@stripe.com",
    ],
    "domains": ["example.com"],
    "maxItems": 20,
}

# Run the Actor and wait for it to finish
run = client.actor("vanborn_labs/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": [
    "support@github.com",
    "not-an-email",
    "user@mailinator.com",
    "jane@gmial.com",
    "contact@stripe.com"
  ],
  "domains": [
    "example.com"
  ],
  "maxItems": 20
}' |
apify call vanborn_labs/email-domain-validator --silent --output-dataset

```

## MCP server setup

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