Table of Contents
- What is a cold email bounce rate?
- What counts as a good bounce rate for B2B cold email?
- Why does bounce rate vary so much between providers and setups?
- What causes a cold email bounce rate to spike?
- How do you fix a rising bounce rate?
- Does a high bounce rate always mean bad list quality?
- How does this compare to running outbound in-house versus with a managed provider?
- Key Takeaways
- What this means for your next deliverability check
- Related reading
A sales leader checking campaign health usually looks at responses first and deliverability second, if at all, which is backwards: a rising cold email bounce rate is the earliest signal that an outbound programme is about to lose its sending domains, long before inbox placement visibly suffers. Across 1,726,176 emails sent over 90 days on Danish Lead Co.'s own outbound platform, the overall figure was 2.18%, but that single average hides a gap wide enough to sink a programme: one mailbox setup in the same dataset got rejected 38.98% of the time, nearly 18 times the platform average, while the best-performing setup sat at 0.05%.
What is a cold email bounce rate?
A cold email bounce rate is the percentage of sent emails that are rejected by the recipient's mail server and never reach an inbox, counted against total sends in a given window. A bounce is different from a response, an open, or a spam complaint: it is the mail server itself refusing the message, either because the address does not exist (a hard bounce) or because of a temporary block such as a full inbox or a greylist delay (a soft bounce). The figure matters more than most metrics it sits next to because mailbox providers use it directly to decide how much of a sender's future mail reaches the inbox at all, rather than the spam folder.
What counts as a good bounce rate for B2B cold email?
A good cold email bounce rate sits close to our own 90-day platform average of 2.18%, and anything climbing well past that on a specific mailbox or domain is worth investigating before it spreads. There is no universal published threshold that applies to every sender, because mailbox providers weigh this figure alongside complaint rate, send volume, and domain age together, not in isolation. What a buyer or operator can use instead is a real range: across 532 campaigns in the same window, the monthly figure moved between 0.78% and 2.32%, so a number sitting noticeably outside that band on a live campaign is the signal to check infrastructure before sending more volume.
| Month | Emails sent | Bounce rate |
|---|---|---|
| 2026-03 | 35,261 | 1.01% |
| 2026-04 | 500,476 | 0.78% |
| 2026-05 | 485,040 | 1.85% |
| 2026-06 | 545,537 | 2.32% |
| 2026-07 | 597,855 | 2.3% |
| 2026-08 | 579,174 | 2.17% |
| 2026-09 | 519,913 | 2.06% |
Why does bounce rate vary so much between providers and setups?
It varies this much because the mailbox setup behind a send, not the list itself, is usually the bigger factor. Across nine infrastructure setups running on the same platform in the same 90 days, rejections ranged from 0.05% to 38.98% of sends, and the gap was concentrated in one pattern: manually configured mailboxes without managed warmup or ongoing monitoring got rejected far more than setups built and maintained specifically for cold outreach. A list of the same quality sent through two different setups can see outcomes more than ten times apart.
| Provider / setup | Sends | Bounce rate |
|---|---|---|
| Maildoso | 215,011 | 0.05% |
| Google (Manual Setup) | 9,987 | 0.62% |
| Google Hypertide | 456,044 | 1.77% |
| Google Inboxlee | 71,068 | 1.18% |
| Google Zapmail | 413,003 | 1.93% |
| Google Icemail | 104,279 | 2.63% |
| Google InboxAutomate | 7,181 | 0.63% |
| Outlook Hypertide | 444,020 | 3.13% |
| Outlook (Manual Setup) | 10,604 | 38.98% |
What causes a cold email bounce rate to spike?
A spike is almost always one of three things: a stale or unverified list, a mailbox that lost reputation from being pushed too hard too fast, or a manual setup missing the warmup and monitoring a managed one has by default. The data above points at the third cause directly: the one setup in our platform rejected 38.98% of sends and was also the only one configured and run manually rather than through a managed sending provider, and it did not outperform the rest of the platform in any other metric despite the extra risk. A high figure on a verified list almost always traces back to the sending infrastructure, not the contacts.
- Stale or unverified lists. In the same 90-day window, 2,461,206 leads were processed and only 30.82% came back verified deliverable, with 35.89% excluded before a single email was sent. Sending to the unverified remainder inflates the number directly.
- Manual mailbox setups without warmup. The 38.98% figure above sat on a manually configured Outlook setup; every other setup in the dataset, Google or Outlook, ran through managed infrastructure and stayed under 4%.
- Volume ramped faster than domain reputation can absorb. This is the mechanism behind domain reputation dropping: a new domain sending high volume immediately gets flagged before it has a sending history.
How do you fix a rising bounce rate?
Fixing it means working backwards through the same three causes in order: verify the list, isolate the mailbox, then rebuild sending volume gradually rather than restarting at full speed.
- Re-verify the list before the next send. Run every contact through a deliverability check and exclude anything unverified; treat the 30.82% figure above as a realistic expectation for a cold list, not a worst case.
- Pull the worst-performing mailbox or domain out of rotation immediately. A single setup bouncing at 38.98% does not just waste its own sends: it drags down the sending domain's reputation for every other mailbox on it.
- Check whether the setup is manual or managed. If a mailbox was configured by hand rather than through a dedicated sending platform, that is the first thing to audit, per the pattern above.
- Ramp volume back up slowly on a recovering domain. A domain that has already bounced hard needs a lower daily send volume for one to two weeks before returning to normal, not an immediate return to full volume.
- Re-run a full deliverability audit rather than assuming one fix solved it. Rejections, spam placement, and sender reputation move together; checking only the number that prompted the alarm misses the other two.
Does a high bounce rate always mean bad list quality?
No. A high figure often means the sending infrastructure is the problem, not the list, which is the opposite of what most teams assume first. The data above shows this directly: the 38.98% came from a manually configured setup, not from a worse list, since every other setup in the same window drew from comparable sources and stayed under 4%. Blaming the list and buying a new one without checking the mailbox setup usually reproduces the same outcome on the next send.
How does this compare to running outbound in-house versus with a managed provider?
An in-house team running outbound through manually configured mailboxes is the exact setup that produced the 38.98% outlier in our own data, which is why infrastructure management is one of the parts of outbound that is hardest to do well without dedicated tooling. A managed provider's advantage here is not better contacts, it is that the number of mailboxes and their configuration is monitored continuously rather than set up once and left alone. Teams comparing outsourcing versus hiring an SDR team should weigh this specifically: a new in-house hire is rarely also a deliverability specialist, and this is the metric that punishes that gap fastest.
| Comparison point | Manual mailbox setup | Managed sending infrastructure |
|---|---|---|
| Rejected sends in our data | 38.98% (Outlook, manual) | 0.05% to 3.13% across eight managed setups |
| Warmup | Usually none | Built in and ongoing |
| Monitoring | Reactive, after responses dry up | Continuous, before it affects sends |
| Recovery if flagged | Slow, often restarts the domain | Faster, spread across more infrastructure |
What this means for your next deliverability check
If your team cannot currently break this figure down by mailbox or sending setup, that is the gap to close before the next volume increase, because an aggregate number hides exactly the kind of outlier shown here. On a call with Danish Lead Co., we run this same breakdown against your live infrastructure: rejections by mailbox, by provider, and by month, measured against the ranges in this piece. You leave knowing which setups are safe to scale and which ones need rebuilding, backed by outbound systems built to catch this before it costs you a domain. Book a call to get your own infrastructure checked.