MailSure
← All posts
Basics· 2 min read

Email validation vs email verification: is there a difference?

The two terms are used interchangeably, but there is a useful distinction. Here is how to think about it and which one you actually need.

Photo by borevina on Pixabay

You will see "email validation" and "email verification" used as if they mean the same thing. Most vendors, including us, use them loosely. But there is a useful distinction hiding underneath.

Validation: is it well formed?

Validation asks whether an address could be an email address. It is a check on the text itself:

This needs no network access and runs in microseconds. It is what a regex in your signup form does, with the limits we cover in why regex isn't enough.

Verification: does it actually work?

Verification asks whether the address does receive mail. That means going out to the network:

nobody-here-at-all@gmail.com is perfectly valid and almost certainly unverifiable.

Why the distinction matters

If you only validate, you stop obvious typos but let through every well-formed fake: asdf@asdf.com, an address on a domain that expired last year, a throwaway inbox. These are the addresses that bounce.

If you verify, you catch those too, at the cost of a network lookup and a little latency.

Which do you need?

Both, in layers:

  1. Validate in the browser so the person gets instant feedback on a missing @.
  2. Verify on the server before you store the address or send to it.

In practice a verification service performs the validation step as well, so you can send everything to one place. When a vendor says "validation", check whether they do the network checks. The test is simple: does someone@this-domain-does-not-exist-12345.com come back as invalid? If so, it is doing real verification.

The short version

Try the difference yourself: paste a made-up address on a real-looking domain into the checker on our home page and see which checks it fails.

Try it yourself

Keep reading