Home / Blog / What is a good email bounce rate?

What is a good email bounce rate? (and how to lower yours)

By Andrej Užušienis · July 2, 2026 · 7 min read

Bounce rate is the single most-watched deliverability metric, and also the most misunderstood. Marketers quote it constantly, but few can say what number is actually safe, how the mailbox providers calculate it on their side, or why a "clean" list still bounces. This guide fixes that: what a good bounce rate really is, how to measure it correctly, and the specific mechanics of how verifying addresses before you send drives it down.

What counts as a bounce

A bounce is any message your sending platform could not deliver to the recipient's mailbox. The receiving mail server rejected it — either permanently or temporarily — and returned a status code explaining why. Every bounce is logged against your sending domain and IP, and the major inbox providers (Gmail, Microsoft, Yahoo) keep score.

There are two families of bounce, and they are not equal. A hard bounce is a permanent rejection: the address does not exist, the domain has no mail server, or the recipient blocked you outright. A soft bounce is a temporary failure: the mailbox is full, the server is down, or the message was greylisted. The distinction matters enough that it deserves its own article — see hard vs soft bounces for the full breakdown. For bounce-rate purposes, hard bounces are the ones that hurt your reputation.

How to calculate bounce rate correctly

The formula is simple, but people apply it to the wrong denominator. Bounce rate is:

Bounce rate = (bounced messages ÷ messages sent) × 100

The mistake is calculating against delivered messages instead of sent messages. If you sent 10,000 emails and 300 bounced, your bounce rate is 3% (300 ÷ 10,000), not 3.09% (300 ÷ 9,700). Providers judge you on the sent figure, so measure it that way. If you want a cleaner picture of engagement, track your hard-bounce rate separately — it is the number that actually predicts trouble.

What is a good bounce rate?

Context matters, but these thresholds hold across almost every ESP and industry benchmark:

Bounce rateVerdictWhat it means
Under 1%ExcellentWell-maintained list or verified at capture. This is the target for cold outreach.
1% – 2%AcceptableNormal for an engaged marketing list. Keep an eye on the trend.
2% – 5%WarningProviders start throttling. Investigate list source and hygiene now.
5% – 10%DangerDeliverability actively degrading; risk of being flagged as a spammer.
Over 10%CriticalLikely to get the sending domain blocked. Stop and clean before sending again.

Gmail and Microsoft do not publish exact cutoffs, but the operating reality is: a cold-outreach campaign that bounces above 2% will start seeing rate limiting, and above 5% you are one campaign away from a burned sending domain. An established, permission-based newsletter can tolerate slightly more because the providers trust the sender history — but you never want to test that trust.

Why lists bounce even when they look clean

Email addresses decay. Roughly 20–30% of a B2B list goes stale every year: people change jobs, companies fold, mailboxes get deactivated. An address that was valid when you captured it eighteen months ago may hard-bounce today. This is why bounce rate is not a one-time problem — it is a maintenance problem.

The other common source is capture-time errors. Typos (gmial.com), fake signups, and honeypot addresses all enter a list looking perfectly plausible and only reveal themselves when you send. A list can look clean to the human eye and still be 4% dead weight.

How verification reduces bounce rate

Email verification pre-checks each address against the same signals the receiving server will use, before you ever hit send. A good verifier runs five layers: RFC 5322 syntax, an MX record lookup to confirm the domain accepts mail, disposable-provider detection, role-account filtering, and a live SMTP RCPT probe that asks the real mail server whether the mailbox exists — without delivering a message. If you want the deep protocol walkthrough, we wrote one on how SMTP RCPT validation works.

Removing the addresses that fail these checks is what moves the number. In practice:

A list that verifies at 96% deliverable will, in the real world, bounce close to that verified figure — often under 1%. The gap between "looks fine" and "verified fine" is exactly the gap between a working sending domain and a throttled one.

Verify your list before you send

Five checks in under 500ms — syntax, MX, disposable, role-account, and live SMTP. Free in your browser, no signup.

Try the verifier →

A practical bounce-rate routine

Keeping bounce rate low is less about one big cleanup and more about rhythm:

  1. Verify at the point of capture. Validating on your signup form stops most bad addresses from ever entering the list. The Mailcheq API is built for exactly this — a single call at form submission.
  2. Re-verify before every large send. Especially for lists that have been sitting. Addresses that were valid last quarter may not be now.
  3. Segment by engagement. Suppress addresses that have not opened or clicked in 6–12 months; they are the most likely to have gone stale or turned into spam traps.
  4. Watch the trend, not just the number. A bounce rate creeping from 0.8% to 1.6% over three campaigns is a signal to clean, even though 1.6% is still "acceptable."
  5. Authenticate your domain. Bounces are not only about bad addresses — misconfigured authentication causes rejections too. Check your SPF and DMARC records so legitimate mail is not bounced on a technicality.

The bottom line

Aim for under 1% on cold outreach and under 2% on engaged marketing lists. Calculate against messages sent, not delivered, and track hard bounces separately because those are the ones that damage your reputation. Verification is the highest-leverage lever you have: it removes the guaranteed bounces before the providers ever see them, which is the difference between a sending domain that keeps working and one that quietly stops reaching the inbox.

Spotted an error in this article? Email hello@mailcheq.com and we will fix it.