Email Validator API – Syntax, MX & Disposable Check

Email validator and API that checks every address for valid syntax, a real domain with MX records (DNS), disposable / temporary email providers, role accounts (info@, sales@) and common domain typos (gmial.com → gmail.com) — without sending any email or touching the mail server.

What does it do?

• Syntax check (RFC 5322 dot-atom local part, IDNA domains, length limits).
• DNS check over DNS-over-HTTPS (Cloudflare, fallback Google): NXDOMAIN, MX records, null MX (RFC 7505), A-record fallback.
• Disposable domain detection with the open-source disposable-email-domains list (CC0, ~5,000 domains, fetched fresh each run, subdomains included).
• Flags role accounts, free webmail providers and typo domains with a suggestion.
• A clear status per email: valid, risky, invalid or unknown, with the reason.
• No SMTP "ping", no email sent: safe for your sender reputation.

Use cases

• Clean signup forms and CRMs before importing leads.
• Reduce bounces before an email campaign.
• Block throwaway accounts (trial abuse) with the disposable flag.
• Fix typos like gmial.com at the point of capture.
• AI agents and automations (Make, Zapier, n8n) that need a quick email check.

Input

Field	Description
emails	Email addresses to validate (duplicates are removed). Example: info@apify.com
concurrency	Parallel domain lookups. Example: 10
maxItems	Upper limit of emails checked per run. Example: 1000

Example input:

{
  "emails": [
    "info@apify.com",
    "support@github.com",
    "test@mailinator.com",
    "hello@10minutemail.com",
    "sales@gmial.com",
    "not-an-email",
    "contact@this-domain-does-not-exist-fluye-123.com",
    "postmaster@wikipedia.org"
  ]
}

Output

Real output (first items of a run on 26 Oct 2026):

[
  {
    "email": "info@apify.com",
    "normalized": "info@apify.com",
    "isValidSyntax": true,
    "syntaxError": null,
    "domain": "apify.com",
    "domainExists": true,
    "hasMx": true,
    "mxRecords": [
      "aspmx.l.google.com",
      "alt1.aspmx.l.google.com",
      "alt2.aspmx.l.google.com",
      "aspmx2.googlemail.com",
      "aspmx3.googlemail.com"
    ],
    "isDisposable": false,
    "isRoleAccount": true,
    "isFreeProvider": false,
    "typoSuggestion": null,
    "status": "valid",
    "reason": "Syntax OK and domain accepts email (MX)"
  },
  {
    "email": "support@github.com",
    "normalized": "support@github.com",
    "isValidSyntax": true,
    "syntaxError": null,
    "domain": "github.com",
    "domainExists": true,
    "hasMx": true,
    "mxRecords": [
      "github-com.mail.protection.outlook.com"
    ],
    "isDisposable": false,
    "isRoleAccount": true,
    "isFreeProvider": false,
    "typoSuggestion": null,
    "status": "valid",
    "reason": "Syntax OK and domain accepts email (MX)"
  }
]

Export the results as JSON, CSV or Excel, read them through the API, or send them to Google Sheets, Make, Zapier, n8n or webhooks. You can also run this Actor from AI agents through the Apify MCP server.

Pricing

Pay per event: $1.80 per 1,000 emails plus $0.00005 per run start. There is no extra platform usage charge.

FAQ

Does it send emails or connect to SMTP servers? No. It only uses DNS and a public domain list, so it never contacts the mailbox. That also means it cannot confirm that a specific mailbox exists (catch-all domains look valid).

What do the statuses mean? valid = syntax OK and domain accepts mail; risky = disposable domain, typo domain or only an A record; invalid = bad syntax, domain does not exist, null MX or no mail records; unknown = DNS error.

Where does the disposable list come from? github.com/disposable-email-domains/disposable-email-domains (CC0), downloaded at the start of each run.

How fast is it? About 1,000 emails per minute; domains are cached within a run.

Can I schedule it? Yes, with Apify schedules, or call it from the API for each new signup.

Do you store my emails? Only in your own Apify dataset for the run.

Do I need a login or API key? No. It uses the source's public API; you only need an Apify account.

Can AI agents use it? Yes. Call it through the Apify API, or from Claude, Cursor or any MCP client via the Apify MCP server.

Data source and license

Sources: DNS answers from public DNS-over-HTTPS resolvers (Cloudflare 1.1.1.1, Google Public DNS) and the disposable-email-domains list (CC0 1.0). Not affiliated with Cloudflare, Google or the list maintainers.

This Actor is not affiliated with or endorsed by the data source. You are responsible for using the data in line with the source's license and terms.