Check If an Email Is Valid

How email verification actually works

Every email verifier — free or paid — walks the same ladder. Three rungs. Each one filters out a different kind of bad address.

Rung one: syntax.Is the address even shaped like an email? One @ sign. A legal local part. A domain with a real top-level domain. This catches the obvious junk — missing dots, stray spaces, "jane@gmail" with no .com. It also catches something sneakier: typos. Someone types gmial.com instead of gmail.com and the address looks fine to a human. A verifier spots it instantly. This tool checks dozens of the most common domain misspellings and suggests the fix.

Rung two: the domain.A perfectly formatted address is worthless if the domain can't receive mail. So the next check asks DNS a simple question: does this domain have MX records? MX (mail exchange) records tell the world which servers accept mail for a domain. No MX records, no delivery. Ever. This tool runs that lookup live against Google's public DNS, so a dead domain fails on the spot. The domain layer is also where disposable-address detection happens — throwaway providers like mailinator.com are well known, and any address on one will be abandoned within hours.

Rung three: the mailbox.This is the rung browsers can't climb. To confirm that jane.cooper@ specifically exists at a domain, a verification service opens an SMTP conversation with the mail server and asks — politely, without sending anything — whether it would accept mail for that exact recipient. That requires server infrastructure, careful rate limiting, and handling of catch-all domains that say yes to everything. It's why dedicated verification services exist and why they charge money.

Why invalid emails quietly wreck your deliverability

Here's the part most people learn the hard way. Sending to a bad address doesn't just waste one email. It leaves a mark.

When your message hits a nonexistent mailbox, the receiving server rejects it — a hard bounce. Mailbox providers watch your bounce rate closely, and they treat a high one as a signature of a careless sender or a purchased list. The widely used guardrail is 2%. Drift past it and Gmail and Outlook start filing your mail — all of it, including messages to real, interested people — into spam. Keep drifting and your domain's reputation degrades to the point where recovery takes weeks of careful, low-volume sending. That's the whole economics of verification: removing dead addresses before you send is dramatically cheaper than repairing email deliverability after the damage is done.

Role accounts deserve a special mention. Addresses like info@, admin@, and sales@ are often technically valid — the mailbox exists and accepts mail. But they're shared inboxes read by nobody in particular, and they report spam more readily than personal addresses. For cold outreach, a valid role account is still a risky target. That's why this tool flags them separately instead of just calling them valid.

The honest limits of a browser-based check

This tool climbs the first two rungs of the ladder — and does it well. But you should know exactly what it can't see:

• Mailbox existence.The domain may accept mail while your specific recipient doesn't exist — ex-employees are the classic case. Only an SMTP-level check catches this.
• Catch-all domains. Some domains accept mail for any address, real or not. They pass every DNS check and still bounce nothing until the mail is silently discarded.
• Full mailboxes and blocks.A real mailbox can still reject your mail because it's over quota or because a filter blocks you specifically.

The practical workflow: use this free checker to clean the obvious problems out of any list — typos, dead domains, disposables, role accounts. Then, for high-stakes campaigns, run what survives through a dedicated SMTP verification service before you send. Two minutes of hygiene here saves your sender reputation there.