Email Verifier & Validator - Bulk Syntax, MX Check, No SMTP avatar

Email Verifier & Validator - Bulk Syntax, MX Check, No SMTP

Pricing

$1.00 / 1,000 email validateds

Go to Apify Store
Email Verifier & Validator - Bulk Syntax, MX Check, No SMTP

Email Verifier & Validator - Bulk Syntax, MX Check, No SMTP

Email verifier and validator for bulk lists: syntax, MX records, disposable, role and free-provider flags, typo suggestions. No SMTP probing. $1 per 1,000 emails, DNS failures free.

Pricing

$1.00 / 1,000 email validateds

Rating

0.0

(0)

Developer

Jeremy Larsen

Jeremy Larsen

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

3 days ago

Last modified

Share

Email Verifier & Validator - Bulk, $1/1k, No SMTP

Email verifier and validator for bulk lists: paste addresses or give a CSV URL and get one row per unique email with syntax, MX/DNS, disposable-domain, role-account and free-provider flags plus typo suggestions. It never probes mail servers (no SMTP), so it does not claim a mailbox exists. You pay only for rows that were checked, and DNS failures are free.

Free to try: a new Apify account includes free monthly platform credit, enough to validate the output on a few dozen emails before you pay anything. This Actor has no hidden minimums: failed items are never billed.

How to use Bulk Email Validator

  1. Open the Actor and paste addresses into emails, or set csvUrl to a public CSV.
  2. Click Start. Duplicates are removed (case-insensitive) and validated once.
  3. Open the Output tab or download JSON/CSV/Excel. The SUMMARY record shows counts by status.
  4. Re-run rows with status unknown (DNS failure) later; they were not charged.

Pricing

Pay per event, no subscription and no compute fees on top. Price: $1.00 per 1,000 emails.

EventWhen it is chargedPrice
email-validatedOne email address checked (syntax, DNS/MX, disposable, role, free-provider).$0.001

Failed, blocked or unknown items are not billed. Set a maximum cost per run in the run options to cap spend.

Example input

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

Example output

Illustrative sample of the output shape (field names from the Actor; values shown for a disposable address).

{
"input": "bob@mailinator.com",
"email": "bob@mailinator.com",
"valid": false,
"status": "disposable",
"reason": "disposable_domain",
"domain": "mailinator.com",
"hasMx": true,
"isDisposable": true,
"isRole": false,
"isFreeProvider": false,
"didYouMean": null
}

Details and limits

Cleans an email list without contacting any mail server. For every address it checks:

CheckOutput field
Syntax (RFC 5321/5322-style, length limits, IDN domains converted to punycode)status = invalid_syntax, reason
Domain DNS: MX records, A/AAAA fallback, RFC 7505 null-MXhasMx, hasARecord, mxRecords
Disposable / throwaway domain (incl. subdomains of listed domains)isDisposable
Role account (info@, admin@, support@, noreply@ ...)isRole
Free mailbox provider (Gmail, Outlook, Yahoo, iCloud, Proton ...)isFreeProvider
Typo suggestion for common providers (gmial.com, hotmial.com, outlok.com)didYouMean

valid is true when the syntax is correct, the domain can receive mail (MX, or A/AAAA fallback) and it is not a disposable domain.

What this does NOT do (read before buying)

  • No SMTP probing. It cannot tell whether a specific mailbox (jane@company.com) exists. valid: true means "the address is well-formed and its domain accepts mail", not "the mailbox exists". Catch-all domains, full mailboxes and non-existent users on real domains pass.
  • Disposable detection is only as good as the open list (about 9 900 domains). New throwaway services are missed until the list is updated; the list in this version was fetched 2026-10-15.
  • The role and free-provider lists are short hand-curated lists, not exhaustive.
  • Typo suggestions cover about ten big providers only and are suggestions, not corrections.
  • DNS answers can change between runs (domains get new records); flags for a given domain are deterministic only while its DNS is.

Privacy

Only the emails you supply are processed. Nothing is stored beyond the run's dataset and summary (subject to your Apify retention settings). No third-party API is called; only DNS queries for the email domains are sent.

Data sources and licenses

Disposable domains: disposable-email-domains, CC0 1.0. See data/SOURCES.md.

More from PennyData

FAQ

Does it check that the mailbox exists?
No. It never opens an SMTP connection, so valid: true means well-formed with a domain that accepts mail, not that the mailbox exists. This is why it is cheap and why it cannot get your IP blocklisted.

Is it legal?
It only sends DNS queries for the email domains you supply and calls no third-party API. You are responsible for having a lawful basis to process the addresses you submit (e.g. under GDPR).

Need a custom field, a higher volume or a different source?
Open an issue on the Actor page and describe what you need; custom variants are possible.

Is it maintained?
Yes. Reports of breakage are answered through the Issues tab, and runs that fail are not billed.

Built with AI assistance (Claude); maintained by the publisher.