Article
How to Calculate Email Bounce Rate: Formula, Examples, and Benchmarks
By Unlimited Verifier Team ·

Summary
Email bounce rate is the percentage of attempted sends that receiving servers rejected, calculated as (hard bounces + soft bounces) divided by emails sent, multiplied by 100. For example, 1,056 bounces from 48,000 sends equals a 2.2% bounce rate. Reporting hard and soft bounces separately helps diagnose whether the problem is your list or a specific provider.Email bounce rate is the percentage of your attempted sends that a receiving mail server rejected, calculated as bounced emails divided by emails sent, then multiplied by 100. A campaign with 1,056 bounces from 48,000 sends has a 2.2% bounce rate.
The formula is simple. Most wrong numbers come from three input decisions: which bounces to count, what to divide by, and how to combine campaigns. This guide works through each decision with arithmetic, then covers how to forecast bounce rate before you send and how to calculate it in a spreadsheet. For the wider context, start with our email marketing benchmarks pillar.
Quick answer
- Formula: Bounce rate = (hard bounces + soft bounces) ÷ emails sent × 100.
- Count the right bounces: Include permanent failures (SMTP codes starting with 5) and soft bounces that keep recurring. Track policy rejections, often coded 5.7.x, in their own bucket.
- Pick the right denominator: Divide by emails attempted, not delivered or total list size. Track suppressed addresses separately.
- Combine campaigns correctly: Divide total bounces by total sends. Never average percentages.
- Set your target: Keep total bounces under 2%, aiming for under 1% on engaged lists. Forecast the rate with verification before you send.
What is email bounce rate, and what does the formula actually measure?
Bounce rate measures the share of send attempts that came back as undeliverable. A bounce is reported in a delivery status notification (DSN), a message format defined in RFC 3464, which a receiving server or relay generates after it rejects your message.
Bounce rate and delivery rate are complements. Delivered plus bounced equals attempted, so the two always total 100%. Our guide on how to calculate email delivery rate covers that side in detail.
Track three numbers for every send:
| Metric | Formula | Example (48,000 sent; 720 hard; 336 soft) |
|---|---|---|
| Total bounce rate | (hard + soft) ÷ sent × 100 | 1,056 ÷ 48,000 = 2.2% |
| Hard bounce rate | hard ÷ sent × 100 | 720 ÷ 48,000 = 1.5% |
| Soft bounce rate | soft ÷ sent × 100 | 336 ÷ 48,000 = 0.7% |
| Delivery rate | (sent − bounced) ÷ sent × 100 | 46,944 ÷ 48,000 = 97.8% |
The split matters because the two types point at different problems. A high hard rate means addresses on your list don't exist, so the list needs cleaning. A high soft rate concentrated on one email domain often points to that provider's server, or to a full-mailbox pattern, rather than to your list as a whole. The hard and soft rates must sum to the total. If they don't, a category is missing from your export.
Bottom line: Bounce rate is bounces divided by attempted sends. Always report the hard and soft components alongside the total, because they diagnose different problems.
Which bounces should you count?
Count every permanent failure and any soft bounce that repeats. The category depends on the enhanced status code the receiving server returns, defined in RFC 3463. The first digit matters most: 4.x.x is a temporary failure and 5.x.x is a permanent one.
| Example code | Class | Typical meaning | How to count it |
|---|---|---|---|
| 5.1.1 | Permanent | Mailbox doesn't exist | Hard bounce |
| 5.1.2 | Permanent | Destination host or domain not found | Hard bounce |
| 4.2.2 | Temporary | Mailbox full | Soft bounce |
| 5.7.1 | Permanent, policy | Message refused by policy or reputation | Separate policy bucket |
The DSN also carries an Action field. A value of "failed" means the server gave up, and "delayed" means it will retry. Use that field to separate final failures from messages still in the retry queue.
Soft bounces are where calculations diverge. A common working rule is to treat an address as a list problem once it soft-bounces on three separate sends. One full mailbox is not a dead address, but the same address failing on three sends in a row almost always is.
The 5.7.x codes are the grey zone. They usually mean your mail was refused for authentication, reputation or policy reasons, not because the address is dead. Some platforms file them under hard bounces anyway, which mixes a sender problem into a list-quality number. If a 5.7.1 spike arrives with a clean list, check your SPF, DKIM and DMARC setup and your sending reputation first. Our deliverability metrics every sender should track guide covers those checks.
Some platforms also report "blocked" or "deferred" events separately from bounces. Leaving them out of your numerator makes the rate look better than it is, so note which definition your platform uses.
Bottom line: Count permanent failures and repeated soft bounces. Keep policy rejections in their own bucket so they don't distort your reading of list quality.
How do you calculate email bounce rate step by step?
Take one campaign's sent count, hard bounces and soft bounces from the same export, add the two bounce counts, divide by sent, multiply by 100 and round to one decimal place. The sections below explain why each input has to be handled carefully.
Three common methods exist, and they suit different jobs:
| Method | Best for | Main risk |
|---|---|---|
| Spreadsheet from an ESP export | Per-campaign diagnosis and custom weighting | Manual errors when exports come from different dates |
| ESP dashboard figure | A quick check on one campaign | Definitions and suppression handling vary by platform |
| Pre-send verification forecast | Deciding which addresses to send to before a campaign | Predicts bounces; it doesn't guarantee them |
Run these steps on every campaign:
- Pull all counts from one send. Take attempted sends, hard bounces and soft bounces from the same export or log. Mixing reports from different dates is the most common source of wrong rates.
- Confirm what "sent" means. Check whether your platform counts addresses it suppressed before sending. The denominator section below explains why this changes the answer.
- Deduplicate within the send. Each address should count once per campaign. Duplicate rows inflate both the bounce count and the send count, and they distort the rate.
- Add hard and soft bounces. Keep policy rejections out of the sum unless your platform counts them as bounces and you state that in your report.
- Divide by sent, multiply by 100, round to one decimal. Round consistently across reports so numbers compare cleanly.
- Read the result after a fixed window. Most bounce notifications arrive within minutes or hours, but deferred messages can be retried for days before a server gives up. A 24-hour read can understate the final rate. We recommend a 72-hour window for the headline number, and writing that window into every report.
Bottom line: Calculate from one consistent set of counts, read the result after a fixed window, and write down the definitions you used so the number can be compared later.
Which denominator should you use: sent, delivered, or list size?
Use emails attempted (sent) as the denominator. Each alternative answers a different question, and confusing them is the most common calculation error.
| Denominator | Good for | Problem |
|---|---|---|
| Emails attempted (sent) | The campaign bounce rate, which is the figure most ESP thresholds refer to | Depends on whether suppressed addresses are counted |
| Delivered | Nothing useful for bounce rate; it belongs in delivery rate | Delivered already excludes the bounces, so bounces ÷ delivered overstates the rate |
| Total list size | Measuring what share of your database is failing | Includes addresses you didn't mail, so it understates the campaign rate |
| Unique addresses attempted | Cumulative list health across campaigns | Needs deduplication and your own send log |
The suppression trap is the subtle one. Most platforms automatically stop sending to addresses that bounced earlier. Those addresses never count as attempted sends, so a campaign can look clean while a large pool of failed addresses sits on your list.
Here is an example. A list of 51,000 contains 3,000 addresses suppressed after earlier bounces. The campaign attempts 48,000 and gets 1,056 bounces.
- Bounce rate on attempted sends: 1,056 ÷ 48,000 = 2.2%
- Bounce rate if you divided by the full list: 1,056 ÷ 51,000 = 2.1%
- Suppression pool: 3,000 ÷ 51,000 = 5.9% of the list has already failed
Report 2.2% as the campaign rate, since that is the figure ESPs use. Report the 5.9% separately as your list-health signal. A growing pool usually means the list is decaying faster than you clean it. Ecommerce and SaaS teams with heavy sign-up traffic often see this pool grow quickly, which is covered in email verification for ecommerce and SaaS. To read pool growth against normal list growth, see our average email list growth rate article.
Bottom line: Divide by attempted sends for the campaign rate, and track the suppression pool separately so a clean-looking campaign doesn't hide a decaying list.
How do you calculate bounce rate across multiple campaigns?
Divide total bounces by total attempted sends. Averaging the campaign percentages gives the wrong answer because it gives a 1,000-address send the same weight as a 100,000-address send.
Two campaigns show the difference:
- Campaign A: 10,000 sent, 50 bounced = 0.5%
- Campaign B: 1,000 sent, 40 bounced = 4.0%
The simple average is (0.5 + 4.0) ÷ 2 = 2.25%, which is wrong. The correct weighted rate is (50 + 40) ÷ (10,000 + 1,000) = 90 ÷ 11,000 = 0.82%.
Weighted totals answer "what share of all our mail bounced?" Per-campaign and per-segment rates answer "where is the problem?" Segmenting is where the real diagnosis happens. Consider a send of 50,000 addresses split into two sources:
- Organic sign-ups: 40,000 sent, 120 bounced = 0.3%
- Imported leads: 10,000 sent, 600 bounced = 6.0%
- Overall: 720 ÷ 50,000 = 1.44%
The overall figure looks acceptable, but the imported segment is six times the ceiling. Without the split, the team would miss the cause. Our list maintenance best practices guide covers how to schedule cleaning for imports like this.
If you need a list-level rate across many sends, deduplicate addresses first. An address that bounced in January and again in March is one failed address on the list, not two. Label any approximation as one when you don't have a complete send log.
Bottom line: Use weighted totals for overall performance, per-segment rates for diagnosis, and never average percentages.
What is a good email bounce rate?
Keep total bounce rate under 2% and aim for under 1%. Sources disagree on the exact threshold, so here is what each one says and why we recommend 2%.
The clearest public figures come from Amazon SES. Its documentation describes a 5% bounce rate as a point where an account is reviewed, and 10% as a level at which sending may be paused. Other providers can act well before those points, especially on a single campaign to an untested list. The SES numbers are therefore the outer limits, not targets.
Our recommended numbers:
- Under 1%: Healthy for engaged lists, and the target for any re-engagement or first send to an older list.
- 2%: Our operational ceiling. Above it, investigate before the next send.
- 5%: Treat as an incident. It matches the public SES review point, and it means the list needs remediation.
We recommend 2% rather than 5% for two reasons. Providers can react before 5%, and a campaign at 2% usually points to a specific problem, such as an old import, that gets worse with each send. Norms also differ by audience. The ecommerce benchmarks and nonprofit benchmarks show how these expectations vary, and the benchmarks by industry for 2026 article covers sector differences.
Bounce rate is not the same metric as complaint rate. Google's sender guidelines ask bulk senders to keep spam rate below 0.10% and never reach 0.30%, and Google Postmaster Tools reports spam rate for Gmail traffic. Don't compare a bounce rate with a complaint threshold. Our spam complaint rate guide covers that side.
Bottom line: Use 2% as your ceiling and 1% as your target. Treat 5% and 10% as the points where ESPs step in, not as goals.
How can you estimate bounce rate before you send?
Verify the list first, then use the Invalid and Risky counts to set a projected bounce band. The lower bound is Invalid ÷ total. The upper bound is (Invalid + Risky) ÷ total.
Verification checks each address in layers. Syntax catches typos and malformed addresses. The domain and MX check confirms the domain exists and accepts mail. The SMTP mailbox check asks the receiving server whether the mailbox exists. Each address is then sorted into a bucket. Dedicated verifiers, the category covered in our best email verification tools roundup, all work this way, though their categories and checks differ.
The Risky bucket needs the most care. Risky addresses are typically the ones the check couldn't confirm, such as addresses on catch-all domains, which accept any recipient, so the mailbox can't be verified. Our catch-all email verification page explains how that case is handled. To spot-check a single address, such as a key account that came back Risky, use the free email checker.
Limits matter here. Verification predicts bounces; it doesn't guarantee them. Results can change if a mailbox is closed after your check, and your ESP's own suppression rules still apply. Unlimited Verifier states 99.5% accuracy for deep verification. That is the company's own figure, not an independent benchmark.
Pricing matters if you forecast often. Unlimited Verifier includes unlimited standard verification on every plan, with no per-email fees. Deep verifications are metered, at 750 a month on Free and 25,000 a month on Pro. Our email verification pricing overview explains how the tiers compare.
Bottom line: Verification turns your list into a projected bounce band. The Invalid count sets the floor, and the Risky count sets the ceiling.
How do you forecast bounce rate for a 25,000-contact list?
Here is a worked example. The counts are hypothetical, but the arithmetic and plan limits are real. A B2B team wants to send to a 25,000-contact list, which is exactly the Pro plan's per-list maximum. Pro costs $29 a month, or $25 a month billed annually.
Verification returns:
- Valid: 22,100
- Risky: 1,900
- Invalid: 1,000
- Check: 22,100 + 1,900 + 1,000 = 25,000 ✓
Projected band for the full list:
- Lower bound: 1,000 ÷ 25,000 = 4.0%
- Upper bound: (1,000 + 1,900) ÷ 25,000 = 11.6%
Sending to the full list would breach the 2% ceiling even at the lower bound, so the decision is clear. The plan is to remove the Invalid addresses and hold back the Risky ones.
Revised plan:
- Suppress the 1,000 Invalid addresses in your ESP.
- Hold the 1,900 Risky addresses out of the first send.
- Send to the 22,100 Valid contacts.
If you added the Risky addresses back, the worst-case rate would be 1,900 ÷ 24,000 = 7.9%, which is why they wait. Once the Valid send is done and its bounce rate is known, you can test a small Risky sample and watch its result before any larger send.
The forecast tells you which addresses to remove and which to hold. The observed rate tells you whether the list is healthy. Suppose 330 of the 22,100 Valid addresses bounce:
- Observed rate: 330 ÷ 22,100 = 1.5%
That is under the 2% ceiling but above the 1% target. Break the 330 bounces down by source and segment before the next send. The cause is usually concentrated, and the next send should exclude it.
Bottom line: The forecast decides who gets mailed, and the post-send calculation confirms whether the list held up.
How do you calculate bounce rate in a spreadsheet?
Export one row per campaign with sent, hard and soft counts, then add three formulas: total bounces, bounce rate and a weighted total. The steps below use Google Sheets or Excel, and assume column B is sent, C is hard bounces and D is soft bounces.
Part A: Calculate a campaign's bounce rate
- Export the campaign report from your ESP as a CSV. Include the campaign name, sent count, hard bounces and soft bounces. Add a suppressed count if your platform provides one, so you can track the suppression pool.
- Open the file in Google Sheets or Excel. Keep one campaign per row, so the formulas can be filled down.
- Add a total bounces column. In cell F2, enter
=C2+D2. - Add a bounce rate column. In G2, enter
=F2/B2and format the cell as a percentage. - Add a hard bounce rate column. In H2, enter
=C2/B2. This separates list decay from total bounces. - Add a weighted total. In a summary row, enter
=SUM(F2:F10)/SUM(B2:B10). This gives the correct overall rate across campaigns, not an average of percentages. - Flag campaigns above your ceiling. In I2, enter
=IF(G2>0.02,"Investigate","OK")and fill down.
Part B: Forecast a list before you send
- Export the list as a CSV with an email column. Free accounts can verify lists of up to 150 emails each, 25 lists a month. Pro accounts can verify lists of up to 25,000 emails each.
- Create an account. Sign up on the Free plan to test the workflow, or choose Pro for larger lists.
- Upload the file. On the upload and verify a list page, CSV and Excel files up to 10MB are accepted, and the email column is detected automatically.
- Run verification and read the counts. You'll get totals for Valid, Risky and Invalid.
- Enter the counts into your sheet. Calculate
=Invalid/Totalfor the lower bound and=(Invalid+Risky)/Totalfor the upper bound. - Export and save the results. Export as CSV, Excel or JSON. Free results are kept for 24 hours and Pro results for 30 days, so save your own copy for records and for your compliance file.
- Re-import only Valid contacts into your ESP. Add Invalid addresses to your suppression list. Unlimited Verifier has no native ESP, CRM or Zapier integrations, so this is a CSV export, verify and re-import workflow, or an API call from your own scripts.
Automating the process: Verification API access is on Pro, and the Free plan does not include it. The verification API accepts single-email checks and batches of up to 10,000 emails per request, and Pro includes 100,000 API emails a month. To check addresses at the point of signup, see our real-time email validation guide. For automation patterns, see API-driven workflows.
Bottom line: The spreadsheet gives you the campaign rate in minutes, and verification gives you the forecast before the send.
What are the most common mistakes when calculating bounce rate?
- Averaging campaign percentages. A 1,000-address send gets the same weight as a 100,000-address send. Use total bounces ÷ total sends.
- Dividing by delivered. Delivered already excludes the bounces, so the result is inflated. Divide by attempted sends.
- Counting only hard bounces. Repeated soft bounces are often the early signal of a list that is about to fail. Count them once they recur.
- Reading the rate too early. A 24-hour read can miss deferred messages still in retry. Use a fixed window, such as 72 hours, and state it.
- Ignoring the suppression pool. A clean campaign rate can hide a growing pool of addresses you've already stopped mailing.
- Treating 5.7.x codes as dead addresses. A spike in policy rejections usually points to authentication or reputation, so check those before you clean the list.
- Mixing definitions across tools. One platform may count suppressed addresses and another may not. Pick one definition and print it on every report.
- Losing the evidence. Free verification results are kept for 24 hours and Pro results for 30 days. Keep your own exports for audits and for any compliance review.
- Treating verification as proof. A Valid result predicts delivery; it doesn't guarantee it. It also doesn't prove consent. Our overview of email verification compliance and hygiene covers what verification does and doesn't establish.
- Comparing bounce rate with complaint rate. They measure different things and have different thresholds. Report them separately.
Bottom line: Most calculation errors come from inconsistent definitions. Write yours down and apply it to every send.
How we compared (and limitations)
This guide is based on public documentation: RFC 3463 for enhanced status codes, RFC 3464 for delivery status notifications, Amazon SES's published documentation, and Google's sender guidelines and Postmaster Tools. We haven't run controlled tests of any ESP's review process, and platforms define bounces differently, so check your own platform's documentation before acting on any threshold.
The 2% ceiling and 1% target are our recommendations, not an industry standard. Thresholds change over time. The worked examples use hypothetical counts. The 99.5% accuracy figure is Unlimited Verifier's own stated number. Plan limits reflect the product's published terms at the time of writing. The verification engine is open source, so you can review its implementation on GitHub.
Bottom line: Use the formulas and definitions here, and check the thresholds against your ESP's documentation before you act on them.
Worked bounce rate calculation
| Metric | Count | Rate |
|---|---|---|
| Emails sent | 48,000 | 100% |
| Hard bounces | 720 | 1.5% |
| Soft bounces | 336 | 0.7% |
| Total bounces | 1,056 | 2.2% |
| Delivered | 46,944 | 97.8% |
Formula: (720 + 336) ÷ 48,000 × 100 = 2.2%
Frequently asked questions
What is a good email bounce rate?
A bounce rate under 2% is the commonly cited target, and under 1% is typical for engaged lists. Rates above 2% usually signal list quality problems or sending infrastructure issues that should be investigated before the next campaign.
What is the difference between a hard bounce and a soft bounce?
A hard bounce is a permanent failure, such as a nonexistent mailbox (SMTP code 5.1.1). A soft bounce is temporary, such as a full mailbox or server outage (code 4.x.x), and only counts toward your rate if it repeats.
Should bounce rate be divided by delivered emails or sent emails?
Divide by emails attempted, not delivered. Bounces are the failed attempts, so using delivered emails as the denominator would overstate the rate. Suppressed addresses should be tracked separately rather than mixed into the denominator.
How do I calculate bounce rate across multiple campaigns?
Add all bounces from every campaign and divide by the total emails sent across those campaigns. Averaging each campaign's percentage gives a distorted result when campaign sizes differ.
What is the difference between bounce rate and delivery rate?
They are complements. Delivery rate is (sent minus bounced) divided by sent, so bounce rate plus delivery rate always equals 100%. Use both together to understand send health.
Do soft bounces count toward bounce rate?
Yes, most senders include soft bounces in total bounce rate, but many email platforms only count a soft bounce after it repeats across several attempts. Check your platform's definition so your numbers are comparable over time.
What does a 5.7.x bounce code mean?
A 5.7.x code is a permanent policy rejection, meaning the receiving server refused the message for reasons such as spam filtering, authentication failure, or sender reputation. Track these separately because they indicate reputation or authentication issues rather than invalid addresses.
How can I forecast bounce rate before sending?
Verify the list with an email verification service before sending, remove invalid and risky addresses, then estimate the bounce rate from the verified invalid share. Verification reduces hard bounces but cannot predict every soft or policy bounce.
Can I calculate bounce rate in a spreadsheet?
Yes. Put sent counts in one column and hard and soft bounces in adjacent columns, then use a formula such as =(B2+C2)/A2 formatted as a percentage. For multiple campaigns, use SUM on the bounce and sent columns before dividing.
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.