Bulk Email Verifier & Validator: MX, Disposable | $0.40/1k avatar

Bulk Email Verifier & Validator: MX, Disposable | $0.40/1k

Pricing

from $0.32 / 1,000 email checkeds

Go to Apify Store
Bulk Email Verifier & Validator: MX, Disposable | $0.40/1k

Bulk Email Verifier & Validator: MX, Disposable | $0.40/1k

Verify emails with DNS only, no SMTP probing. Input: list of emails. Output per address: status (valid/risky/invalid), score 0-100, reasons, MX hosts, disposable, role-account and free-provider flags, typo suggestion. $0.40 per 1,000 emails. No API key.

Pricing

from $0.32 / 1,000 email checkeds

Rating

0.0

(0)

Developer

Impakt

Impakt

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

a day ago

Last modified

Features

Limited permissions

Share

Bulk Email Verifier & Validator: Syntax, MX, Disposable, Role & Typo Checks

Agent quick reference

  • Purpose: Verify emails with DNS only, no SMTP probing.
  • Price: $0.40 per 1,000 emails (pay per event; you pay only for items returned). Set maxTotalChargeUsd on the run to cap spend.
  • Call: POST https://api.apify.com/v2/acts/mauve_bunch~email-validator-dns/run-sync-get-dataset-items?token=<APIFY_TOKEN> with the JSON input below, or via the Apify MCP server (call-actor, Actor mauve_bunch/email-validator-dns).
  • Minimal input: {"emails": ["jane.doe@gmail.com", "john@gmial.com", "info@stripe.com", "someone@mailinator.com"], "checkDns": true, "concurrency": 50, "dnsTimeoutSecs": 5, "maxEmails": 100000, "dnsResolver": "system"}
  • Output: one JSON object per item in the default dataset; a SUMMARY record in the key-value store has run counts.

Try it in one click: press Start with the four prefilled addresses and see valid, risky and typo results in about 3 seconds. $0.40 per 1,000 emails, DNS only, no SMTP probing.

Clean an email list in minutes without ever sending a probe to a mail server. This Actor checks every address for valid syntax, whether the domain exists and accepts mail (MX/DNS), disposable domains, role accounts such as info@ or sales@, free-mail providers, and likely typos like gmial.com. Each address gets a clear status (valid, risky, invalid, unknown), a 0–100 score and a list of reasons you can filter on.

It is fast and cheap because it uses DNS only. That also makes it safe for your sender reputation and your IP: no connections to recipient mail servers, no greylisting, no blocklisting.

Honest scope: DNS-based validation tells you whether an address can receive mail. It cannot confirm that a specific mailbox exists or detect catch-all domains. If you need mailbox-level verification, use an SMTP-based verifier after this cheap first pass.

What it checks

CheckWhat it catches
SyntaxMissing @, illegal characters, double dots, over-long local part or domain, bad TLD, internationalized domains (converted to punycode)
Domain existsTypos and dead domains (NXDOMAIN)
MX / mail routingDomains with no mail server, "null MX" domains that explicitly refuse mail, and domains that fall back to an A record
Disposable domainsTemporary inbox services such as Mailinator-style domains (maintained community list, subdomains included)
Role accountsadmin@, info@, support@, sales@, noreply@ and similar shared mailboxes
Free providersGmail, Outlook, Yahoo, iCloud and other consumer domains, so you can separate business from personal addresses
Typo suggestionsjohn@gmial.com becomes john@gmail.com; .con becomes .com
Gmail username rulesGmail usernames must have 6–30 letters, numbers or dots, so abc@gmail.com is flagged
Mail provider hintDetects Google Workspace, Microsoft 365, Yahoo, iCloud, Proton, Zoho and others from MX hosts

Duplicates (case-insensitive) are removed automatically and billed once.

How to use it

  1. Paste or upload your addresses into Emails (one per line, or send a JSON array via API).
  2. Click Start.
  3. Download the dataset as CSV/Excel/JSON. Filter on status = valid for a clean list, or inspect reasons to see why an address was flagged.

Input example

{
"emails": ["jane.doe@gmail.com", "john@gmial.com", "info@stripe.com", "someone@mailinator.com"],
"checkDns": true,
"concurrency": 50
}

Output example

{
"email": "john@gmial.com",
"normalizedEmail": "john@gmial.com",
"status": "risky",
"score": 20,
"reasons": ["dns_lookup_failed:ESERVFAIL", "possible_typo"],
"syntaxValid": true,
"domain": "gmial.com",
"domainExists": null,
"hasMx": null,
"mxHosts": [],
"mxProvider": null,
"isDisposable": false,
"isRoleAccount": false,
"isFreeProvider": false,
"suggestion": "john@gmail.com",
"smtpChecked": false,
"checkedAt": "2026-11-19T01:09:00.954Z"
}

Status meanings

  • valid: syntax is fine, the domain exists and has mail routing, and nothing suspicious was found.
  • risky: deliverable in principle but worth reviewing: disposable domain, role account, likely typo, or only an A record instead of MX.
  • invalid: will bounce: bad syntax, non-existent domain, no mail server, or a null-MX domain.
  • unknown: DNS did not answer in time. Re-run those addresses.

Pricing

Pay per event, no subscription:

EventPrice
Actor start$0.0001
Each unique email checked$0.0004 (about $0.40 per 1,000 emails, with discounts on paid Apify plans)

Validating 50,000 addresses costs roughly $20. Set a maximum charge per run in Apify to stay in control.

Use it from code or automation

from apify_client import ApifyClient
client = ApifyClient("YOUR_APIFY_TOKEN")
run = client.actor("YOUR_USERNAME/email-validator-dns").call(run_input={"emails": ["a@example.com", "b@gmial.com"]})
for row in client.dataset(run["defaultDatasetId"]).iterate_items():
print(row["email"], row["status"], row["reasons"])

Works with Zapier, Make, n8n and Google Sheets integrations, and as an MCP tool for AI agents that need to sanity-check addresses before writing to a CRM.

Privacy and compliance

Only the addresses you submit are processed, and only DNS queries about their domains are made; no data is sent to the recipient's mail server. The Actor does not store your list outside your own Apify run storage. The disposable-domain list comes from the community project disposable-email-domains (CC0).

Limits

  • No mailbox-level or catch-all detection (by design, to avoid SMTP probing).
  • DNS answers can vary between resolvers; a temporary DNS failure returns unknown, not invalid.
  • Role-account and free-provider lists cover the most common names and providers, not every possible one.
  • Maximum 100,000 emails per run by default (raise Max emails if needed).

FAQ

Why not check the mailbox over SMTP? Many providers block or tarpit probes, probing can hurt your IP reputation, and results are often unreliable (catch-all servers accept everything). DNS validation removes the large share of obviously bad addresses at a fraction of the price.

Does it work for international addresses? Yes, internationalized domain names are converted to punycode before lookup.

Can I keep the original order? Rows are produced in input order after duplicate removal.

How do I report a wrong result? Open an issue with the address and what you expected.

Feedback

Found this useful? A quick review on the Store helps others find it. Issues or feature requests? Open an issue and I'll reply fast.