Email verification checks that an address will actually receive mail before you send to it.
Key points
- Checks usually run in layers: syntax, domain and MX lookup, then an SMTP recipient test as defined in RFC 5321 [1].
- A permanent failure such as status 5.1.1, bad destination mailbox, is the signal verification aims to catch in advance [2].
- Services such as Twilio SendGrid's validation API return a verdict of valid, risky or invalid with a confidence score [3].
- Results are least certain for a Catch-All Email Address domain and for Role-Based Email Address addresses, which are often flagged as risky.
- Verifying before sending keeps Bounce Rate low, which protects Sender Reputation and Inbox Placement [5].
- Callback verification, a related anti-spam technique, uses the same SMTP method to check sender addresses and is widely criticized for creating extra traffic [4].
How verification works
Verification proceeds from cheap checks to expensive ones. First, syntax: does the address follow the local-part at domain format? Second, domain: does the domain exist, and does it have an MX Record or other route for mail? Third, mailbox: the verifier opens an SMTP session with the receiving server and issues a RCPT TO for the address, then ends the session without sending. Under RFC 5321, a 250 reply indicates the server will accept mail for that recipient, while a 550 indicates rejection [1]. Enhanced status codes from RFC 3463, such as 5.1.1 for a bad destination mailbox, give more detail [2]. Additional checks can flag disposable domains, role addresses and known spam traps.
Reading the results
Verification is probabilistic. Some servers accept every recipient, which makes a Catch-All Email Address domain impossible to confirm. Others reject or delay probes, return temporary errors, or rate-limit repeated checks, producing an unknown result. For this reason verification services generally return a category rather than a yes or no; Twilio SendGrid's validation API, for example, labels addresses as valid, risky or invalid and includes a score [3]. A common policy is to send only to valid results, treat risky ones cautiously or in small volume, and drop invalid ones. Wikipedia notes that the similar technique of callback verification has drawbacks, including load on remote servers and unreliable answers [4].
Why it matters for outbound
Mailbox providers watch how often your mail bounces. A high Bounce Rate signals a poorly maintained list and can reduce Inbox Placement for all of your mail, not just the bad addresses. Google's sender guidelines ask senders to keep lists clean and to follow authentication and complaint thresholds, including a spam rate below 0.3% [5]. Because B2B contact data decays steadily as people change jobs, verification should happen close to the time of sending rather than months earlier at import, an issue covered under Data Decay. The same applies to addresses produced by an Email Finder or a Waterfall Enrichment process, since a found address is only a candidate until it is checked. Any hard bounce that still slips through should be added to a Suppression List immediately so you never send to it again.
Related terms
Outreach without the busywork.
PineLead finds new B2B prospects every day, qualifies them against your criteria and writes the first email in your voice. You approve — PineLead sends.
Start free with 100 credits →