What is email verification?

Email verification is the process of checking whether an email address exists and can receive mail before you send to it, usually by validating syntax and domain records and then probing the recipient’s mail server without delivering a message. Its job is to remove addresses that would bounce or put your sender reputation at risk.

TL;DR

Typical results: valid, invalid, catch-all (accept-all), unknown, and risky (role-based, disposable).
Removes most hard bounces, but cannot detect every spam trap or predict every catch-all outcome.
Run it at the last moment before an address enters a sequence, not only at import.
Different from enrichment: enrichment finds an address; verification checks it.

Why it matters for a B2B pipeline

Every hard bounce tells mailbox providers you are mailing addresses you did not get from their owners. Enough of them and your domain reputation drops, which hurts placement for your good prospects too. Verification is the cheapest protection in outbound: it costs a fraction of a cent to a few cents per address, while a burned sending domain costs weeks of capacity. It also keeps reporting honest, because campaigns are not diluted by contacts who never received the email.

Example

A list of 5,000 found emails is verified before loading:

3,950 valid: send.
600 catch-all: send in a small, separate batch from a dedicated pool, and stop if bounces rise.
300 invalid: drop and suppress.
150 unknown (server did not answer): re-verify later or drop.

Without this step, the 300 invalid addresses alone would mean a 6% bounce rate on the first send.

How to do it well

Verify immediately before sending, and re-verify anything older than about 90 days because of data decay.
Treat catch-all as its own segment, not as valid.
Know your verifier’s blind spots. Some mail servers (several consumer providers and many corporate gateways) refuse or fake verification probes, so results for those domains are unreliable. If a domain returns only “invalid” or only “unknown”, treat it as unverifiable rather than dead.
Use a second verifier as a tiebreaker on disputed or high-value addresses.
Suppress invalids globally so they cannot be re-imported.
Track bounces by verifier and by data source to find which one is wrong.

Tool categories: standalone verifiers (ZeroBounce, NeverBounce, MillionVerifier and similar), verification built into finders and waterfall enrichment tools, and sequencer-side checks.

Common mistakes

Verifying once at import and sending months later.
Treating catch-all as valid.
Trusting one verifier blindly, including on domains it cannot probe.
Assuming verification makes a purchased list safe from spam traps.

Email verification