Article

What Bounce Rate Is Safe for Cold Email? The 2% Ceiling Explained

By Unlimited Verifier Team ·

Diagram showing how to calculate a cold email hard bounce rate against the 2% safe ceiling.

Summary

A safe cold email bounce rate is below 2% hard bounces, with under 1% as the target for new lists and sending domains. Measure only hard bounces (SMTP 5.x.x codes) against unique addresses attempted, and verify lists before sending. If you cross 2%, pause, clean the list, and fix the source before sending more.

For cold email, keep hard bounces below 2% of the addresses you attempt, and aim for under 1% on the first sends from any new list or sending domain. Anything above 2% is a signal to stop, verify and fix the list before sending more.

Cold lists are built from data recipients never gave you permission to use for outreach, so they carry more dead and risky addresses than a newsletter list. Our pillar guide on email verification for sales prospecting covers the full workflow. This article answers the number question: what to aim for, how to calculate it, which bounces count, and what to do when you cross the line.

Quick answer


What bounce rate is safe for cold email?

A safe cold email bounce rate is below 2% hard bounces, with under 1% as the target for early sends. Treat 2% as a ceiling rather than a goal, because a campaign that lands near it has little room for error before a mailbox provider or your sending tool reacts.

Sources do not agree on one number, and the public figures were not written for cold outreach. Amazon SES's documentation describes account review starting at a 5% bounce rate and a risk of pausing at 10%. Those thresholds protect a shared sending system. Cold outreach to lists you have not verified needs a tighter working ceiling, and we recommend 2% because it keeps you clear of automated review with margin to spare.

The right number also depends on where you are in your sending history:

Situation Hard-bounce ceiling Target Why
New sending domain, first ~200 sends 1% under 0.5% No positive history with mailbox providers yet
Warmed domain, verified list 2% under 1% Established reputation absorbs a small miss
Scraped or purchased list, unverified Do not send n/a Bounce rates on unverified purchased lists are often well above 2% on a first pass
Re-engaging an older list 2% under 1% Dormant addresses decay, so expect more failures

For how cold teams actually perform, see our average cold email bounce rate benchmarks.

Bottom line: Plan for a 2% ceiling and a under-1% target, and tighten both for any new domain.

Why is the safe bounce rate lower for cold email than for newsletters?

Cold email has less margin because recipients never asked to hear from you, so there is no prior engagement to offset a bad address or a frustrated reader. A newsletter sent to people who opened last month can tolerate a few failures. A cold email to an address pulled from a directory cannot.

Mailbox providers judge senders on several signals, and complaints are the one they state most explicitly. Google's email sender guidelines ask bulk senders to keep spam rates below 0.10% in Postmaster Tools and to avoid reaching 0.30%. Yahoo's sender requirements describe similar expectations for complaints. Neither provider publishes a bounce limit as clearly, which is why the 2% ceiling is a planning number rather than a provider rule.

Bounces also work as an early warning. Dead addresses often show up in your bounce data before complaints rise, which gives you time to act if you watch the rate on every batch.

Bottom line: Cold email has less margin than newsletters because recipients never opted in, so each bounce carries more weight.

How do you calculate bounce rate correctly?

Bounce rate is the number of unique hard-bounced addresses divided by the number of unique addresses you attempted, multiplied by 100. Most miscalculations come from the denominator, so use this formula:

Bounce rate = unique hard bounces ÷ unique addresses attempted × 100

Use addresses attempted, not contacts in your CRM and not delivered emails. A list of 5,000 contacts where you only reached 2,500 in the current sequence should be measured against the 2,500. Sequences create a second trap. If an address bounces on step one and you stop sending to it, it should not appear in the denominator for step two. Counting it again inflates your rate.

Measure per campaign and per source. A blended rate can hide a problem: if one data source bounces at 0.4% and another at 7%, the average looks acceptable while one source damages your domain.

Worked calculation: You attempt 2,500 unique addresses across a three-day sequence and see 31 unique hard bounces.

31 ÷ 2,500 × 100 = 1.24%

That is under the 2% ceiling but above the 1% target. For a new domain, treat it as a warning.

Bottom line: Divide unique hard bounces by unique addresses attempted, measure per source, and leave out contacts you never tried.

Which bounces count against your list?

Only hard bounces measure list quality, and you tell them apart by the SMTP enhanced status code. RFC 3463 defines these codes. The first digit shows whether the failure is temporary (4) or permanent (5), and the next parts show the category.

Enhanced code Typical meaning Counts toward list hygiene? What to do
5.1.1 Mailbox does not exist Yes (hard) Suppress permanently
5.1.2 Destination domain or host unknown Yes (hard) Suppress; check the domain for a typo or expiry
5.7.1 Refused by policy (often reputation, authentication or blocklisting) No, not a list defect Check SPF, DKIM, DMARC, blocklists and volume
4.x.x Temporary failure (full mailbox, greylisting) Only if repeated across sends Retry; suppress after repeated soft failures

The 5.7.1 row is the one senders most often misread. Suppressing an address on a policy rejection can remove a real contact and leave the actual problem untouched. The fix is in your authentication, sending volume and content, not in the list.

Bottom line: Count 5.1.x hard bounces against the list, and treat 5.7.x rejections as a sending-reputation problem.

How many bounces can one cold campaign afford?

Convert your ceiling into a daily bounce budget, so you know exactly when to pause.

Worked example: You run three sending inboxes at 60 cold emails a day each, which is 180 sends a day.

180 × 2% = 3.6 bounces per day

Bounces arrive as whole numbers, so the budget rounds down. Three bounces is 1.67%, which is allowed. A fourth bounce takes the day to 2.2%, which is over the ceiling. Set your alert at four bounces, and pause when it fires.

Now apply a tighter scenario. You send 300 emails from a new domain, with a 1% ceiling.

300 × 1% = 3 bounces allowed on day one

If you see 9 bounces, your rate is:

9 ÷ 300 × 100 = 3.0%

That is three times the first-send ceiling. Stop, suppress the bounced addresses, and check the source before sending again.

Bottom line: Convert your ceiling into a bounce budget per day and pause the moment you exceed it.

Why does the first send from a new domain matter most?

The first sends from a new domain carry the most risk because mailbox providers have no history to weigh against a bad batch. A domain with weeks of clean sending can absorb a noisy day. A new domain often cannot.

A common rule of thumb among deliverability practitioners treats the first few hundred sends as the window that sets a domain's early reputation. The 200-send figure in this article is a planning window, not a provider rule, but it is a sensible place to tighten your limits.

Recovery is slow and expensive. If a first batch bounces heavily, you usually spend the next several weeks sending smaller volumes to rebuild trust. Verifying before the first send costs far less than that.

Bottom line: Verify before the first send from any new domain, because early bounces are the hardest to recover from.

How do you get bounce rate under 1% before you send?

Getting under 1% is a process, not a one-time cleanup. Follow these seven steps in order.

  1. Record the source of every contact. Add a column for where each address came from: a data vendor, a scrape, an event list or a CRM import. You cannot fix a problem you cannot attribute.
  2. Verify the full list before any send. Sort every address into Valid, Risky and Invalid. Verification catches syntax errors, dead domains, missing MX records and nonexistent mailboxes before they reach your sending tool.
  3. Suppress Invalid addresses permanently. Keep them out of every sequence, including follow-ups.
  4. Hold Risky addresses back. Catch-all domains accept any address, so a "deliverable" result does not confirm the mailbox exists. Disposable and role-based addresses such as info@ belong in a separate segment.
  5. Send only Valid addresses first. Start with a canary batch of 50 to 100 sends, read the bounce rate, then scale.
  6. Set an automatic pause at your ceiling. If your sending tool offers an alert or pause rule, set it at 2%. If it does not, check the rate by hand after every batch.
  7. Re-verify on a schedule. People change jobs and domains expire. Re-run verification monthly for active prospecting lists. Our guide to email list maintenance best practices covers the schedule in more detail.

Bottom line: Verify, suppress, hold back Risky addresses, send a canary batch, and keep re-verifying.

Do the sources of cold lists change the bounce rate?

Yes, often a great deal. How a list was built predicts its bounce rate better than most senders expect, so source matters as much as the verification step.

Enrichment databases label many emails as "verified" or "guessed," and those labels reflect each vendor's own process. A guessed address built from a name and company pattern can be correct, but it has not been confirmed. Our breakdown of Apollo's verified and guessed statuses explains what those labels mean, and how to verify Apollo lists before sending shows how to check them. A vendor label is a starting point, not a substitute for verification.

Teams that buy B2B lists face this most, and email verification for ecommerce and SaaS covers the patterns that repeat across those businesses. For comparisons of sourcing tools, see our roundup of best email finders for B2B prospecting.

The practical habit is to split bounce data by source after every campaign. If one source consistently bounces higher, verify it more strictly or stop buying from it.

Bottom line: Track bounce rate by source, because one weak data source can sink an otherwise clean campaign.

What should you do when bounce rate goes above 2%?

Stop sending to the affected segment immediately, then work through the cause before resuming. Each extra send to a bad list adds to the damage.

  1. Pause the sequence for the segment that crossed 2%. Leave other segments running only if their rates are below target.
  2. Export the bounced addresses and suppress every 5.1.x hard bounce across all campaigns, not only the current one.
  3. Split the bounces by code. If most are 5.7.x, check SPF, DKIM and DMARC, then review your domain's blocklist status. Unlimited Verifier offers a free domain blacklist checker for that step.
  4. Find the source. If the bounces cluster in one list, verify that list in full before you send to it again.
  5. Resume with a canary batch and a tighter ceiling for the next three days.

If your problem sits inside a sequencer's settings, for example follow-ups reaching addresses that already bounced, our guide on fixing a high bounce rate in Smartlead walks through those checks.

Bottom line: Pause the segment, suppress hard bounces everywhere, diagnose by code and source, then restart with a canary batch.

Hands-on tutorial: verify a cold list before you send

This walkthrough uses Unlimited Verifier. You can follow the same steps with any bulk verifier that sorts results into Valid, Risky and Invalid.

  1. Export your prospect list as a CSV. Include the email column and a source column if you have one. The source column lets you split bounce results later.
  2. Create an account. You can sign up and test the process on a small list before choosing a plan.
  3. Upload the file. Use upload and verify a list. CSV and Excel files up to 10MB are accepted, and the email column is detected automatically.
  4. Let the checks run. Each address is checked for syntax, domain, MX records and the SMTP mailbox. Catch-all domains are detected, and disposable and role-based addresses are flagged.
  5. Read the three buckets.
    • Valid: send these in your first wave.
    • Invalid: suppress permanently.
    • Risky: hold back. Catch-all results are explained on the catch-all email verification page.
  6. Export your results as CSV, Excel or JSON. On the Free plan, results are kept for 24 hours, so download them the same day. On Pro, they are kept for 30 days.
  7. Re-import only Valid contacts into your sequencer as a new list. Unlimited Verifier has no native integrations with sequencing tools, so this is a manual export and re-import, or an API call from your own script. If your sequencer is Instantly, our guide on verifying Instantly leads before launching covers that workflow.
  8. Suppress Invalid addresses in your sequencer's suppression list so they are never contacted again.
  9. Check individual cases. For a single high-value contact that came back Risky, run it through the free single-address checker.

Bottom line: Export with a source column, verify, send Valid addresses only, suppress Invalid ones, and hold Risky ones back.

Worked example: cleaning an 18,400-row prospect list

This example is illustrative. The plan limits and arithmetic are real, and the verification outcomes are hypothetical.

Scenario: A B2B team has 18,400 prospects from three sources and plans one campaign to all of them. It wants to know what bounce rate to expect.

Step 1: Estimate the risk before verifying. Suppose the purchased segment carries most of the risk and a hypothetical 7.6% of all rows are Invalid. Sending unverified would produce:

18,400 × 7.6% = 1,398 bounces ≈ 7.6%

That is nearly four times the 2% ceiling in a single send.

Step 2: Choose a plan. The Pro plan allows lists of up to 25,000 emails, so 18,400 rows fit in one list. Standard verification is unlimited on every plan with no per-email fees, and Pro includes 25,000 deep verifications a month. If you use the whole deep quota, Pro works out to:

$29 ÷ 25 thousand-verification blocks = $1.16 per 1,000 deep verifications

Check current email verification pricing on the plan page before you buy, since prices can change.

Step 3: Verify and sort. Assume these hypothetical outcomes:

Check the total: 13,100 + 3,900 + 1,400 = 18,400.

Step 4: Plan the send. Run deep verification on the 9,600 rows from the purchased source. That uses 9,600 of the 25,000 monthly deep quota and leaves 15,400 for re-checks. Send to the 13,100 Valid addresses first. If the residual bounce rate on that segment is a hypothetical 0.6%:

13,100 × 0.6% = 79 bounces ≈ 0.6%

That is under the 1% target. Hold the 3,900 Risky addresses until the main send stays clean, and suppress the 1,400 Invalid addresses.

Result: Instead of an expected 7.6% bounce rate, the planned send lands near 0.6%, at the cost of one month of Pro at $29.

Bottom line: Verifying first turned an expected 7.6% bounce rate into a planned 0.6%, for one month of Pro.

Which Unlimited Verifier plan fits your cold email volume?

Choose a plan by how many addresses you verify each month, how large each list is, and whether you need API access. For a broader comparison of options, see our guide to the best email verification tools and our checklist on how to choose an email verifier.

Your situation Plan that fits Why
Testing the process on small lists Free Up to 25 lists a month of 150 emails each, plus 750 deep verifications; results kept 24 hours
Recurring prospect batches up to 25,000 rows Pro Unlimited lists of up to 25,000 emails each, 25,000 deep verifications a month, results kept 30 days
Verifying at signup or inside your own tools Pro with API 100,000 API emails a month, with bulk batches of up to 10,000 emails per request

The Free plan's list limit is worth checking before you start. A 600-row list needs:

600 ÷ 150 = 4 lists, which uses 4 of your 25 monthly lists

The company states 99.5% accuracy for deep verification. That is Unlimited Verifier's own figure, not an independent benchmark. If you verify inside your own product or CRM, the email verification API covers single checks and bulk requests, and our real-time email validation guide explains the signup pattern. For the wider workflow, see email verification API and automation.

Bottom line: Free suits testing, Pro suits recurring prospect batches, and Pro with API suits teams that verify inside their own tools.

Do cold email tools with built-in verification solve the problem?

Built-in verification can help, but it does not replace a separate check on the source list. What matters is when the tool verifies, and what it does with the results.

Check three things. Does it verify before sending, or only after a bounce? Does it suppress hard bounces across all campaigns? Can you export bounce data by source? Our review of best cold email tools with built-in verification covers these differences. If a built-in step is opaque, many teams run an independent verifier on the source list first.

Bottom line: Built-in checks only help if they run before sending, suppress across campaigns and export bounce data by source.

What about compliance for cold email?

Verification keeps your list clean, but it does not give you permission to email anyone. Compliance depends on how you send, not only on who you send to. This is general information, not legal advice.

In the United States, the FTC's CAN-SPAM compliance guide requires accurate headers, a clear sender identity, a valid postal address and a working opt-out. Opt-out requests must be honoured within 10 business days. In the UK, the ICO guidance on electronic marketing treats corporate subscribers differently from individual subscribers, so a generic role address and a named individual's work address can follow different rules. Check the rules that apply in each market you email.

Verification confirms that an address is deliverable. It does not show the person agreed to be contacted. Keep a record of your lawful basis for each segment, and read more on email verification compliance and hygiene.

Bottom line: Verification controls bounces, while compliance depends on your lawful basis and how quickly you honour opt-outs.

Common mistakes that push bounce rate over 2%

Bottom line: Most high bounce rates come from miscounting the denominator, mixing up bounce types, or sending before a verification pass.

How we compared (and limitations)

This article is based on public documentation: RFC 3463 for enhanced status codes, Google and Yahoo sender guidelines, Amazon SES's published thresholds, and the FTC and ICO guidance on electronic marketing. We have not run controlled tests against any mailbox provider or sending platform, and we have not independently benchmarked any verifier's accuracy.

Thresholds vary by provider and change over time, so treat 2% and 1% as planning numbers, not guarantees. Worked-example outcomes are hypothetical. Unlimited Verifier's plan limits and its 99.5% deep-verification accuracy are the company's own stated figures.

Bottom line: Use the 2% ceiling and 1% target as planning numbers, then check them against your own bounce data.

Bounce rate ceilings by sending situation

Situation Hard-bounce ceiling Target
New sending domain, first ~200 sends 1% under 0.5%
Warmed domain, verified list 2% under 1%
Scraped or purchased list, unverified Do not send n/a
Re-engaging an older list 2% under 1%

Frequently asked questions

What is a good bounce rate for cold email?

A good cold email bounce rate is under 1% hard bounces, and you should never exceed 2% per campaign. Staying under 1% gives you room for normal list decay and protects your sender reputation with mailbox providers.

What counts as a hard bounce?

A hard bounce is a permanent delivery failure, usually an SMTP 5.x.x code such as 5.1.1, meaning the address does not exist or the domain rejects mail. Soft bounces, like a full inbox or temporary server issue, are usually retried and should not be counted toward your hard-bounce rate.

How do you calculate cold email bounce rate?

Divide the number of hard bounces by the number of unique addresses you attempted to send to, then multiply by 100. For example, 14 hard bounces out of 1,000 unique addresses is a 1.4% bounce rate.

What should I do if my bounce rate goes above 2%?

Pause sending, stop the campaign, and investigate the list source. Re-verify the remaining addresses, suppress all Invalid results, and hold back Risky addresses until you have confirmed a cleaner list before resuming.

Why is the cold email bounce limit lower than for newsletters?

Cold recipients never opted in, so they have no prior engagement to offset bad addresses or complaints. Mailbox providers also scrutinize unsolicited senders more closely, which leaves less margin for error.

Do soft bounces count toward my cold email bounce rate?

Most teams track soft bounces separately from hard bounces. Hard bounces drive list-quality decisions, while repeated soft bounces from the same address often convert to hard bounces and should then be suppressed.

Should I verify emails before a cold email campaign?

Yes. Verify addresses before sending, send only Valid addresses first, hold Risky ones back, and suppress Invalid ones. Verification is the main way to keep hard bounces under the target before the first send.

Is the bounce rate limit the same for every sending domain?

No. A new sending domain with no positive history should use a tighter ceiling, such as 1% during the first few hundred sends, while an established, warmed domain with a verified list can tolerate closer to 2%.

Do Amazon SES and Google thresholds apply to cold email?

Those published thresholds were written for general bulk sending and shared systems, not unsolicited outreach. Cold senders should use a stricter working ceiling, since they have less reputation buffer than permission-based senders.

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 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.