Free Email Verifier
Enter any email address. We check syntax, domain, MX records, disposable providers and role accounts — and tell you why.
0 of 30 free checks used today (per browser)
How it works
Every check this tool runs happens at the DNS stage: we resolve the domain, look up its MX (mail exchange) records and confirm the domain actually accepts mail. We then layer on registry checks — whether the address sits on a disposable-inbox provider, and whether the local part is a shared role account rather than a person.
You will notice there is no SMTP handshake here — no 'RCPT TO' ping to ask the mail server if the mailbox exists. Public tools that do this get their IPs blocked within days, poison their own results, and sometimes get the queried domain flagged. The DNS stage catches the majority of dead addresses (typo domains, expired companies, no-mail domains) without any of those downsides.
What DNS checks cannot see is whether one specific mailbox exists on a server that accepts everything. That is the catch-all problem below, and it is why 'valid' here means 'deliverable domain, clean syntax, not disposable or role' — not 'a human reads this inbox'.
The math
- Syntax
local@domain — RFC 5322 shapeCatches malformed addresses, double @, illegal characters and structural typos before anything else runs.- Domain exists
A / AAAA resolutionNXDOMAIN means the domain is gone — the company shut down or the address was typed with a typo (gmial.com).- MX records
MX lookup · null MX (RFC 7505)No MX means the domain cannot receive mail. A null MX (priority 0, target '.') is an explicit 'this domain accepts no email'.- Disposable check
domain ∉ disposable registry10-minute-mail providers are flagged as risky — they deliver today and are dead tomorrow.- Role check
local ∉ {info, support, sales, admin, contact, …}Role prefixes mark shared inboxes, not a person — they rarely bounce but rarely convert either.
Benchmarks and honest caveats
| Valid | deliverable domain, clean syntax | Not a guarantee a human reads the inbox — see catch-all below. |
|---|---|---|
| Catch-all domains | accept all addresses | Roughly half of what looks 'invalid' on a catch-all domain actually bounces — we flag these as inconclusive rather than guess. |
| Role accounts | low bounce, low conversion | Legal/compliance risk is higher than the bounce risk on info@-style addresses. |
| Disposable | near-certain inactivity | Never worth a send slot. |
Common mistakes
- Verifying once and never again. People change jobs, companies shut down and domains expire — a list verified six months ago decays measurably every month.
- Trusting catch-all domains as valid. A server that accepts everything makes every guess look real; treat those results as unknown, not valid.
- Emailing role accounts at scale. They hurt engagement metrics (opens, replies) and can trigger spam complaints from shared-monitoring inboxes.
FAQ
Why doesn't this tool do an SMTP check?
The SMTP 'RCPT TO' probe is the old-school way to ask a mail server if a specific mailbox exists. We deliberately skip it on a public tool: mail servers rate-limit and blocklist IPs that probe them, results become unreliable, and the probed domain can end up flagging you. Reachfold verifies inside its own verified infrastructure with warmed, rotated sources when a campaign needs mailbox-level certainty.
What is a catch-all (accept-all) domain?
A mail server configured to accept mail for every possible address at its domain, valid or not — companies do this so typos still arrive. It means the server cannot tell you whether jane@ exists. We surface this honestly as inconclusive rather than reporting a confident 'valid' that would bounce.
How fresh are the disposable-domain lists?
The registry is updated continuously — new temporary-mail providers appear daily and get added as they are discovered. A brand-new disposable provider can take a short while to be catalogued, which is one more reason engagement data (opens, replies) should inform your decisions too.
Can I verify a whole list here?
Not in this free tool — it is one address at a time, with a per-browser daily limit. Uploading a list for bulk verification (with catch-all handling, deduplication and role filtering) is part of Reachfold's lead finding and list hygiene.
Keep reading: Bounce rates explained · Email verification tools compared
Keep Reading
Stop verifying addresses one at a time
Reachfold is AI-native, deliverability-first outbound: multi-channel sequences across email and LinkedIn, an agent that asks before it acts, and a measured inbox rate gating every campaign.