Email Validator for Agents (MX, Disposable, Typo) avatar

Email Validator for Agents (MX, Disposable, Typo)

Pricing

from $2.00 / 1,000 email checkeds

Go to Apify Store
Email Validator for Agents (MX, Disposable, Typo)

Email Validator for Agents (MX, Disposable, Typo)

Validate email addresses without sending mail: syntax, DNS/MX, null MX, disposable and role detection, free-provider flag, typo suggestions, SPF/DMARC. Clear valid/risky/invalid verdicts with reason codes for AI agents and CRM hygiene.

Pricing

from $2.00 / 1,000 email checkeds

Rating

0.0

(0)

Developer

Fairquery

Fairquery

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

3 hours ago

Last modified

Share

Fairquery Apify Actor that validates email addresses without sending any email or probing SMTP servers: syntax, DNS/MX, null MX, disposable-domain and role-account detection, free-provider flag, typo suggestions ("gmial.com" → "gmail.com"), mail provider, and SPF/DMARC. Each address gets a clear valid / risky / invalid / unknown verdict with machine-readable reason codes.

When to use this Actor (LLM / tool selection)

Use it when an agent needs to:

  • Clean a lead / CRM / signup list before outreach or import
  • Decide whether an address can receive mail (domain exists, has MX, no null MX)
  • Flag disposable/temporary inboxes, role addresses (info@, sales@) or free webmail on B2B forms
  • Suggest a fix for a mistyped domain
  • See which mail provider (Google Workspace, Microsoft 365, …) and DMARC policy a domain uses

Do not use it to confirm a specific mailbox exists — that requires SMTP probing, which this Actor deliberately avoids (privacy, IP reputation and ToS reasons). valid means "well-formed, deliverable domain, no risk flags", not "mailbox confirmed".

How it works

CheckSource
SyntaxRFC 5321/5322 pragmatic subset, IDN domains → punycode
MX / A / AAAA / TXTDNS-over-HTTPS https://cloudflare-dns.com/dns-query (cached per domain, 10 domains in parallel)
Disposable domainsBundled CC0 list from disposable-email-domains (~9.9k domains, subdomains matched)
Role / free provider / typoBuilt-in lists + edit-distance against popular providers

Input

FieldTypeDefaultDescription
emailsstring[]6 sample addressesAddresses; entries may be comma/semicolon/newline lists or Name <addr>
checkDnsbooltrueMX/A lookups (turn off for syntax-only)
checkSpfDmarcbooltrueReport SPF/DMARC presence and DMARC policy
allowRoleAccountsbooltrueIf false, role addresses → risky
allowDisposableboolfalseIf true, disposable domains are not risky
allowFreeProvidersbooltrueIf false, free webmail → risky (B2B lists)
maxEmailsint10000Safety cap per run
{ "emails": ["jane@acme.com", "info@apify.com", "bob@gmial.com"], "allowFreeProviders": false }

Output

Every row has schema_version (1.0.0), type (email | error), source_url (the DoH MX query URL), checked_at.

{
"type": "email", "input": "someone@gmial.com", "email": "someone@gmial.com", "domain": "gmial.com",
"verdict": "risky", "reasons": ["DISPOSABLE_DOMAIN", "POSSIBLE_TYPO", "IMPLICIT_MX_ONLY"],
"syntax_valid": true, "is_disposable": true, "is_role_account": false, "is_free_provider": false,
"did_you_mean": "someone@gmail.com", "domain_exists": true, "has_mx": false, "null_mx": false,
"implicit_mx": true, "mx_records": [], "mail_provider": null, "has_spf": false, "has_dmarc": false, "dmarc_policy": null,
"source_url": "https://cloudflare-dns.com/dns-query?name=gmial.com&type=MX"
}

Reason codes: INVALID_SYNTAX, DOMAIN_NOT_FOUND, NULL_MX, NO_MAIL_SERVER (→ invalid); DISPOSABLE_DOMAIN, ROLE_ACCOUNT, FREE_PROVIDER, POSSIBLE_TYPO, IMPLICIT_MX_ONLY (→ risky depending on the allow* flags); DNS_NOT_CHECKED (→ unknown).

Error rows (machine-readable, never charged)

{ "type": "error", "code": "DNS_LOOKUP_FAILED", "message": "DoH MX acme.com -> HTTP 503", "retryable": true, "input": "jane@acme.com", "domain": "acme.com" }

Codes: INPUT_EMPTY, MAX_EMAILS_EXCEEDED, DNS_LOOKUP_FAILED. Duplicate addresses (case-insensitive) are skipped and counted in the summary.

Run summary

Key-value store record RUN_SUMMARY: emails checked, duplicates skipped, verdict counts, domains checked, DNS request count, echoed input.

Pricing

Pay per event: email-checked per email row. Error rows are never charged. See the Store pricing tab.

Memory / runtime

Default 256 MB. No browser, no proxy. ~1,000 emails across a few hundred domains finish in well under a minute.

MCP / Apify tools

Call from agents via Apify MCP (https://mcp.apify.com, authenticated with your Apify token), Actor fairquery/email-validator-mx-disposable:

{ "actor": "fairquery/email-validator-mx-disposable", "input": { "emails": ["jane@acme.com"] } }

Read dataset items (type == "email") and the RUN_SUMMARY record. A standalone stdio MCP server lives in the GitHub repo under mcp/.

Local development

npm install
npx apify run # uses input defaults, or storage/key_value_stores/default/INPUT.json
npm test

Kits & templates

Optional guides from Fairquery for wiring this Actor into agents and automations (the Actor works fine without them):

Disclaimer

DNS-based validation cannot guarantee a mailbox exists or accepts mail. Use results to reduce bounces, not as proof of deliverability. Comply with anti-spam law (CAN-SPAM, GDPR/ePrivacy) when emailing.