Email verification and bounce rate: Why it matters

A big list full of invalid addresses is not an asset. It is a liability with a delay on it.

How addresses get found

Most B2B addresses come from a small number of routes: pattern inference from a name and company domain, published contacts on company websites, and matching a person to a role via LinkedIn. Only one of those produces a confirmed address, and it is not the first.

Guessed is not verified

Tools commonly infer firstname.lastname@company.com and present it with confidence. Some of those are simply wrong. Sending to them produces bounces, and bounces are the most expensive kind of mistake in cold email.

Why bounce rate carries so much weight

A high bounce rate is one of the clearest signals a mailbox provider has that a sender is not careful. The consequences do not stay local to that campaign:

• Messages start landing in spam rather than the inbox.
• The reputation of the whole domain suffers.
• Good copy stops rescuing you, because it is not being seen.

One bad list undoes weeks of work

This is the part teams underestimate. You can warm a domain patiently for a month and undo it with one unverified import. Verification is cheap insurance on an asset that took real time to build.

What email verification checks, in order

A verification tool runs an address through a sequence of increasingly expensive checks:

1. Syntax. Is the address even shaped like an address? Typos and stray spaces fail here.
2. Domain and MX records. Does the domain exist and does it publish mail servers? A company that folded last year fails at this step.
3. SMTP handshake. The tool opens a conversation with the receiving server and asks whether the mailbox exists, without sending anything. This is the check that separates guessed addresses from real ones.
4. Risk flags. Role accounts (info@, office@), disposable addresses and catch-all domains get marked, because each carries its own problem even when technically valid.

The output is typically three buckets: valid, invalid, and risky or unknown. The first goes in the campaign, the second in the bin. The third is where judgment comes in.

What bounce rate is acceptable

Rather than aim at a published threshold, treat bounce rate the way we do in practice: a properly verified list bounces so rarely that any visible bounce rate is news. Set your own alarm line low, write it down before the campaign starts, and pause sending the moment a campaign crosses it rather than finishing the batch and cleaning up afterwards. Verification is what makes that possible, because it removes the invalid addresses that cause hard bounces in the first place.

Distinguish the two bounce types. A hard bounce means the address does not exist; the contact is dead and must never be mailed again. A soft bounce means a temporary condition, a full mailbox or a greylisting server, and one retry later is fine. It is the hard bounces that mailbox providers hold against you, which is why they feed directly into sender reputation.

Catch-all domains: the honest grey zone

Some company servers accept mail for any address at their domain, valid or not. Verification cannot give a confident answer there, so tools mark these contacts as "accept-all" or "unknown". The pragmatic handling: send to catch-alls in small numbers, mixed into campaigns dominated by verified-valid addresses, and watch the bounce reports. If a catch-all domain bounces once, suppress every contact at that domain. Excluding catch-alls entirely is safer but discards a real share of many B2B markets, especially smaller European firms whose IT setup defaults to accept-all.

Verification decays, so repeat it

A list verified in January is not verified in June. People change jobs, companies rename, mailboxes get closed, and B2B contact data ages at a pace most teams underestimate; a meaningful share of any list stops being valid within a year. The rule that follows: verify at the point of sending, not at the point of buying. A list older than about three months gets re-verified before any campaign touches it. The wider upkeep routine is covered in list decay and maintenance, and where European contact data comes from in the first place is covered in where European B2B data comes from.

Common verification mistakes

• Trusting the sourcing tool's own "verified" label. Fix: run an independent verification pass; the vendor grading its own homework is not a control.
• Verifying once, then mailing for six months. Fix: re-verify anything older than a quarter.
• Deleting soft bounces. Fix: retry them once later; only hard bounces are dead.
• Mailing the "unknown" bucket at full volume. Fix: trickle catch-alls in small batches and monitor, keeping daily volume within safe limits as covered in how many emails per day is safe.
• Ignoring bounces mid-campaign. Fix: check bounce rate after the first sending day of any new list; catching a bad import on day one saves the domain.

The European wrinkle

Verification habits matter more in Europe than in the US for two reasons. First, address patterns are less uniform: German firms mix first.last@ with surname-only formats, Baltic and Polish companies often use national domains and localised spellings, and pattern-guessing tools trained on American data miss more often. Second, a bounce to a dead address is still an attempted contact for compliance purposes, and sloppy lists undermine the accuracy duty that GDPR places on anyone processing business contact data. Clean lists are both a deliverability practice and part of operating legitimately in the region, and that duty is tightest in the strictest market, as the guide to cold email law in Germany explains.

It is part of the system, not a step

Verification belongs with authentication, warm-up and volume control. They all protect the same thing: that the message actually arrives. Doing three of the four is not enough.