Email Verifier — bulk validation that tells you what it actually checked

Clean an email list before you send to it. Syntax, domain, MX records, 8,700+ disposable providers, role accounts, free mailboxes — and typo correction that turns user@gmial.com back into a reachable person instead of a rejection.

Quick start: press Start with no configuration at all. It ships with a demo list that reaches every verdict the Actor can produce, so one run shows you the whole output shape.

Sample output

normalizedEmail	status	confidence	isDisposable	isRoleAccount	didYouMean	reason
jane@vercel.com	risky	65	false	false		Domain accepts mail via mx.vercel.com. The mailbox itself was not checked.
sales@stripe.com	risky	50	false	true		Domain accepts mail via aspmx.l.google.com (role account).
test@mailinator.com	undeliverable	5	true	false		Disposable or temporary address provider.
user@gmial.com	undeliverable	5	true	false	gmail.com	Disposable provider. Did you mean user@gmail.com?
nobody@nosuchdomain-xyz.com	undeliverable	2	false	false		Domain does not exist.

Every row also carries email, local, domain, isValidSyntax, isFreeProvider, domainExists, acceptsMail, mxHost, mxCount, smtpChecked, smtpReason and mailboxExists.

Why this one

It does not pretend to have checked things it did not check. Every verifier on this Store advertises live SMTP validation. Outbound port 25 is blocked by default on most cloud hosts, so a hosted verifier either is not doing it or is not saying where from. This Actor treats that as a field, not a footnote: smtpChecked says whether the mail server was actually asked, smtpReason says what stopped it, and a mailbox that was never confirmed is never labelled deliverable. It comes back risky, with the reason spelled out.

That sounds like a weaker claim than the competition makes. It is a more useful one. A list marked "95% deliverable" that then bounces costs you your sending reputation; a list that tells you which 60% is proven and which 35% is merely plausible lets you decide.

Typos are recovered, not just rejected. gmial.com, hotmial.com, yahooo.com — a bounded edit-distance match against the twenty domains people actually mistype. A typo'd address is a real person you can still reach, and every other verifier throws them away. Suggestions are only offered for domains that do not accept mail, so a legitimate company domain is never "corrected" into Gmail.

Duplicates are removed before you are charged. A list pasted out of a CRM is routinely a third duplicates, and case and whitespace variants of the same address are the same address.

What you can do with it

• Clean a scraped lead list. Point it at the output of any contact scraper and turn onlyDeliverable on — you are charged per row returned, so filtering is genuinely cheaper, not just tidier.
• Protect a sending domain. excludeRoleAccounts removes the info@ and abuse@ addresses that get senders blocklisted.
• Sharpen a B2B list. excludeFreeProviders drops Gmail and Outlook signups, which tell you nothing about where someone works.
• Catch form typos. Run it on signups and use didYouMean to ask the user rather than losing the account.
• Feed an AI agent. Rows are under 600 bytes and always the same shape, and every verdict carries a plain-language reason a model can quote back.

Input

Field	Default	Notes
emails	13 demo addresses	Plain addresses or pasted Name <a@b.com> form. Deduplicated before charging.
checkMailbox	false	Opens an SMTP conversation and asks whether the mailbox exists. Honest about whether it worked.
onlyDeliverable	false	Drops undeliverable rows before charging.
excludeRoleAccounts	false	Drops info@, sales@, support@ and ~40 others.
excludeFreeProviders	false	Drops Gmail, Yahoo, Outlook and similar.
concurrency	10	Parallel lookups. DNS resolvers start refusing above about thirty.

How the verdict is reached

status	means
deliverable	The mail server accepted the address. Only reachable with checkMailbox on and port 25 open.
risky	The domain exists and accepts mail; this mailbox is unproven.
undeliverable	Bad syntax, dead domain, no MX record, disposable provider, or the server rejected it.

confidence is a 0–100 companion to status, so you can set your own threshold rather than trusting ours.

Limits worth knowing before you buy

Without checkMailbox, nothing can be deliverable — that is the design, not a gap. With it on, the result depends on whether the run's host can reach port 25 and whether the receiving server answers honestly; many large providers greylist or accept everything, and a server that accepts everything is reported as unproven rather than as a pass.

The disposable-domain list is a dated snapshot, recorded in every run's summary. New throwaway providers appear constantly and no list is ever complete.

This checks whether an address can receive mail. It does not tell you whether the person still works there, and it is not a substitute for permission to contact them.

Pricing

Pay per address returned, after filtering. Nothing is charged for duplicates or for rows your filters removed.

Disclaimer

This Actor performs standard DNS lookups and, when asked, a standard SMTP conversation — both public internet protocols, used exactly as specified. It scrapes no website, calls no third-party API, and stores no address after the run. There is no robots.txt to respect because no website is involved.

The disposable-domain list is derived from the public disposable-email-domains project, released under CC0 1.0 (public domain).

Verifying an address tells you it can receive mail. It says nothing about whether you are permitted to contact the person behind it — that is your responsibility under GDPR, CAN-SPAM and the equivalent rules in your market.