---
title: "Cold Email Bounce Rate: Benchmarks & Fixes (2026)"
description: What is a good cold email bounce rate in 2026? Hard vs soft bounces, SMTP codes, the 2% and 5% rules, why catch-alls hurt, and how to bring bounces down fast.
---
[](https://www.genflows.com/)
[Case Studies](https://www.genflows.com/#case-studies) [Deliverables](https://www.genflows.com/#deliverables) [Process](https://www.genflows.com/#process) [Team](https://www.genflows.com/#team) [FAQ](https://www.genflows.com/#faq)
[Book a Call](https://app.iclosed.io/e/genflows/discovery-genflows)
[Home](https://www.genflows.com/) / [Blog](https://www.genflows.com/blog)
[Cold Email](https://www.genflows.com/blog/tag/cold-email)
# Cold Email Bounce Rate: Benchmarks & Fixes (2026)
GenFlows Team · Oct 15, 2026, 2:43:30 PM · 7 min read
TL;DR
- **Aim for under 2%.** That is the common practitioner and vendor target *(directional)*. Sending tools typically auto-pause around 5%. Instantly’s default is above 5%.
- **Google and Microsoft do not publish a bounce-rate threshold.** Google’s numeric limit is for spam complaints (below 0.3%, ideally below 0.10%). For bounces it says to cut volume when errors rise.
- **Read the code before you act.** A 5.1.1 means the address is bad, so suppress it. A 5.7.x means you were blocked for policy or authentication, so fix your setup and keep the contact.
- **Catch-all domains are the hidden risk.** Hunter reports a 27% bounce rate on its accept-all test segment against 1% for valid addresses *(single vendor test)*.
- **Verify twice.** Once when you build the list, and again just before sending.
A high bounce rate is the fastest way to damage a new sending domain. Every bounce tells mailbox providers you do not know who you are writing to. This guide explains the two bounce types, what the codes mean, the thresholds worth using, and the fixes that move the number.
It sits next to our guides on [email verification tools](https://www.genflows.com/blog/best-email-verification-tools-2026), [deliverability monitoring](https://www.genflows.com/blog/cold-email-deliverability-monitoring-2026) and [recovering a blacklisted domain](https://www.genflows.com/blog/cold-email-domain-blacklisted-recovery-2026).
*Sourcing note: SMTP code meanings come from RFC 3463, and Google’s guidance from its sender help page. Tool thresholds come from vendor help centers, read in October 2026. Items marked (directional) come from snippets, vendor blogs or single tests. We could not read Microsoft’s primary sender page, so we do not state a Microsoft bounce rule.*
## The Short Answer
Keep bounces under 2%, pause a campaign at 3–5%, and treat anything above that as a data or setup problem, not a copy problem. The 2% figure is a practitioner target, not a mailbox-provider rule. The useful habit is to separate bad addresses (remove them) from blocks (fix your infrastructure).
## Hard Bounces vs Soft Bounces
RFC 3463 splits delivery failures by status class. A **4.x.x** code is a persistent transient failure: the message is valid and a later retry may work. A **5.x.x** code is a permanent failure: resending the same message to the same address is unlikely to help.
| Bounce type | Example code | Likely cause | Action |
| --- | --- | --- | --- |
| Hard, invalid address | 550 5.1.1 | Mailbox does not exist: stale data or a typo | Suppress permanently; fix the data source |
| Soft, mailbox full | 4.2.2 (some servers send 5.2.2, directional) | Recipient over quota | Retry later; drop after repeated failures |
| Soft, temporary | 4.x.x | Busy server, greylisting, throttling | Retry; slow volume if it persists |
| Block, policy or authentication | 550 5.7.1, 550 5.7.515 | Failed SPF, DKIM or DMARC, reputation or policy | Fix DNS and authentication, lower volume; keep the contact |
| Catch-all risk | Accepted, then silence or a late bounce | Domain accepts all mail | Segment, send a small sample, monitor |
Lemlist’s help center makes the same split: invalid addresses, typos and closed accounts are hard bounces to remove right away, while repeated soft bounces can turn into hard ones *(directional)*.
**Do not delete 5.7.x contacts.** RFC 3463 describes X.7.x as policy failures where sender and recipient share responsibility. The address may be perfectly good. Deleting it hides an authentication or reputation problem. Check your [SPF, DKIM and DMARC setup](https://www.genflows.com/blog/cold-email-spf-dkim-dmarc-setup-2026) first.
## What Is an Acceptable Bounce Rate?
| Source | What it says | Type |
| --- | --- | --- |
| Google sender guidelines | No bounce threshold. Reduce volume when bounces or deferrals rise; auto-unsubscribe repeat bouncers. Spam rate below 0.3%, ideally below 0.10% | Provider guidance |
| Microsoft | No bounce threshold found; high-volume senders must pass SPF, DKIM and DMARC alignment (directional) | Provider guidance |
| Instantly | Auto-pause default above 5%, adjustable in Preferences | Tool default |
| Smartlead | Describes the industry standard as usually under 5% (directional) | Vendor guidance |
| Practitioner blogs | Under 2% as the target (directional) | Rule of thumb |
The honest summary: under 2% is a target, around 5% is where tools pause you, and no mailbox provider publishes a number. We recommend you pause earlier than the tool does. A new domain has little reputation to spend, which is why [mailbox volume planning](https://www.genflows.com/blog/how-many-domains-mailboxes-cold-email-2026) matters as much as list quality.
## Why Cold Lists Bounce
- **Stale or purchased data.** Closed accounts and role changes produce 5.1.1 errors. Our guide to [building a B2B cold email list](https://www.genflows.com/blog/how-to-build-b2b-cold-email-list-2026) covers sourcing.
- **Catch-all domains.** The server accepts every address, so verifiers cannot confirm the mailbox. Hunter’s experiment saw 27% bounces on accept-all addresses versus 1% on valid ones *(single vendor test)*.
- **Typos and closed accounts.** Common in scraped or hand-entered data *(lemlist help, directional)*.
- **Authentication failures.** Google requires SPF or DKIM for all senders, and SPF, DKIM and DMARC for bulk senders sending more than 5,000 messages a day.
- **New mailbox reputation.** Lemlist suggests roughly 30–40 emails a day on a new mailbox *(directional)*. Sudden volume can trigger blocks.
We found no primary source on role-account bounce behaviour, so we make no claim about it.
## How to Bring Bounces Down
1. **Verify at build time and again before sending.** Addresses decay between enrichment and send. The re-verification interval is our recommendation; no source defines one.
2. **Segment catch-alls.** Send a small sample first (a 5–10% sample is a vendor suggestion, directional) and scale only if it stays clean.
3. **Suppress hard bounces everywhere.** Add them to a global suppression list, not just one campaign.
4. **Cut volume when errors rise.** This is Google’s own advice for rising bounces or deferrals.
5. **Separate bounces from blocks in your reporting.** Read the enhanced status code. Mixing them hides the real cause.
6. **Turn on auto-pause** and set it lower than the default if your domains are new.
## How Sending Tools Handle Bounces
- **Instantly:** auto-pauses above 5% by default, checked only after a campaign has sent 200 emails, with a 7-day exemption after you resume.
- **Smartlead:** “High Bounce Rate Auto Protection” uses a threshold you set, pauses the campaign and fires a webhook. Its help article calculates the rate against total leads, not emails sent, and the minimum volume is not documented *(directional)*.
- **lemlist:** help articles give conflicting figures (manual 5%, alerts at 10%, auto-pause far higher) *(directional)*. Check the app before relying on any of them.
Because defaults differ, compare them in our [Smartlead vs Instantly](https://www.genflows.com/blog/smartlead-vs-instantly-2026) guide, and wire bounces into your CRM using the steps in [syncing outbound data into HubSpot](https://www.genflows.com/blog/sync-cold-email-linkedin-data-hubspot-2026).
## Frequently Asked Questions
### What is a good cold email bounce rate?
Under 2% is the common target *(directional; practitioner and vendor guidance)*. Tools such as Instantly auto-pause above 5% by default. Neither Google nor Microsoft publishes a bounce-rate threshold.
### What is the difference between a hard and a soft bounce?
Under RFC 3463, a 4.x.x code is a transient failure that may succeed on retry, and a 5.x.x code is a permanent failure. Hard bounces should be suppressed, and soft ones retried or dropped after repeated failures.
### What does error 5.1.1 mean?
It means the destination mailbox does not exist, usually from stale data or a typo. Suppress the address permanently and review where the data came from.
### Is a 5.7.x error the same as a bad address?
No. A 5.7.x code is a policy or authentication refusal. The address may be valid, so fix your SPF, DKIM, DMARC, content or volume rather than deleting the contact.
### Do catch-all emails cause bounces?
They can. Hunter reported 27% bounces on its accept-all test segment against 1% for valid addresses *(single vendor test)*. Segment catch-alls, send a small sample, and monitor before scaling.
### At what bounce rate should I pause a campaign?
Instantly’s default auto-pause is above 5% after 200 sends. We suggest pausing earlier, around 3%, on new domains. That is our recommendation, not a provider rule.
---
**Want clean lists and safe sending infrastructure without the guesswork?** Start with our [email verification guide](https://www.genflows.com/blog/best-email-verification-tools-2026), or [talk to our team](https://www.genflows.com/).
*By the GenFlows GTM engineering team. Tool defaults change often; confirm them in your account. Last updated October 2026.*
[#Cold Email](https://www.genflows.com/blog/tag/cold-email)
Share [in](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fwww.genflows.com%2Fblog%2Fcold-email-bounce-rate-benchmarks-fixes-2026) [X](https://twitter.com/intent/tweet?url=https%3A%2F%2Fwww.genflows.com%2Fblog%2Fcold-email-bounce-rate-benchmarks-fixes-2026&text=%3Cspan+id%3D%22hs_cos_wrapper_name%22+class%3D%22hs_cos_wrapper+hs_cos_wrapper_meta_field+hs_cos_wrapper_type_text%22+style%3D%22%22+data-hs-cos-general-type%3D%22meta_field%22+data-hs-cos-type%3D%22text%22+%3ECold+Email+Bounce+Rate%3A+Benchmarks+%26+Fixes+%282026%29%3C%2Fspan%3E)
↗
Written by
GenFlows Team
The GenFlows team builds AI-powered cold outbound systems for B2B teams.
On this page
## Keep reading
### [Outbound Systems Sales Navigator HubSpot Integration: Plans & Limits (2026) Oct 15, 2026, 2:38:03 PM Read →](https://www.genflows.com/blog/linkedin-sales-navigator-hubspot-integration-2026)
### [Cold Email Instantly HubSpot Integration: Setup & Sync (2026) Oct 14, 2026, 3:30:45 PM Read →](https://www.genflows.com/blog/instantly-hubspot-integration-2026)
### [Cold Email lemlist HubSpot Integration: Setup & Limits (2026) Oct 14, 2026, 3:27:57 PM Read →](https://www.genflows.com/blog/lemlist-hubspot-integration-2026)
## Ready to fill your calendar?
We build AI-powered cold outbound engines that book meetings on autopilot. Let's see if it fits your team.
[Book a Call](https://app.iclosed.io/e/genflows/discovery-genflows)
Precision-engineered outbound systems for B2B companies.
[](https://www.clay.com/experts/partner/wouter-harink?via=wouter) [](https://www.clay.com/experts/partner/wouter-harink?via=wouter) [](https://www.smartlead.ai/partner/wouter-harink)
Explore
- [How it works](https://www.genflows.com/#process)
- [Results](https://www.genflows.com/#results)
- [Revenue calculator](https://www.genflows.com/#calculator)
- [About](https://www.genflows.com/#founder)
Reach us
- [info@genflowsagency.com](mailto:info@genflowsagency.com)
- [Book a call](https://app.iclosed.io/e/genflows/discovery-genflows)
- [LinkedIn](https://www.linkedin.com/company/genflows-agency/)
© 2026 GenFlows Agency. All rights reserved.
[Privacy](https://www.genflows.com/privacy) [Terms](https://www.genflows.com/terms) v1.0
```json
{
"@context" : "https://schema.org",
"@type" : "BlogPosting",
"author" : {
"@type" : "Person",
"name" : "GenFlows Team"
},
"dateModified" : "2026-10-15T12:43:31Z",
"datePublished" : "2026-10-15T12:43:30Z",
"description" : "What is a good cold email bounce rate in 2026? Hard vs soft bounces, SMTP codes, the 2% and 5% rules, why catch-alls hurt, and how to bring bounces down fast.",
"headline" : "Cold Email Bounce Rate: Benchmarks & Fixes (2026)",
"image" : [ "" ],
"keywords" : "Cold Email",
"mainEntityOfPage" : {
"@id" : "https://www.genflows.com/blog/cold-email-bounce-rate-benchmarks-fixes-2026",
"@type" : "WebPage"
},
"publisher" : {
"@type" : "Organization",
"logo" : {
"@type" : "ImageObject",
"url" : ""
},
"name" : "GenFlows"
},
"wordCount" : 1366
}
```
```json
{
"@context" : "https://schema.org",
"@type" : "BreadcrumbList",
"itemListElement" : [ {
"@type" : "ListItem",
"item" : "https://www.genflows.com/",
"name" : "Home",
"position" : 1
}, {
"@type" : "ListItem",
"item" : "https://www.genflows.com/blog",
"name" : "Blog",
"position" : 2
}, {
"@type" : "ListItem",
"name" : "Cold Email Bounce Rate: Benchmarks & Fixes (2026)",
"position" : 3
} ]
}
```
```json
{
"@context" : "https://schema.org",
"@type" : "BlogPosting",
"author" : {
"@type" : "Person",
"name" : "GenFlows Team",
"url" : "https://www.genflows.com/blog/author/genflows-team"
},
"datePublished" : "2026-10-15T12:43:30.000Z",
"headline" : "Cold Email Bounce Rate: Benchmarks & Fixes (2026)",
"mainEntityOfPage" : {
"@id" : "https://www.genflows.com/blog/cold-email-bounce-rate-benchmarks-fixes-2026",
"@type" : "WebPage"
},
"publisher" : {
"@type" : "Organization",
"logo" : {
"@type" : "ImageObject"
}
}
}
```
```json
{
"@context" : "https://schema.org",
"@type" : "FAQPage",
"mainEntity" : [ {
"@type" : "Question",
"acceptedAnswer" : {
"@type" : "Answer",
"text" : "Under 2% is the common target (directional; practitioner and vendor guidance). Tools such as Instantly auto-pause above 5% by default. Neither Google nor Microsoft publishes a bounce-rate threshold."
},
"name" : "What is a good cold email bounce rate?"
}, {
"@type" : "Question",
"acceptedAnswer" : {
"@type" : "Answer",
"text" : "Under RFC 3463, a 4.x.x code is a transient failure that may succeed on retry, and a 5.x.x code is a permanent failure. Hard bounces should be suppressed, and soft ones retried or dropped after repeated failures."
},
"name" : "What is the difference between a hard and a soft bounce?"
}, {
"@type" : "Question",
"acceptedAnswer" : {
"@type" : "Answer",
"text" : "It means the destination mailbox does not exist, usually from stale data or a typo. Suppress the address permanently and review where the data came from."
},
"name" : "What does error 5.1.1 mean?"
}, {
"@type" : "Question",
"acceptedAnswer" : {
"@type" : "Answer",
"text" : "No. A 5.7.x code is a policy or authentication refusal. The address may be valid, so fix your SPF, DKIM, DMARC, content or volume rather than deleting the contact."
},
"name" : "Is a 5.7.x error the same as a bad address?"
}, {
"@type" : "Question",
"acceptedAnswer" : {
"@type" : "Answer",
"text" : "They can. Hunter reported 27% bounces on its accept-all test segment against 1% for valid addresses (single vendor test). Segment catch-alls, send a small sample, and monitor before scaling."
},
"name" : "Do catch-all emails cause bounces?"
}, {
"@type" : "Question",
"acceptedAnswer" : {
"@type" : "Answer",
"text" : "Instantly’s default auto-pause is above 5% after 200 sends. We suggest pausing earlier, around 3%, on new domains. That is our recommendation, not a provider rule."
},
"name" : "At what bounce rate should I pause a campaign?"
} ]
}
```