Cold Email Bounce Rate: What Is Too High?
No mailbox provider publishes a bounce-rate threshold — the widely-quoted 2% is industry convention, not a rule from Google, Microsoft or Yahoo.
No mailbox provider publishes a bounce-rate threshold — the widely-quoted 2% is industry convention, not a rule from Google, Microsoft or Yahoo. What every provider does publish is the instruction to remove invalid addresses promptly. Treat under 2% as normal, 2–3% as a reason to stop and investigate, and above 3% as active damage.
Key takeaways
- No provider publishes a bounce number. Anyone quoting “Gmail’s bounce limit” is quoting a convention, not a source.
- Every provider publishes the direction: monitor bounces, remove invalid recipients promptly.
- The published number is complaints: below 0.3% at Gmail and Yahoo, with Gmail recommending below 0.10%.
- Hard and soft bounces are different actions. A 5xx code is permanent and must never be retried; a 4xx is transient and should be.
- Verification before sending is the only reliable fix. Cleaning up afterwards means the damage has already been done.
What actually counts as a bounce?
A bounce is a rejection from the receiving side, and the first digit of the response tells you which kind it is. RFC 5321 defines a 4yz reply as a transient negative completion — “the message as sent is still valid and… the client SHOULD, in fact, send the message again, possibly after waiting a bit longer” — and a 5yz reply as a permanent negative completion, where the message “is invalid in some way or there is a permanent problem with the server” (RFC 5321).
That distinction matters more than the label your tool prints:
| Hard bounce (5xx) | Soft bounce (4xx) | |
|---|---|---|
| Meaning | Permanent failure | Temporary failure |
| Typical cause | Address does not exist, domain refuses the sender, policy rejection | Mailbox full, recipient-side rate limit, temporary deferral |
| Correct action | Suppress the address permanently | Retry later, on a sensible schedule |
| Counts against list quality | Yes, heavily | Only if it persists |
Yahoo documents the same split for its own systems: “A 421 or 451 SMTP error indicates a temporary problem blocking the delivery of your message,” while “A 553 or 554 SMTP error indicates an email could not be delivered due to a permanent problem” (Yahoo).
Two traps sit in that table. Some 5xx-looking messages are not bounces at all — Gmail returns 550 5.4.5 for “Daily user sending limit exceeded,” which is about your mailbox, not the recipient’s address (Google); suppressing that prospect throws away a good address. And a soft bounce repeated to the same address should eventually be retired rather than retried forever.
At what rate should I pause?
There is no published provider figure, so here is a defensible operating scale with the reasoning attached, not a borrowed statistic:
| Bounce rate | What it usually means | What to do |
|---|---|---|
| Under 1% | A verified, recently-sourced list | Keep sending |
| 1–2% | Normal decay in B2B data — people change jobs | Keep sending, re-verify the older segments |
| 2–3% | The list has a systemic problem: age, a scraped source, guessed address patterns | Stop the campaign and investigate before sending more |
| Above 3% | You are sending to addresses that largely do not exist | Stop, re-verify everything, do not resume on the same list |
The reason to stop rather than push through is what a bounce represents to the receiving side: an attempt to deliver to an address that isn’t there. Providers do not publish a threshold, but they do publish the expectation. Yahoo’s best practices ask senders to “Monitor hard and soft bounces as well as inactive recipients,” to “Remove invalid recipients from your list promptly,” and to “Reduce the number of invalid recipients by using double/confirm opt-in” (Yahoo). Microsoft’s bulk guidance is to “Maintain list hygiene: Remove invalid and bouncing email addresses” (Microsoft).
What does Gmail actually measure?
Complaints, not bounces. Google’s sender guidelines instruct senders to keep the spam rate reported in Postmaster Tools “below 0.3%” and to aim “below 0.10%” so a single bad campaign does not push the rolling rate over the line (Google). Yahoo publishes the same 0.3% figure (Yahoo).
Nowhere in either set of guidelines is there a bounce-rate number. This is why “keep bounces under 2%” should always be presented as what it is — a widely-shared operating convention that tracks well with real outcomes — rather than dressed up as a provider requirement.
There is also a visibility catch. Gmail’s Postmaster Tools “only applies to messages sent to personal Gmail accounts,” and data may be withheld when “the total number of messages for a given day is too low” (Google). Most B2B outreach goes to company domains, so your own send logs are usually a better bounce signal than any provider dashboard.
How fast does a clean-up show up?
Not instantly, and that asymmetry is the point. A bounce rate is a rolling measure of the mail you have already sent, so removing bad addresses stops the damage accumulating but does not erase the last few thousand failed attempts. Recovery is a matter of sending clean volume for a sustained period, at a pace providers describe as healthy — Google’s guidance is to increase volume slowly, and it warns that “immediately doubling previously sent volumes suddenly could result in rate limiting or reputation drops” (Google).
The practical consequence: resuming a paused campaign at full volume the moment a list is cleaned is the second mistake, right after the list. Resume gradually.
How do I stop it happening again?
Verify before sending, not after bouncing. Verification tells you whether an address accepts mail before you spend your domain’s reputation finding out, and it is the only step in this article that prevents the problem instead of measuring it.
A verification result is not simply yes or no. Useful statuses are:
- Valid — the mailbox accepts mail; safe to send.
- Invalid — it does not exist; never send, suppress permanently.
- Risky — deliverable but flagged, for example a role address; send only with a reason.
- Unknown — the receiving side would not give a definitive answer.
- Catch-all — the domain accepts everything, so acceptance proves nothing about that specific mailbox.
Catch-all domains are why a verified address can still bounce: the domain answers yes to everything. Treat catch-all results as lower confidence and, where the deal matters, confirm another way.
How WarmySender handles this
WarmySender puts a campaign into a cooldown when its bounce rate crosses a set threshold, rather than letting it run to the end of a bad list. The point of the guard is to stop early — a campaign that finishes with a high bounce rate has already spent the reputation the guard exists to protect.
Bounce classification is deliberately careful about what it treats as a bad address. A provider rate-limit response that happens to carry a permanent-looking code is classified as a rate limit and retried, not recorded as a bounce that removes a real prospect from your list. And when a bounce is used as evidence to stop sending to a whole recipient domain, that requires corroboration from more than one sender before it takes effect, so a single misconfigured mailbox cannot poison a domain for everyone else.
Verification runs inside the same paced allowance as everything else. Agents — Claude, ChatGPT, Cursor, Codex, OpenClaw and Hermes Agent — can verify addresses and build campaigns in plain language, but no agent sends a message itself and no agent can raise a limit. See the email verifier, why verified emails can still bounce, why a campaign paused for bounces and bounce shield.
Frequently asked questions
Is 5% bounce rate bad for cold email?
Yes. At 5%, one in twenty of your recipients does not exist, which is a statement about your data source rather than a run of bad luck. No provider publishes that number as a limit, but every provider tells you to remove invalid addresses promptly, and a rate that high means you are discovering them by sending.
Do soft bounces hurt my sender reputation?
A single soft bounce is a normal part of mail delivery — a full mailbox or a temporary deferral, which RFC 5321 says should be retried. Repeated soft bounces to the same address over days are different: at that point the address is functionally undeliverable and should be retired rather than retried indefinitely.
Does Gmail publish a maximum bounce rate?
No. Google’s sender guidelines publish a spam-complaint threshold — below 0.3%, ideally below 0.10% — and give no bounce-rate figure at all (Google). Any article quoting “Gmail’s bounce limit” is quoting industry convention.
Why did a verified email still bounce?
Most often because the domain is catch-all: it accepts mail for every address, so verification cannot distinguish a real mailbox from one that does not exist. Other causes are legitimate timing — the person left between verification and send — or a policy rejection aimed at your sending domain rather than at their address.
Should I retry a bounced email?
Only if the code starts with 4. RFC 5321 defines those as transient failures worth retrying after a wait; codes starting with 5 are permanent, and retrying them adds failed delivery attempts without any prospect of success (RFC 5321).