How to Verify an Email Address and Check If It's Valid
Need to check if a mail ID is valid before you hit send, or check valid email addresses across a whole customer list? The obvious way is to send something and see if it bounces. The trouble is that bounces can hurt your sender reputation, and on a big list they add up fast. Some email platforms even review accounts whose bounce rate gets too high.
The better way is to verify addresses before you send. It happens in layers. Steps 1 to 3 below are free ways to verify an email address yourself (format, typos, whether the domain has mail servers). Step 4 asks the mail server directly whether the mailbox exists, still without delivering a single message. Here's what each layer can and can't tell you.
What "valid" really means
An address can pass or fail at three different levels:
- It's written correctly. It follows the rules for how an email address is put together.
- Its domain can receive email. The part after the @ exists and has mail servers.
- The mailbox exists. The mail server recognizes that particular person.
On top of that, some addresses are real but risky to send to, such as throwaway inboxes or catch-all servers. We'll cover those too.
Step 1: Check the format
The official rules for email addresses (a standard called RFC 5322) say an address is a name part, then @, then a domain. The name part can use letters, digits, dots and a set of symbols such as + and _. In normal use it can't start or end with a dot, can't have two dots in a row, and can't contain spaces.
There are size limits too. The mail-sending standard (RFC 5321) sets a maximum of 64 characters for the part before the @ and 255 for the domain.
Format checks catch the obvious junk: a missing @, a space in the middle, john..smith@, or no domain at all. But a perfectly formatted address like nobody123@example.com can still be fake, so this is only the first filter.
A note on capitals: the domain part isn't case-sensitive. The standard says mail servers must treat the part before the @ as case-sensitive, but also discourages relying on that. Most providers ignore capitals in practice, but it's safest to keep addresses exactly as people typed them.
Step 2: Catch typos in the domain
Many bad addresses are real people who slipped on the keyboard: gmial.com, yahoo.con, hotmial.com. These are well formatted, so a format check passes them, but mail will never arrive. Comparing domains against common providers catches many of these, and you can often fix them rather than delete them. It's worth a quick look down your list before anything else.
Step 3: Check that the domain can receive mail
Every domain that accepts email points to its mail servers with DNS records called MX records (mail exchanger). You can look these up for free with any online "MX lookup" tool, and they tell you a lot:
- The domain doesn't exist. Every address at it is undeliverable. This often turns up on old business lists, where companies have closed or changed names.
- No MX records. The standard lets mail fall back to the domain's main address, so this isn't automatically fatal, but it's a warning sign.
- A "null MX" record. A domain can publish a special record (defined in RFC 7505) that announces it accepts no email at all. Addresses there are dead.
It's also worth checking whether the domain is parked, expired or brand new, since those often belong to addresses nobody reads.
Step 4: Ask the mail server about the mailbox
This is the step that answers "does this person's inbox exist?" without sending an email. Mail servers talk to each other in a simple back-and-forth, a bit like a phone call. A checker calls the domain's mail server, says who the mail would be from, then names the recipient. The server answers, and the checker hangs up before any message is sent. You can't easily do this by hand, which is why people use an email checker for this step.
The server answers with a three-digit code, set out in RFC 5321:
- A 2xx reply means the server accepted the recipient.
- A 5xx reply is a permanent failure. Code 550 means "mailbox unavailable," for example mailbox not found.
- A 4xx reply is temporary: try again later. The answer is unknown for now.
You may read about an old "VRFY" (verify) command that's meant to do this. The standard lets servers switch it off, and a server that can't check an address on the spot is supposed to give a noncommittal answer (code 252) rather than confirm it. So naming the recipient, as above, is the more useful test.
Where mailbox checks hit their limits
- Catch-all servers accept every address at the domain, real or not, so the mailbox can't be confirmed either way. See what a catch-all email is.
- Temporary answers. Some servers reply "try later" (4xx) to unfamiliar connections, which leaves the result unknown.
- Things change. A mailbox that exists today can be closed next month.
Step 5: Flag addresses that are real but risky
An address can pass every check above and still be a poor choice to send to:
- Disposable addresses from throwaway services, which often stop working after a short time. Read what a disposable email address is.
- Role addresses like info@ or sales@, which belong to a department rather than a person.
- Fake-looking addresses like test@test.com or random strings of letters.
- Duplicates, which mean the same person hears from you twice.
Check a list from $1.49
What no checker can promise
A valid address means the mailbox exists right now. It doesn't mean your email will reach the inbox, and it can't predict that someone will close their account next week. After every send, remove any address that hard-bounces. Mailchimp's help center describes a hard bounce as "a permanent reason an email can't be delivered," such as an address that doesn't exist. For a full routine, see how to clean an email list.
Frequently asked questions
How do I check if an email address is valid without sending an email?
Use a checker that asks the recipient's mail server whether it accepts the address, then disconnects before any message is sent. This works for most addresses, but catch-all servers and servers that only give temporary answers can't be confirmed this way.
If an address passes a format check, is it real?
Not necessarily. A format check only confirms the address is written correctly. The domain may not exist, or the mailbox may not be there, so you need domain and mailbox checks as well.
Why do some results come back as Unknown?
Some mail servers answer with a temporary 'try again later' reply or won't give a clear answer about a mailbox. When the server doesn't say yes or no, the honest result is unknown.
Can I verify an email address for free?
Partly. You can check the format yourself (one @, no spaces, no double dots), look for typos in the domain such as gmial.com, and use a free DNS lookup tool to see whether the domain has mail servers (MX records). Confirming that the mailbox itself exists needs a mail server check, which is what paid checkers do.