Email Validator & MX Record Checker – Bulk, Disposable, Role avatar

Email Validator & MX Record Checker – Bulk, Disposable, Role

Pricing

$1.00 / 1,000 email checkeds

Go to Apify Store
Email Validator & MX Record Checker – Bulk, Disposable, Role

Email Validator & MX Record Checker – Bulk, Disposable, Role

Email validation, verification & email checker for list cleaning: RFC syntax check, MX record/DNS deliverability, disposable email detection, role-address (info@, admin@) and free-provider flags, typo suggestions (gmial.com → gmail.com). No SMTP probing, no mailbox pinging.

Pricing

$1.00 / 1,000 email checkeds

Rating

0.0

(0)

Developer

Forever Tools

Forever Tools

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

14 hours ago

Last modified

Share

Bulk Email Validator & MX Record Checker: Syntax, Disposable, Role

Clean a list of email addresses cheaply and safely. You paste a list of emails and get one row per address with syntax validity, whether the domain can receive mail (MX lookup), disposable-provider detection, role-address and free-provider flags, and typo suggestions such as gmial.com to gmail.com.

Bulk email verification without SMTP

This actor checks addresses at the DNS level. It does not connect to mail servers or ping mailboxes, so it cannot confirm that a specific mailbox exists. That is a deliberate trade-off: it is fast, cheap and has no risk of getting your IP blocklisted by mail servers. For each address you get:

  • Syntax validity (local part and domain rules)
  • MX / DNS check of the domain, with fallback to implicit MX (A/AAAA records) and detection of null MX ("domain accepts no mail")
  • Disposable provider detection (Mailinator, Guerrilla Mail, YOPmail and others from a built-in list)
  • Role address flag (info@, admin@, support@, sales@, noreply@ and similar)
  • Free provider flag (Gmail, Outlook, Yahoo and similar)
  • Typo suggestion for common misspelled domains (gmial.com, hotmial.com, outlok.com)

Input example

{
"emails": ["jane@gmial.com", "info@example.org", "x@mailinator.com", "not-an-email"],
"maxConcurrency": 20
}

emails is required; duplicates are removed. maxConcurrency (1 to 50, default 20) is how many domains are resolved in parallel, and lookups are cached per domain.

How to check if an email address is valid: output

One realistic row:

{
"email": "x@mailinator.com",
"valid": true,
"status": "risky",
"domain": "mailinator.com",
"hasMx": true,
"mxHosts": ["mail.mailinator.com"],
"isDisposable": true,
"isRole": false,
"isFree": false,
"suggestion": null,
"reason": "disposable provider"
}

status is one of invalid, risky, deliverable-domain or unknown. deliverable-domain means the syntax and domain are OK. risky means it passes DNS but is a disposable or role address, or its domain is a likely typo of a common provider (e.g. gmial.com; see suggestion). unknown means a DNS error prevented a verdict. mxHosts lists up to five mail servers.

How it works

  1. Each address is trimmed and checked for valid syntax; malformed input returns status: "invalid" with reason: "bad format". Pasted and scraped forms such as Jane Doe <jane@example.com>, mailto:jane@example.com?subject=Hi, (jane@example.com) or jane@example.com. at the end of a sentence are accepted (the email field keeps your original input), and internationalized domains such as münchen.de are checked in their punycode form.
  2. The domain is compared against the built-in disposable, free-provider and typo lists, and the local part against the role-address list (a +tag suffix is ignored, so info+news@ counts as a role address).
  3. The domain's MX records are resolved once and cached. If none exist, the actor falls back to A/AAAA records (implicit MX). A null MX record or a domain with no mail server gives valid: false.
  4. Results are pushed to the dataset one row per address, and you can export them as JSON, CSV or Excel from the Apify console or API.

Use cases

  • Clean a signup or newsletter export before importing it into your email service, to reduce hard bounces.
  • Filter disposable and role addresses out of lead lists.
  • Catch typos in form submissions and offer the corrected address from suggestion.
  • Pre-screen a list cheaply before deciding whether a full SMTP verifier is worth paying for.

Pricing: how much does email validation cost?

$0.001 per email checked, flat, no subscription. Addresses that end as unknown (a DNS error prevented a verdict) are not charged.

  • 1,000 emails = $1.00
  • 10,000 emails = $10.00
  • 100,000 emails = $100.00

Apify platform compute usage is separate from the per-email price.

Limitations

  • No mailbox-level verification. No SMTP probing, so a deliverable-domain address may still bounce if the mailbox does not exist.
  • Catch-all domains are not detected, since that requires talking to the mail server.
  • Lists are finite. Disposable, free-provider, role and typo detection use built-in lists, so a new or obscure disposable domain may not be flagged, and only common typos get a suggestion.
  • Temporary DNS failures produce unknown rows; re-run those later.

FAQ

How do I validate an email list without sending emails? Paste the list into emails. The actor checks syntax and DNS records only, and never contacts the recipient.

Can it tell me whether a mailbox really exists? No. It confirms the address can plausibly receive mail at domain level, not that the mailbox exists.

How do I detect disposable or temporary email addresses? Check isDisposable; those rows also get status: "risky".

How do I find role addresses like info@ or support@? Check isRole.

How fast is bulk email checking? Domains are resolved concurrently and cached, so a list with many addresses on the same domain needs only one lookup per domain.

Is my list stored anywhere? Addresses are processed in the run and stored only in your run's dataset.

Built by Forever Tools (AI-assisted development).

Other actors by the same developer (same flat pay-per-result pricing, no subscription):

Integrations

Run it from the Apify API, a schedule, or no-code tools: the Apify apps for Zapier, Make and n8n can start any public actor ("Run Actor") and read its dataset. AI agents can call it through the Apify MCP server.

Ready-made examples

One-click tasks you can run or copy and adapt: