Guide

What a high bounce rate actually costs you

The real cost isn't the wasted send. It's what a bad batch does to every send after it.

Bounces aren’t just wasted sends. Once a domain’s bounce rate crosses roughly 2–5% — the exact threshold varies by provider and isn’t published precisely by any of them — mailbox providers start treating the whole domain as suspect, not just the addresses that bounced. That’s the mechanism behind a sequence that used to land fine suddenly going to spam: it’s rarely a content problem, it’s a reputation one, and reputation is domain-wide.

Bounce type matters

A hard bounce (the mailbox doesn’t exist) counts against you more than a soft bounce (temporarily unavailable — a full inbox, a server hiccup). A list built from guessed addresses generates hard bounces specifically, since a nonexistent mailbox will always hard-bounce, every time, from every provider you try it with.

The damage outlasts the bad batch

Domain reputation doesn’t reset the day after a bad send — providers weight recent history, so a rough week can suppress deliverability for weeks afterward, well past whatever campaign caused it. A domain still building trust has the least buffer to absorb this; see warming up a new sending domain.

Verification is the cheap side of this trade

Checking an address against the mail server before sending costs a fraction of a cent. Recovering a domain’s reputation after a spam-folder problem costs weeks of reduced deliverability across every campaign, not just the one that caused it. Verifying before you send is insurance against a problem that’s expensive and slow to undo, bought at a price that’s neither.

A simple way to talk about the money

Suppose you send 5,000 messages. 8% hard-bounce. That is 400 user unknown events in a short window.

The wasted sends are the small line. The large line is: Gmail and Outlook now have a recent sample in which a large fraction of your recipients did not exist. The next 5,000 — even if those are clean — ride on that sample.

The calculator exists to put a list size next to a rate so this is visible in a meeting. It is not a prediction of inbox placement.

Where the bad addresses come from

Guessed patterns (jane.doe@ on a company that uses jdoe@).
Stale databases (the person left; the mailbox is gone).
Domain mistakes (company.co vs company.com).
Tools that labelled catch-all as verified — those often don't bounce, which is a different injury.

Mailbox-level verification before send deletes the first three. Honest catch-all flags prevent the fourth from looking like a healthy campaign.

Hard bounce vs complaint vs unsubscribe

They are not interchangeable. Complaints ("this is spam") are worse per event than a hard bounce. Unsubscribes are healthy if they are easy. Do not conflate them in a dashboard screenshot.

A guessed list produces hard bounces. A purchased list of people who never opted in produces complaints. Verify the first problem; do not send the second.

Repair, if you already did the damage

Stop the campaign.
Verify everything remaining. Drop catch-alls from the send.
Pause volume. Authenticate if you skipped that.
Expect weeks, not overnight. A new sibling domain may be cheaper than rehabilitating the apex — with the cost that you start warmup again.

Verifier, warmup, catch-all.

What would a bad batch cost you?

Plug in a list size and a bounce rate. The damage is the sends you cannot make afterwards, not the one bounced message.

Emails sentBounced

4.00%

2–5% is already enough to hurt warmup. Verify the rest of the file before you scale volume.