Glossary · Emails and phones
What is email verification?
The short answer
Email verification is the check that an email address exists and can receive mail, done before anything is sent: the syntax first, then the domain and its MX records, then a short exchange with the receiving mail server that asks whether it would accept the address. It cannot settle every case: a catch-all domain says yes to any address.
Real data
The domain step on three real domains, and what the API promises
The mail servers returned with verified work addresses at gong.io, hubspot.com and stripe.com on November 10, 2026, the second step of any verification. Then what the BlitzAPI documentation says about the addresses it returns, read the same day.
Returned by the BlitzAPI API on
From the BlitzAPI API reference, Find Work Email, read on
/v2/enrichment/emailMX records returned with the verified addresses
- gong.io
- 2 hosts at Proofpoint, both priority 10
- hubspot.com
- 1 host at Google, priority 1
- stripe.com
- 5 hosts at Google, priority 10 to 30
A verifier talks to the host with the lowest priority number first. At gong.io that host is a security gateway, which receives the mail before the mailbox does.
What the documentation says
- Find Work Email returns
- A verified address, or found: false
- Records counted when no address is found
- None
- Verified addresses re-tested
- At least once every 30 days
- An endpoint that checks an address you send
- None
The re-test interval comes from the Data Quality page of the documentation; the last row comes from the API reference, whose endpoints take a profile, a company, a domain, a phone number, an email address (Reverse Email Lookup, which returns the person) or a search, and none returns a verdict on whether an address can receive mail.
How does email verification work?
Email verification works by asking, one step at a time, whether an address could receive mail, without ever sending a message. Each step can stop the check; only the last one talks to the mail server.
- Step 1SyntaxOne @, a real domain ending, allowed characters
- Step 2Domain and MXThe domain exists and accepts mail, through its MX records or its own address
- Step 3Server checkThe server is asked whether it takes mail for the address
- Step 4VerdictValid, invalid, or unknown when the server cannot tell
The server check follows the start of a normal SMTP delivery. The verifier connects to the host listed in the domain’s MX record, introduces itself, names a sender, then names the address to test in a RCPT TO command. A 250 reply means the server accepts that recipient. A 550 reply with the enhanced code 5.1.1, defined in RFC 3463, means the mailbox does not exist, while a 550 with a 5.7 code is a policy refusal that says nothing about the mailbox. The verifier then disconnects, so nothing is delivered.
What do email verification results mean?
Email verification results come in a few standard labels, and each one says how far the check got. Tools name them differently, but the logic is the same:
| Result | What happened | What to do |
|---|---|---|
| Valid | The server accepted the address, and it refuses addresses it does not know | Send |
| Invalid | Bad syntax, a domain that accepts no mail, or a permanent refusal of the mailbox | Remove it |
| Catch-all | The server accepts every address at the domain, real or not | Find other evidence before sending |
| Unknown | No clear answer: a timeout, a temporary refusal, a blocked check | Check again later, or find other evidence |
Which is which?
Five answers a verifier can get. Which mean the address can receive mail, which mean it cannot, and which prove nothing yet?
250 OK to RCPT TO, on an ordinary domain
The server accepted the recipient, and it would have refused a mailbox it does not know. Strong evidence at this stage, not a delivery receipt.
550 5.1.1, user unknown
A permanent failure: there is no mailbox by that name at the domain.
250 OK to RCPT TO, on a catch-all domain
The server accepts every address, real or not, so its yes carries no information. Verifiers label this result catch-all.
451 4.7.1, try again later
A temporary refusal, often greylisting: the server wants the sender to come back later and has said nothing yet about the mailbox.
maya.chen@@acme.com
Two @ signs: the address fails the syntax check before any server is asked.
Show the answers
- 250 OK to RCPT TO, on an ordinary domainDeliverableThe server accepted the recipient, and it would have refused a mailbox it does not know. Strong evidence at this stage, not a delivery receipt.
- 550 5.1.1, user unknownUndeliverableA permanent failure: there is no mailbox by that name at the domain.
- 250 OK to RCPT TO, on a catch-all domainNot provenThe server accepts every address, real or not, so its yes carries no information. Verifiers label this result catch-all.
- 451 4.7.1, try again laterNot provenA temporary refusal, often greylisting: the server wants the sender to come back later and has said nothing yet about the mailbox.
- maya.chen@@acme.comUndeliverableTwo @ signs: the address fails the syntax check before any server is asked.
Why can’t email verification confirm every address?
Email verification cannot confirm every address because the last step depends on what the mail server is willing to say. A catch-all domain accepts every recipient, so a real mailbox and a made-up one get the same answer. Some servers answer a first check with a temporary refusal, a technique called greylisting, and some limit or block a sender that asks too many questions.
Time is the other limit. An address that passes today can fail next month, when the person leaves and the employer closes the mailbox, which is why a list goes through verification again before each campaign rather than once.
Is email verification the same as email validation?
Email verification and email validation usually mean the same check, and many tools use the two words interchangeably. Where a difference is made, validation means the checks that need no server, the syntax and sometimes the domain, and verification adds the conversation with the mail server.
Both happen before sending. An email bounce is what happens after, when an address that was never checked, or checked too long ago, turns out not to work.
Can BlitzAPI verify an email address?
BlitzAPI cannot verify an email address you already have: none of its endpoints takes an address and returns a verdict on whether it can receive mail. To clean a list you already own, use a dedicated verification service.
What BlitzAPI does is the other half of the problem. Find Work Email takes a LinkedIn profile URL and returns an address only when it is verified, with the MX records of its domain, or found: false with no record counted; the documentation says verified addresses are re-tested at least once every 30 days. Reverse Email Lookup takes an address and returns the person it belongs to, not whether its mailbox accepts mail today.
Sources and method
- Written by
- Antoine Blitz, Founder, BlitzAPI
- Published
- API calls run on
- BlitzAPI API reference, Find Work Email
- BlitzAPI guide, Data Quality (the re-test interval)
- RFC 5321, Simple Mail Transfer Protocol
- RFC 3463, Enhanced Mail System Status Codes
The MX records come from the Find Work Email calls of November 10, 2026 behind the company email format page, run through the BlitzAPI MCP server; no address or name is shown here, and the profile URL in the request is a placeholder.
The SMTP replies in the sorting exercise are standard codes from RFC 5321 and RFC 3463, shown as examples rather than measurements.