To reduce your email bounce rate, verify every address immediately before you send, remove hard bounces from your list the moment they occur, and authenticate your sending domain with SPF, DKIM, and DMARC. In B2B, most bounce problems trace back to one cause: contact data that was accurate when you collected it and stale by the time you used it.
Bounce rate is the percentage of sent emails that never reach a mailbox. It matters far beyond the individual message, because inbox providers read it as a signal of whether you know who you are emailing. A sender with a clean list looks like a legitimate business. A sender with a dirty one looks like a spammer working from a purchased file — and gets filtered accordingly.
What counts as a good email bounce rate in 2026?
Under 2% is the universal safe zone. Above 5%, inbox providers begin throttling you, and above 8% you risk domain-level blocking.
| Bounce rate | Status | What it means |
|---|---|---|
| Under 2% | Excellent | List quality and verification are working |
| 2–3% | Acceptable | Normal for a well-verified cold list |
| 3–5% | Warning | List quality degrading; deliverability at risk |
| 5–8% | Danger | Messages increasingly filtered to spam |
| 8%+ | Critical | Throttling and domain-level blocks likely |
Hard bounces deserve a tighter target than your overall rate. Aim for under 0.5%. Between 0.5% and 2% is a caution range worth investigating, and sustained hard bounce rates above 2% are grounds for delivery deferral at the major providers.
Well-run B2B campaigns typically land between 0.35% and 0.5% overall. Sectors with fast contact turnover — B2B sales, recruiting, legal — commonly run 0.7% to 1.5% on hard bounces, which is higher than ideal but realistic given how quickly B2B data ages.
How much does your list source change the number?
Enormously. The same message sent to two lists can produce a tenfold difference in bounce rate:
| List source | Typical bounce rate |
|---|---|
| Aged domain + verified list | 1–2% |
| New domain (under 90 days) | 2–3% |
| Platform-sourced and verified | 2–4% |
| Web-scraped, unverified | 8–20% |
| Purchased list | 15–40%+ |
This is why “our copy isn’t working” is so often a misdiagnosis. If you are bouncing at 12%, copy is not your problem. For what a healthy campaign actually looks like once deliverability is fixed, see our breakdown of cold email open rate benchmarks.
What is the difference between a hard bounce and a soft bounce?
A hard bounce is a permanent failure (5xx SMTP code) — the address does not exist or you are blocked. A soft bounce is temporary (4xx SMTP code) — the server is asking you to try again later.
The distinction matters because they demand opposite responses. Hard bounces must be suppressed instantly. Soft bounces should be retried a limited number of times, then suppressed if they persist.
| SMTP code | Type | Meaning | What to do |
|---|---|---|---|
| 550 5.1.1 | Hard | Mailbox does not exist | Suppress immediately |
| 550 5.7.1 | Hard | Blocked by policy or spam filter | Fix authentication or content |
| 550 5.7.515 | Hard | Microsoft authentication failure | Fix SPF/DKIM/DMARC |
| 553 / 554 | Hard | Invalid address or rejected message | Suppress, review content |
| 421 | Soft | Service unavailable, rate limited | Slow your sending |
| 450 / 451 | Soft | Greylisting or temporary failure | Retry on a delay |
| 452 | Soft | Mailbox full or storage exceeded | Retry, then suppress |
550 5.1.1 accounts for the majority of hard bounces in cold outreach. It is the server telling you, unambiguously, that the person you are emailing does not work there anymore.
Why do B2B lists bounce more than consumer lists?
Because B2B email addresses are tied to employment, and employment changes constantly.
Roughly 15–20% of professionals change jobs each year. The moment they do, their work address becomes invalid — often within days, as IT deprovisions the account. Consumer addresses, by contrast, can stay live for a decade.
The commonly cited figure from HubSpot’s database decay research is 2.1% per month, compounding to about 22.5% per year. More recent studies of live B2B databases report considerably faster decay, with email addresses degrading quickest of all field types precisely because they are the field most tightly coupled to a job.
The practical implication is uncomfortable but simple: a list you verified six months ago is not a verified list. It is an old list with a verification timestamp on it. Anything older than 60 days should be re-verified before you send.
What actually causes a high bounce rate?
In order of how often they are the real culprit:
- Stale data. The address was valid when sourced and the person has since moved on.
- Verification at the wrong moment. Lists verified at import rather than immediately before send.
- Catch-all domains treated as valid. Verification tools return “accept-all,” the list treats that as a pass, and a portion of them fail on send.
- Role-based addresses.
info@,sales@,admin@draw disproportionate complaints and rejections. - Authentication failures. Missing or misaligned SPF, DKIM, or DMARC triggers policy rejections that register as hard bounces.
- Volume spikes on a cold domain. A new domain sending thousands of messages on day one gets rate-limited.
- Typos and syntax errors. Free-text form fills and scraped pages generate malformed addresses at a steady clip.
How do you reduce email bounce rate, step by step?
1. Verify immediately before sending, not at import
Verification is perishable. A record checked at the moment of export reflects reality; one checked ninety days ago reflects history. Move verification to the last possible step in your workflow.
2. Segment catch-all addresses instead of trusting or deleting them
Catch-all domains accept mail for any address, valid or not, which neutralises standard SMTP verification. Roughly a quarter of unverified catch-all addresses hard bounce when actually sent.
Do not discard them — many are legitimate enterprise contacts. Put them in a separate campaign, send at low volume from a warmed domain, and measure. If that segment bounces above 5%, drop it.
3. Strip role accounts and disposable domains
Remove info@, support@, admin@, hello@, and known disposable providers before sending. They convert poorly and damage reputation disproportionately.
4. Authenticate your domain properly
Gmail’s sender guidelines require SPF and DKIM plus DMARC for anyone sending 5,000 or more messages a day, along with one-click unsubscribe headers, TLS, valid forward and reverse DNS, and a spam complaint rate below 0.3% — with Google advising you stay under 0.1%. Microsoft applied the same 5,000/day threshold to its consumer domains in May 2025.
Since 2026, failures here are rejected outright rather than filtered. The message does not land in spam; it does not land at all. We cover the full configuration in our guide to Gmail bulk sender requirements.
5. Ramp volume on new domains
Start at 5–10 messages per day. Double roughly every three to four days, but only while engagement metrics hold. Volume without engagement reproduces the exact pattern spam filters are built to catch.
6. Suppress hard bounces automatically and permanently
A hard bounce should never receive a second message. Automate suppression at the platform level rather than relying on manual list cleaning.
7. Monitor the signals that predict trouble
Watch Google Postmaster Tools for domain reputation and spam rate, run seed placement tests, and review bounce categories in your sending logs. One number in isolation will mislead you.
What should you do after a bounce spike?
A single campaign at a 15% bounce rate can suppress your sender reputation for two to four weeks. Speed of response matters more than anything else.
- Stop sending from the affected domain the same day. Treat throttling or a hard bounce spike as a rollback signal, not something to push through.
- Diagnose which metric actually failed. Bounce rate points to list quality; complaint rate points to targeting or content; delivery rate points to infrastructure.
- Re-verify the entire list. Remove everything returning invalid or unknown.
- Pull catch-all addresses out of the affected campaign entirely.
- Fix authentication before restarting. Recovery without SPF/DKIM/DMARC in place does not work.
- Restart at warmup volume — 5–10 per day — and rebuild from there.
Expect two to four weeks to full recovery. Resist the instinct to “warm up” by sending more; providers reward wanted mail, not additional mail.
How does ZenBee keep bounce rates low?
Verification is built into the platform rather than bolted on as a separate step you might forget.
Real-time verification on reveal. When you reveal a contact, the address is checked against multiple live sources at that moment. If it cannot be verified, it is not shown — you will see “Could not find a business email address for this person” rather than a guess.
Bulk export integrity. Exports are filtered to verified addresses only. A typical export notice reads: “Out of the 2 contacts you requested, 1 was successfully exported, 1 skipped.” Unverified records never reach your CSV or CRM.
No separate verification charge, and credits back on hard bounces. Verification is included, and credits are returned for the rare hard bounce, so you are only paying for contactable people.
The upstream effect matters as much as the verification itself: better targeting means fewer wasted sends. See how lookalike company search and sales intelligence narrow a list to accounts worth contacting in the first place, and how a manufacturer applied it in our lead generation case study.
Frequently asked questions
What is a good email bounce rate?
Under 2% overall, and under 0.5% for hard bounces specifically. Well-run B2B campaigns typically achieve 0.35–0.5%.
Is a 5% bounce rate bad?
Yes. At 5% you are in the danger band where messages are increasingly filtered to spam, and you are approaching the threshold where providers throttle or block your domain. Pause and re-verify.
Do soft bounces hurt sender reputation?
Individually, no — they are routine. But a high or rising soft bounce rate usually signals rate limiting or reputation problems that will become hard bounces if ignored.
Should you email catch-all addresses?
Cautiously, and never mixed into your main campaign. Segment them, send at low volume from a warmed domain, and drop the segment if it bounces above 5%.
How often should I clean my B2B list?
Re-verify anything older than 60 days, and re-verify immediately after any bounce spike or deliverability dip. With B2B data decaying at roughly 2% per month, quarterly is the absolute minimum.
Does verification guarantee delivery?
No. Verification confirms the mailbox exists. Delivery also depends on authentication, sender reputation, content, and volume patterns. It removes the single largest cause of failure, not all of them.
Get a list that does not bounce
Bounce rate is a data problem wearing a deliverability costume. Fix the data and the rest of your outreach metrics move with it.
ZenBee verifies every contact in real time, exports only what it can confirm, and returns credits on the rare hard bounce. Book a demo to see it on your own target accounts, or review pricing to get started.
More on outbound in our Cold Email & Deliverability topic hub.