Article
Cold Email Bounce Rate Benchmarks: What Is a Safe Number?
By Unlimited Verifier Team ·

Summary
A safe cold email bounce rate is under 2% of emails attempted, and under 1% on the first sends from a new list. No reliable industry average exists because published figures depend on list source, verification and how bounces are defined.A safe cold email bounce rate is under 2% of emails attempted, and under 1% on the first sends from any new list, since cold lists are usually older and less confirmed than newsletter lists. Amazon SES starts an account review at 5%, but no reliable industry average exists because published figures depend on list source, verification and definition. This guide explains what the numbers mean, where they come from, and how to keep a cold campaign inside them. For the wider context, start with our sales prospecting verification guide.
Quick answer
- Ceiling: keep each cold campaign under 2% bounces (bounces ÷ emails attempted).
- First sends from a new list: aim for under 1%.
- Stop line: at 3% or higher, pause and investigate before the next send. This is our recommended rule, not a platform rule.
- Average: there is no trustworthy published industry average. Rates depend on list source and on whether the list was verified first.
- Fix: verify the full list before the first send, send only Valid addresses, hold Risky ones back, and ramp up in small batches.
What is a good cold email bounce rate?
A good cold email bounce rate is under 2%, with under 1% as the goal for new lists. Cold email reaches people who never opted in, so mailbox providers and sending platforms tolerate less bounce activity than they would for a newsletter sent to subscribers.
Sources disagree on the exact line. Amazon's SES documentation describes 5% as the review point and 10% as the level that can lead to a pause. That is a platform limit, not a deliverability target. A campaign at 5% has already reached the point where the platform intervenes, so treating 5% as acceptable leaves no margin. We recommend 2% as the ceiling because it leaves room for the re-entry sends and batch-to-batch variation that follow any problem.
Bounce rate also has a blind spot. A catch-all domain accepts mail at the SMTP stage whether or not the mailbox exists, so a dead address on that domain may never appear as a bounce. A campaign can report 0.8% bounces and still be a poor list. A good bounce rate is necessary, but it is not sufficient.
Bottom line: Use 2% as your ceiling and 1% as your goal for new lists. A low bounce rate alone does not prove the list is healthy.
What is the average cold email bounce rate?
There is no reliable single average. Vendor figures come from their own customers, whose lists, sources and verification habits differ widely. Treat any published "industry average" as marketing unless the vendor discloses its sample, its method and its definition of a bounce.
Three factors make averages misleading:
- Verification timing. A list verified in the last 30 days behaves very differently from one exported and sent the same day.
- List source. Addresses from a data provider, scraped company pages and old event lists age at different rates.
- Definition. Some reports count soft bounces, some count only hard bounces, and some divide by delivered mail instead of sent mail.
The more useful benchmark is your own per-campaign trend, measured against the thresholds in this guide. The table below describes typical patterns by list source. These are qualitative patterns, not measured rates, so replace them with your own numbers as soon as you have them.
| List source | Typical pattern | Main driver | First action |
|---|---|---|---|
| Verified within the last 30 days (B2B) | Usually low and steady | Job changes since the last check | Re-verify segments older than your last check |
| Exported from a data provider, unverified | Variable, often with spikes after the first send | Guessed or outdated addresses | Verify the full list before sending |
| Scraped from company websites | Often high | Role addresses, catch-alls, dead mailboxes | Verify, drop Invalid, hold Risky |
| Old trade-show or event list | Often high and concentrated | Addresses that are years old | Treat as a new list and verify all of it |
| Guessed addresses from a finder | Depends on the finder's confidence | Unconfirmed patterns such as first.last@ | Verify each one; see how Apollo's verified and guessed statuses differ |
Experienced outbound teams commonly report that bounces cluster by company domain. When a company is acquired, renamed or retires its mail system, every address on that domain can fail together. Grouping bounces by domain often reveals one bad source faster than reading the campaign total.
Bottom line: No published average should set your target. Measure your own list sources and use the thresholds below to decide what to do.
Why do cold email bounce rates run higher than newsletter rates?
Cold lists run higher because their addresses are usually older, less confirmed and not tied to a consent relationship. A newsletter list typically has a subscription event and recent engagement behind it. A cold list typically has neither, so every unverified address is a guess about whether the mailbox still exists.
Two bounce types matter, and RFC 3463 defines their enhanced status codes:
- Hard bounces are permanent failures. Code 5.1.1 means the destination mailbox does not exist. Code 5.1.2 means the destination system address is invalid, which often points to a domain that no longer receives mail.
- Soft bounces are temporary failures. Code 4.2.2 typically means the mailbox is full. Soft bounces usually clear on retry, but a soft bounce that repeats across sends should be treated as hard.
Hard bounces tell you about list quality. Soft bounces tell you about recipient mailbox capacity and retry behaviour. Mixing them into one number hides the problem you need to fix.
B2B lists decay faster than many teams expect. People change jobs and companies retire mailboxes, so an address that was valid last quarter can return a 5.1.1 today. Re-verifying before each cold campaign therefore matters more than a quarterly clean-up.
Bottom line: Cold lists bounce more because they are older and unconfirmed. Separate hard from soft bounces so you fix the right problem.
How do you calculate cold email bounce rate correctly?
Divide bounced emails by emails attempted, then multiply by 100. For example, 45 bounces from 1,800 attempts is 45 ÷ 1,800 × 100 = 2.5%.
Split that total by type. If 38 of the 45 bounces are hard, the hard rate is 38 ÷ 1,800 × 100 = 2.1%, and the soft rate is 7 ÷ 1,800 × 100 = 0.4%. The hard rate is the one that threatens sender reputation, so it is the number to act on.
Watch for three definition traps:
- Denominator. Some dashboards divide by delivered mail. At low rates the gap is small, but on a list with heavy retries it can hide a problem.
- Repeat bounces. If one address bounces on two follow-up sends, count it once when you judge list quality.
- Classification. Sequencers and ESPs label 4.x.x and 5.x.x codes differently. Teams sending through Smartlead or Instantly should confirm how their tool classifies bounces before setting alerts or comparing reports.
Bottom line: Use attempts as the denominator and track hard bounces separately from soft ones.
Which bounce thresholds should you use?
Use 2% as your ceiling, 3% as your stop line and the decision table below. No single source sets a cold email threshold, and the published figures measure different things.
| Source | Figure | What it measures | How to use it |
|---|---|---|---|
| Amazon SES documentation | 5% review point, 10% pause risk | Account-level bounce rate | Platform limit; don't plan to it |
| Google's bulk sender guidelines | Spam reports below 0.3% | Spam complaints, not bounces | Watch alongside bounces |
| Yahoo sender requirements | Complaint-rate expectations around 0.3% | Complaints | Same as Google |
| Our recommendation | Under 2% ceiling, under 1% target | Bounces per campaign and per batch | Use this for planning |
Google and Yahoo measure complaints, which damage reputation faster than bounces do. Keep both in view. Once you have a measured rate, use this table to choose an action:
| Batch or campaign bounce rate | Meaning | Action |
|---|---|---|
| Under 1% | Healthy | Continue the ramp |
| 1% to under 2% | Acceptable | Continue, and check your top five bounce domains |
| 2% to under 3% | Warning | Pause, verify the rest of the list, and resend to Valid only |
| 3% to under 5% | Stop | Halt the campaign, check domain blacklist status and review the list source |
| 5% or higher | Platform risk | Pause all sending on the account and investigate before any further sends |
Bottom line: Use 2% as the ceiling, 3% as the stop line, and the table above to decide what happens next.
How do you bring a cold campaign under 2%?
Verify the full list, send only Valid addresses, and measure every batch against the thresholds in this guide. Most of the work happens before the first send, where bounces are cheapest to prevent.
- Define your denominator and tag bounce types. Track hard and soft bounces separately, using attempts as the base.
- Verify the full list before the first send. Don't rely on a provider's status labels alone. If your prospects arrive through a signup form, real-time email validation stops bad addresses before they enter the list.
- Group bounces by domain. A company domain with three or more bounces in one batch is a candidate for removal, even if some of its addresses look valid.
- Send Valid addresses only. Hold Risky contacts, including catch-all and role-based addresses, until the main list has shown stable results.
- Ramp in small batches per sending inbox. Start with low daily volumes and increase them over several weeks. Warm-up protects reputation and capacity, so don't jump straight to full volume.
- Check each batch within 24 to 48 hours. Apply the decision table to every batch, not only the campaign total.
- Log per-batch results and re-verify monthly. The counts are your evidence if a platform or client asks what happened. For the full schedule, see email list maintenance best practices.
Bottom line: Verify before you send, send Valid only, and judge each batch on its own.
Hands-on tutorial: verify a cold list before the first send
This walkthrough uses Unlimited Verifier for the verification stage. You need a CSV or Excel file of prospects. For a longer version of this stage, see the cold email list verification workflow.
- Export your list as a CSV. Keep the email column and any segmentation fields, such as company domain or job title.
- Create an account. The Free plan lets you test a small list first. Free results are kept for 24 hours, so export them the same day. Pro keeps results for 30 days.
- Upload the file. Go to Upload and verify a list. CSV and Excel files up to 10MB are accepted, and the email column is detected automatically.
- Run the verification. Each address is checked for syntax, domain, MX records and the SMTP mailbox. Catch-all domains, disposable addresses and role-based addresses are flagged.
- Read the three buckets. Valid addresses go into the first sends. Invalid addresses are removed and suppressed. Risky addresses, including catch-all results, are held back.
- Check suspicious single addresses. Use the free email checker for one contact. For how catch-all domains are handled, see the catch-all email verification page.
- Export the results as CSV, Excel or JSON. Save the summary counts as your batch baseline.
- Re-import Valid contacts into your sending tool as a new segment, and add Invalid contacts to its suppression list.
Unlimited Verifier has no native sequencer, CRM or Zapier integrations, so the workflow is export, verify and re-import, or calling the API directly. API access is included on Pro, which covers 100,000 emails a month. The email verification API accepts single-email checks and bulk batches of up to 10,000 emails per request. Teams building this into their own email verification API and automation scripts can run the export, verify and import loop on a schedule. Teams running enrichment chains should also see our guide to verifiers for Clay waterfall enrichment.
Bottom line: Export, verify, send only Valid, suppress Invalid and hold Risky until the main list has proven itself.
Worked example: a 4,000-prospect campaign
The numbers below are illustrative, and the verification split is hypothetical. The plan limits and arithmetic are real.
The starting point: A SaaS team, one of the common cases covered in email verification for ecommerce and SaaS, sends 4,000 prospects from a scraped list without verifying first. The campaign produces 260 bounces:
260 ÷ 4,000 × 100 = 6.5% bounce rate
That is above the 5% review point, so the team pauses sending.
The plan limits: The Free plan allows lists of up to 150 emails, with 25 lists a month. That caps the month at 150 × 25 = 3,750 emails, so 4,000 contacts won't fit. The Pro plan at $29 a month, or $25 a month billed annually, accepts lists of up to 25,000 emails, so all 4,000 fit in one list.
The verification split (hypothetical):
- Valid: 3,350 (83.75%)
- Risky: 310 (7.75%)
- Invalid: 340 (8.5%)
Check: 3,350 + 310 + 340 = 4,000.
The send plan:
- Remove and suppress the 340 Invalid addresses.
- Hold the 310 Risky addresses for a small test later.
- Send to the 3,350 Valid addresses in batches, starting with the most engaged.
If 27 of the Valid addresses still bounce, the rate is:
27 ÷ 3,350 × 100 = 0.81%
That is inside the under-1% target. The move from 6.5% to about 0.8% comes from verification and segmentation, not from a different sending tool. The second figure is a projection from the hypothetical split, so measure your own campaign before you rely on it.
Cost: Pro is $29 a month, or $25 a month billed annually. Standard verification is unlimited on every plan, so checking all 4,000 addresses carries no per-email fee. If you also run deep verification on all 4,000 rows, that uses 4,000 of the 25,000 deep verifications included each month on Pro. For a broader comparison of plan costs, see email verification pricing.
Bottom line: At 4,000 contacts, the Pro list cap is not a constraint. The arithmetic shows how verification moved a campaign from above the review point to inside the target.
Worked example: a campaign average that hides a bad batch
The batch figures below are illustrative. Assume the same 4,000 verified contacts, sent in five batches of 800, with these bounce counts: 6, 8, 5, 41 and 7.
The campaign total is:
67 ÷ 4,000 × 100 = 1.7%
That passes the 2% ceiling, and a report that shows only the total would look healthy. Now check each batch:
- Batch 1: 6 ÷ 800 = 0.75%
- Batch 2: 8 ÷ 800 = 1.0%
- Batch 3: 5 ÷ 800 = 0.6%
- Batch 4: 41 ÷ 800 = 5.1%
- Batch 5: 7 ÷ 800 = 0.9%
Batch 4 is over the 5% line on its own, so the decision table calls for pausing all sending. The campaign total hid that. Batch 4 probably came from one contaminated source, which domain grouping would show. The lesson is that the total is for reporting and the batch is for decisions.
Bottom line: Measure every batch separately. A healthy campaign total can conceal one batch that puts your account at risk.
Which verification method predicts bounces best?
The SMTP mailbox check is generally the strongest single predictor of a bounce, but only where the receiving server gives a clear answer. The table below compares the main approaches.
| Approach | What it catches | What it misses | Bounce prediction |
|---|---|---|---|
| Syntax-only check | Typos, missing @ signs, invalid characters | Nonexistent mailboxes | Low |
| Domain and MX check | Dead domains and domains with no mail server | Nonexistent mailboxes on a live domain | Medium-low |
| SMTP mailbox check | Nonexistent mailboxes on servers that respond | Catch-alls and servers that block probes | High where the server responds |
| Catch-all detection and Risky holdback | Domains that accept any address | Whether the individual mailbox exists | Flags uncertainty instead of guessing |
| Engagement recency | Dormant but real contacts | Bad data | Predicts opens and complaints more than bounces |
Unlimited Verifier checks syntax, domain, MX records and the SMTP mailbox, detects catch-all domains, and flags disposable and role-based addresses. Results are sorted into Valid, Risky and Invalid. The company states 99.5% accuracy for deep verification. That is Unlimited Verifier's own figure, not an independent benchmark.
If you are comparing best email verification tools, check how each one handles catch-all domains and whether its results split into three buckets. Our guides to the best email verification tools and how to choose an email verifier cover the selection criteria in more depth. If your guessed addresses come from a finder, compare options in our best email finders for B2B prospecting guide before you verify them. Verification also supports broader email verification compliance and hygiene, but it does not prove consent.
Bottom line: SMTP checks are the strongest bounce predictor, and catch-all flags show where that predictor runs out.
What are the most common mistakes with cold email bounce benchmarks?
- Treating 5% as a target. It is a platform review point. Your working ceiling should be 2%.
- Comparing your rate to a vendor's average. Vendor averages reflect their customers' lists and definitions, not yours.
- Dividing by delivered mail. This makes the denominator inconsistent across tools and reports.
- Mixing hard and soft bounces. A high soft rate from full mailboxes calls for a different fix than a high hard rate.
- Measuring only the campaign total. One bad source can hide inside a healthy-looking average, as the batch example shows.
- Sending Risky addresses first. Catch-alls and role addresses belong at the end of the ramp.
- Verifying once and sending for months. B2B lists decay, so re-verify before each campaign.
- Losing results before exporting. Free plan results are kept for 24 hours, so export on the same day.
Bottom line: Most bounce problems come from measuring the wrong thing or verifying too late.
How we compared (and limitations)
This guide is based on public documentation: the Amazon SES documentation, Google's bulk sender guidelines, Yahoo's sender requirements, the RFC 3463 status code definitions, and sender best practices published by M3AAWG. We have not run controlled tests against any platform's review process, and we have not measured bounce rates for any list source. The 4,000-contact and batch examples use hypothetical figures.
Thresholds change without notice, and mailbox providers do not publish their full reputation criteria. Treat every figure here as a planning number to check against your own data. Verification cannot confirm that a contact opted in, and SMTP checks are inconclusive for servers that block or limit probes. Unlimited Verifier's 99.5% deep-verification accuracy is the company's stated figure.
Bottom line: Use the thresholds as a starting point, and let your own batch-level data drive the next decision.
Bounce rate thresholds and actions
| Bounce rate | Action |
|---|---|
| Under 1% | Goal for new lists; continue sending |
| 1% to under 2% | Acceptable ceiling; monitor each batch |
| 2% to under 3% | Review list source and verification before next send |
| 3% or higher | Pause, investigate and fix before sending again |
Frequently asked questions
What is a safe cold email bounce rate?
A safe cold email bounce rate is under 2% of emails attempted. For first sends from a new list, aim for under 1%, because cold lists are often older and less confirmed than newsletter lists. These are recommended guidelines, not official platform rules.
Is 5% bounce rate too high for cold email?
Yes, for cold email 5% is too high. Amazon SES documentation describes 5% as the point where its account review begins, so treating it as acceptable leaves no margin. Keeping bounces under 2% gives room for normal variation between sends.
Why is there no reliable average cold email bounce rate?
Published averages come from vendors using their own customers' lists, sources and verification habits. Those samples differ widely, and many reports do not define how bounces were counted. Any average should be treated as marketing unless its method is disclosed.
Do soft bounces count toward cold email bounce rate?
It depends on how your tool reports it. Some reports count both soft and hard bounces, while others count only hard bounces. Check the definition before comparing your rate to any benchmark, and track hard and soft bounces separately.
How do I calculate cold email bounce rate?
Divide the number of bounced emails by the total number of emails attempted, then multiply by 100. For example, 15 bounces from 1,000 emails attempted is a 1.5% bounce rate. Use attempted emails as the denominator so the figure is comparable across campaigns.
Why can a low bounce rate still mean a bad list?
Catch-all domains accept mail at the SMTP stage even when the mailbox does not exist, so dead addresses on those domains may never bounce. A campaign can show a low bounce rate while still containing many invalid contacts. Verifying the list before sending catches these addresses.
Should I verify a list before a cold email campaign?
Yes. Verifying the full list before the first send lets you send only Valid addresses, hold Risky ones back and remove Invalid ones. This is the most direct way to keep bounces under the recommended ceiling.
What should I do if my cold email bounce rate hits 3%?
Pause sending and investigate before the next campaign. Check the list source, look for catch-all domains, re-verify addresses and review the send volume. This 3% stop line is a recommended internal rule, not a platform requirement.
Cut Bounces and Protect Your Sender Reputation With Unlimited Email Verification
Every invalid address you send to hurts your sender reputation and your inbox placement. Verifying your list before each send means fewer bounces, healthier deliverability, and a predictable cost. With Unlimited Verifier, standard verification is unlimited on every plan, with no per-email fees.
Unlimited Verifier checks syntax, domain, MX records and the SMTP mailbox. It also detects catch-all domains and flags disposable and role-based addresses. Export a CSV from your email platform or CRM, upload and verify the list, then re-import the clean results. You can also automate checks with the email verification API.
| Free | Pro | |
|---|---|---|
| Price | $0 | $29/month ($25/month billed annually) |
| Lists | 25 a month, up to 150 emails each | Unlimited, up to 25,000 emails each |
| Deep verifications | 750 a month | 25,000 a month |
| API access | No | Yes (100,000 emails a month) |
| Result retention | 24 hours | 30 days |
Why teams choose Unlimited Verifier
- Unlimited standard verification on all plans, including Free, with no per-email fees.
- Catch-all detection so you know which domains accept every address.
- Clear Valid / Risky / Invalid results, exportable as CSV, Excel or JSON.
- An open-source verification engine you can inspect on GitHub.
Unlimited Verifier states 99.5% accuracy for deep verification.
Create a free account and verify your next list before you hit send.
Want to test a single address first? Try the free email checker.