Email validation vs email verification: what each check proves

Email validation checks that an address is written correctly. Email verification goes further and asks the receiving mail server whether the mailbox exists.

The two terms are often used as synonyms, but they describe different depths of checking. Validation looks at the text: is there exactly one @, are the characters allowed, does the domain part look like a domain? It runs in a fraction of a millisecond and needs no network.

Verification checks the address against the real mail infrastructure: does the domain exist, does it publish an MX record, and does its mail server accept this particular mailbox? It catches what validation cannot, such as jane@gmial.com (a typo domain) or a closed mailbox at a real company.

In practice, use validation first, because it is free and instant, and verification for the addresses that pass it.

With Easy Email Verification

Easy Email Verification does both in one call: syntax, domain, MX and mailbox checks, plus risk signals. See how email verification works and the developer guides.

Fields of an API response related to this term:

{
    "email": "jane@gmial.com",
    "result": "invalid",
    "reason": "invalid_domain",
    "did_you_mean": "jane@gmail.com"
}

Check an address for freeClean a whole list