Email Bounce Rates: Hard vs Soft Bounces Explained

Email bounce rates measure the percentage of messages that fail to reach recipients. Hard bounces are permanent failures from invalid addresses; soft bounces are temporary, and cover full mailboxes, oversized messages, and servers that happen to be offline. Under 2% is healthy. Above 5% and you are actively damaging your sender reputation at Gmail, Yahoo, and Microsoft.

Most senders don't discover the problem while it's still a bounce problem. They discover it a quarter later, when opens have quietly slid and nobody can say why.

What is an email bounce rate?

An email bounce rate is the share of sent messages that never reached a recipient inbox, expressed as a percentage. The receiving server rejected the message and returned an SMTP error; your sending platform logs that as a bounce instead of a delivery. Both permanent and temporary rejections count.

Bounces are separate from spam folder placement. A message that lands in spam counts as delivered; a message refused at the SMTP handshake counts as bounced. The distinction matters because tools like Gmail Postmaster report them in different panels, and each has a different fix.

The formula is uncomplicated: bounced emails ÷ total emails sent × 100. Send 10,000 and lose 180, and you're at 1.8%. The bounce rate calculator will run it, and the delivery rate calculator shows the same event from the other side.

Two gotchas hide inside it. Some platforms divide by delivered messages rather than sent, which flatters the number. And the aggregate buries the signal: a 2% overall rate could be 0.5% on your main list and 12% on a recently purchased one, and mailbox providers judge you on the bad list. Track bounces by source, signup date, and segment, because that's where the cause lives.

Hard bounces vs soft bounces

A hard bounce is a permanent failure: the address doesn't exist, the domain is invalid, or the recipient server has blocklisted your domain. A soft bounce is temporary: the mailbox is full, the message exceeds a size limit, the server is offline, or greylisting is in effect. Suppress hard bounces immediately; retry soft bounces.

RFC 3463 defines the enhanced status codes that separate the two. A 5.x.x code is permanent; a 4.x.x code is temporary. 5.1.1 means "bad destination mailbox address" (hard), while 4.2.2 means "mailbox full" (soft). Any competent platform maps these to bounce categories for you.

The complication is that Gmail, Yahoo, and Microsoft don't always return clean codes, so every serious sending platform layers provider-specific parsing on top of RFC 3463. A 550 from Gmail with reputation language in the response body is a block, not a bad address, and treating it as one will have you deleting perfectly good subscribers.

Where hard bounces come from

Three places, mostly. Invalid addresses, nonexistent domains, and blocklisting.

An address goes invalid when someone leaves a company, deletes an account, or mistypes at signup; gmial.com, yaho.com, and hotmai.com show up in nearly every list I've audited. The mailbox simply isn't there anymore, and no amount of retrying will conjure it.

Domain-level failures are the worse category, because they say something about how the list was built. If a chunk of your addresses have MX records that don't resolve, those addresses were probably bought or scraped, and Google Postmaster will spot the pattern before you do. Blocklisting is the one senders dread: while Spamhaus, SpamCop, or a recipient's internal list has your domain or IP flagged, every message to that recipient becomes a hard bounce until you're delisted.

One practical warning. Some providers dress up a hard rejection as a soft one. Yahoo's 421 4.7.0 frequently means "we don't like your reputation today" rather than "try again in a minute." If the same address soft-bounces three times running, treat it as hard and suppress it.

Where soft bounces come from

Full mailboxes lead by a wide margin. Abandoned personal accounts fill with newsletters and notification mail until they hit quota; Gmail and Outlook absorb this silently, while smaller providers and self-hosted servers bounce the message back at you.

Greylisting is a deliberate anti-spam technique rather than a failure. The recipient server returns a temporary error on first contact, on the theory that legitimate senders retry and spam tools usually don't. Well-behaved infrastructure waits and tries again, so you rarely see greylist bounces in a final count unless the retries also failed.

Size limits bite B2B senders who attach PDFs. Most corporate servers cap inbound around 25MB, Gmail at 25MB, Outlook.com at 20MB. A 23MB proposal bounces at Outlook and delivers at Gmail from the same send, which is a confusing morning if you don't know to look.

What a good bounce rate looks like

Under 2% is healthy. Between 2% and 5% is a yellow flag worth an afternoon of investigation. Over 5% will degrade your inbox placement within weeks, and by then the fix takes months rather than days.

Universal averages are close to useless here, though. Nonprofits run higher because donor lists age; ecommerce runs lower because addresses arrive fresh from checkout. Check the industry benchmarks for your category, then judge yourself against your own trend line. The direction of travel is what matters: a stable 2.4% on a list you understand beats 0.9% drifting upward for reasons nobody has looked into.

How to reduce your bounce rate

Start with list hygiene. Remove every hard bounce automatically after the first failure and soft bounces after three or four consecutive fails. Most platforms do this by default; some legacy ESPs still require a manual step, so confirm which kind you're on rather than assuming.

Add validation at signup. Real-time verification catches typos and role addresses (info@, admin@, noreply@) before they enter the list, and double opt-in proves a real mailbox exists by making the subscriber click. Our email list hygiene guide covers the suppression rules in detail.

Warm up new sending domains and IPs before you scale. A cold domain sending 50,000 messages on day one collects bounces from providers that have never seen it; a warmed domain that ramped over two weeks doesn't.

Clean on a schedule. Every six months, run re-engagement against your inactive segment and suppress anyone who doesn't open or click after two more sends. Emailing fewer people to sell more feels wrong until you watch it work. Run those sends through the spam checker first, because content filters are noticeably stricter on low-engagement segments.

Finally, monitor by segment rather than by campaign. If one acquisition source produces bounce rates above 3%, quarantine it and investigate before it drags sender reputation down for everyone else; the email deliverability guide covers the monitoring side end to end.

Sudden spikes and spam-filter rejections

Why did my bounce rate suddenly jump?

Three usual suspects: a new acquisition source polluted the list, a sending domain landed on a blocklist, or authentication broke after a DNS change. Check your bounce logs for a pattern in the recipient domain or the error code; the email headers guide walks through reading the diagnostic codes returned in bounce messages.

Can spam filter rejections look like bounces?

Sometimes. A server that drops a message at SMTP for spam reasons returns a bounce-like response, often a 550 with reputation language in the body. Platforms that classify bounces properly flag these as "block" or "reputation" bounces rather than invalid-address bounces, and the fix is deliverability work rather than list pruning. Our how to avoid the spam folder guide covers the content and authentication side.