Email verification tests whether an address is properly formed, whether its domain can receive mail, and whether the mailbox appears to exist, without sending a message to it. It reduces bounces and protects sender reputation. It cannot confirm that a person still works there or wants to hear from you.
What it is
Verification is a set of checks run in order, from cheap to expensive. Syntax comes first: the address must be well formed. Then the domain must exist and publish MX records, which are the DNS entries naming the servers that accept its mail. Then the mailbox itself is probed at the SMTP layer, the protocol mail servers use to hand messages to each other, by opening a conversation and stopping before any message is delivered. The output is a status, usually valid, invalid, risky or unknown, and the last two are the interesting ones.
How it works
Most providers verify a list in bulk and return a per address status plus a reason. Disposable domains, role addresses such as info@ or sales@, and accept all domains get flagged separately because each carries a different risk. Verification is a snapshot with a short shelf life: it describes the mailbox at the moment of the check, which is why teams verify immediately before a send rather than at import time and re verify anything that has been sitting for months.
Why it matters for winning clients
Mailbox providers read bounces as a signal about the sender, not about the list. A campaign that bounces heavily damages the deliverability of every message the domain sends afterward, including replies to customers. Verification is the cheapest insurance against that, and it also saves human time: nobody should write a researched first line for a mailbox that was closed last spring.
Example in LeadCanvas
An agency prospecting local businesses builds a list from public listings and finds the ceiling early. Our own July 2026 study of 231,349 deduplicated business listings found 97.0% show a public phone number while 82.7% show a website, and 15.8% show a phone and no site at all. For that 15.8% there is no domain to verify and no address to guess, so the team routes them to a call queue instead of burning verification credits on invented addresses.
Common mistakes
Treating valid as permission: a deliverable address says nothing about consent or interest. Guessing patterns like first.last@ and verifying the guess, which produces confident junk when the company uses a different convention. Verifying once and reusing the result for a year. And deleting every risky result automatically, when many of those are catch all domains where a different sending strategy, not deletion, is the right answer.
Related terms
A catch all domain is the main reason a check returns unknown. Bounce rate is what verification is meant to keep down. Email deliverability is the broader outcome, and data decay explains why a verified list stops being verified. The links below open the tools where lists are built before they are verified.