Article
Average Email Bounce Rate by Industry: What Good Looks Like
By Unlimited Verifier Team ·

Summary
Most published benchmark reports put typical email bounce rates below 1% of sends, but industry is a weak predictor because list source and address age matter more. For planning, use 2% total bounces as a ceiling and under 1% as the target in any sector.An email bounce rate is the share of sent messages a receiving server refuses to deliver. Most published benchmark reports put the typical rate below 1% of sends, but industry averages are a weak guide because list source and address age explain far more than sector does. For planning, use 2% total bounces as the ceiling and under 1% as the target, in every industry.
Treat published averages with caution. Benchmark reports sample different senders, count bounces differently and rarely publish their full methodology. This guide explains what the numbers mean, shows how to build a benchmark from your own data, and gives you a plan to get under target. For the wider context, start with the email marketing benchmarks pillar.
Quick answer
- Typical bounce rate: most published benchmark reports put it below 1% of sends. Use 2% as your ceiling and 1% as your target.
- List source matters more than industry. A checkout-captured list usually bounces far less than a scraped or imported list in the same sector.
- Calculate per source, not as one blended number. A healthy 0.5% signup list can hide a 6% trade-show import.
- Verify before the first send on any list you didn't capture yourself, and send to Valid addresses first.
- Platform thresholds differ. Amazon SES documentation describes 5% as a review level and 10% as a pause level. Google and Yahoo publish spam-rate expectations around 0.3%, but that is a complaint metric, not a bounce rate.
What is an email bounce rate, and how do you calculate it?
Your bounce rate is the number of bounced emails divided by the number of emails sent, multiplied by 100:
Bounce rate = bounced emails ÷ emails sent × 100
For example, 850 bounces from 42,000 sends gives 850 ÷ 42,000 × 100 = 2.02%.
Two details break most comparisons:
- The denominator. Some reports divide by delivered emails instead of sent. Using the same example, delivered is 41,150, so the rate on delivered is 850 ÷ 41,150 = 2.07%. The gap is small, but it can move you across a threshold. Our guide on how to calculate email delivery rate covers the bases in detail.
- Hard versus soft bounces. A hard bounce is permanent: the mailbox doesn't exist or the domain won't accept mail. The classic example is enhanced status code
5.1.1(bad destination mailbox), defined in RFC 3463. A soft bounce is temporary, such as a full mailbox, a server outage or an oversized message. Blending the two inflates the figure, and hard bounces are the ones that damage sender reputation.
Bottom line: The arithmetic is simple. A benchmark is only comparable to your number if you know whether it uses sent or delivered, and hard or all bounces.
Why does list source matter more than industry?
Industry is a proxy. What actually produces bounces is how an address entered your database and how old it is. Four factors do most of the work:
- Capture method. A customer who types an address at checkout needs the receipt, so the address is usually correct. A badge scan, a business card or a scraped contact has no such feedback loop.
- Age. Addresses decay. Job changes, closed school accounts and abandoned personal mailboxes all become bounces over time. A list untouched for two years can bounce far more than one mailed last month.
- Friction at entry. Forms without verification let typos and throwaway addresses through. Double opt-in forces the subscriber to confirm the address, which filters most errors before the first send.
- Population churn. B2B contacts change employers constantly, and student addresses close after graduation. Those sectors bounce for reasons unrelated to how carefully the sender works.
This explains why two companies in the same sector can post very different numbers. Benchmark reports add their own noise. Many rely on self-reported data, mix transactional and marketing mail, and sometimes publish medians rather than totals. None of that makes them wrong, but an industry average describes a population, not your list.
Bottom line: Ask how each address got into your database and how old it is before you ask what your industry's average is.
What bounce rate is normal for each industry?
No authoritative, universally accepted bounce average exists for each industry. Platform benchmark pages publish figures, but they change from year to year and don't always agree. The table below gives planning bands we recommend, based on list source and age. They are not measured averages. Use them to decide where to verify first, not to judge how you compare.
| Sender type | Typical list source | Main bounce driver | Suggested target |
|---|---|---|---|
| E-commerce | Address typed at checkout | Typos; generally low risk | Under 1% |
| Publishers and newsletters (double opt-in) | Confirmed subscribers | Gradual aging | Under 1% |
| SaaS (self-serve or free trial) | Open signup forms | Disposable and mistyped addresses | Under 1.5%; verify at signup |
| Education and alumni | Student and alumni addresses | School accounts close after graduation | Under 1.5% |
| Nonprofit and donor | Donation forms, older mailing lists | Aging donors, shared family addresses | Under 1.5% |
| Recruiting and staffing | Candidate and job-board contacts | Candidates change jobs quickly | Under 2%; verify before blast |
| B2B sales prospecting | Exported or scraped lead lists | Role churn, guessed address formats | Verify before first send; 2% ceiling |
| Trade shows and events | Badge scans, business cards | Manual entry errors, stale contacts | Verify before first send; 2% ceiling |
Two things stand out. First, risk follows list source. A B2B company running a double opt-in newsletter behaves more like a publisher than like a prospecting team. Second, every row shares the same 2% ceiling. Varying the ceiling by industry tends to excuse weak list practice, while one fixed line keeps attention on the data.
For sales teams, the stakes are higher than a single bounce. Some dead addresses are later recycled into spam traps, which can damage reputation beyond one campaign. The workflow for prospect lists is covered in email verification for sales prospecting. For how the same logic applies to online stores and software companies, see email verification for ecommerce and SaaS.
Bottom line: Use 2% as the ceiling in every industry, and verify first wherever you did not capture the address yourself.
How do you find your own industry benchmark?
Your own benchmark is more useful than any published average. Build it in four steps:
- Export 12 months of campaign data from your ESP, including sent count, hard bounces, soft bounces and the list each campaign went to.
- Tag each list by source: signup form, checkout, import, event, partner, purchased, or legacy migration.
- Calculate the bounce rate per source, not per campaign.
- Compare each source to the 2% ceiling and the target in the table above.
Worked example. A B2B software company sends 116,000 emails in a year across four sources:
| Source | Sent | Bounces | Rate |
|---|---|---|---|
| Website signup (double opt-in) | 48,000 | 240 | 0.50% |
| Newsletter subscribers | 30,000 | 150 | 0.50% |
| Trade-show badge scans | 18,000 | 1,080 | 6.00% |
| Legacy CRM import | 20,000 | 1,000 | 5.00% |
| Total | 116,000 | 2,470 | 2.13% |
The blended 2.13% looks like one manageable problem. Split by source, it becomes two. The two imports produced 2,080 of the 2,470 bounces (84%) from 38,000 of the 116,000 sends (33%). The other 78,000 sends bounced 390 times, or 0.50%.
The fix is targeted: verify the 38,000 import contacts before further campaigns, and leave the healthy sources alone. A blanket clean of the whole database would spend effort where the data is already sound.
Bounces only tell you about list health. For engagement by sector, see average email click-through rate by industry.
Bottom line: Blended rates hide the problem. Calculate per source, then fix the source that is failing.
Which method cuts bounces the most?
No single method covers everything, but the options differ in when they act. The table compares the main choices.
| Method | What it catches | What it misses | Best fit |
|---|---|---|---|
| ESP automatic bounce suppression | Repeat sends to addresses that already hard-bounced | The first bounce itself; reacts after sending | Safety net for every sender |
| Pre-send bulk verification | Invalid syntax, dead domains, missing MX, nonexistent mailboxes, disposable and role addresses | Consent and engagement | Imports, legacy lists, events, bought or scraped data |
| Real-time check at signup (API) | Typos and bad domains at the moment of entry | Valid addresses the person doesn't want mail from | Forms, where developers can add a check |
| Double opt-in | Typos, bots and addresses the person doesn't control | Aging after confirmation; adds signup friction | Newsletters and subscriber lists |
| Sunset policy (remove after inactivity) | Long-dormant addresses likely to be decaying | Recent bad data; a blunt rule | Mature lists, combined with the methods above |
For most senders, the strongest setup combines three things: double opt-in or a real-time check at entry, pre-send verification for any batch from outside, and a sunset rule for aging contacts. Pre-send verification is the most direct way to stop first bounces on data you didn't capture yourself. ESP suppression, by contrast, only stops the second send to an address that already failed.
Unlimited Verifier fits the pre-send and batch row. Each address is checked for syntax, domain, MX records and the SMTP mailbox, and results are sorted into Valid, Risky and Invalid so each group can be handled differently. For signup forms, the Email verification API is available on the Pro plan, and supports single-email checks and bulk batches of up to 10,000 emails per request. For workflow patterns, see email verification API and automation. If you are comparing vendors, the criteria in best email verification tools help you separate tools by how they categorise results rather than by headline price.
Bottom line: Pre-send verification stops the first bounce on imported data. The other methods mainly protect what is already in the list.
How do you set a bounce target for your industry?
Use this seven-step framework:
- Segment by source using the method above.
- Classify each source as low, moderate or high risk, using the planning table.
- Set targets: under 1% for low-risk sources, under 1.5% for moderate, and under 2% for high-risk sources, which should also be verified before first send.
- Verify high-risk sources before their first send, and add a verification or double opt-in gate to new data.
- Watch every send. Investigate when a source reaches 1%, and pause automation if a single campaign passes 2%.
- Review monthly, and re-verify high-risk lists every quarter.
- Keep the counts. If your ESP ever reviews your account, per-source numbers are the evidence reviewers ask for.
Why 1% and 2%? Sources disagree on where the line sits. Amazon SES's documentation describes a 5% bounce rate as a review level and 10% as a pause level, and many ESPs act earlier on a single bad campaign. Google's sender guidelines and Yahoo's sender requirements focus on spam-complaint rates, where 0.3% is the level to avoid, not a bounce metric. We recommend one number pair for every industry: a 1% alert and a 2% hard ceiling. Both sit below every platform trigger above, so you hear about a problem while it is still small. The deliverability metrics every sender should track guide explains how these measures relate.
Bottom line: Set targets per source, alert at 1%, and treat 2% as a hard stop.
How do you verify a high-risk list in Unlimited Verifier?
This is the hands-on process for the step most teams skip.
- Export the list as a CSV from your ESP or CRM. Save each source as its own file with a name that identifies it, such as
tradeshow_2024.csv, so you can trace results back. - Sign up for a free account. The Free plan allows 25 lists a month of up to 150 emails each, plus 750 deep verifications a month. Results are kept for 24 hours, so export them promptly.
- Check the file size against your plan. On Pro, each list can hold up to 25,000 emails, and Pro keeps results for 30 days. Free lists hold 150.
- Upload the file. CSV and Excel files up to 10MB are accepted, and the email column is detected automatically.
- Run 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 in your first sends. Risky addresses, including catch-all and disposable ones, are held back. Invalid addresses are suppressed permanently.
- Export the results as CSV, Excel or JSON, and save the count for each bucket.
- Re-import the Valid contacts into your ESP as a new segment, and add the Invalid addresses to its suppression list. Unlimited Verifier has no native ESP integration, so this export, verify and re-import loop is the workflow.
- Spot-check doubtful individual addresses with the free email checker. For a catch-all domain, see the catch-all email verification page.
Worked example: the cost of cleaning the import. Using the 38,000 import contacts from the earlier example:
- Splitting: 18,000 and 20,000 are each under the Pro cap of 25,000 per list, so no splitting is needed.
- Standard verification of all 38,000 is included, because standard verification is unlimited on every plan.
- Deep verification: Pro includes 25,000 a month. Spend 18,000 on the trade-show list, the highest-risk source, and 7,000 on the CRM list. That leaves 13,000 CRM contacts for the next monthly allowance.
- Cost: one Pro month at $29, or $25 a month billed annually. Our guide to email verification pricing explains how to compare plans.
Hypothetical result for the trade-show list (illustrative, not measured): 15,480 Valid (86%), 1,440 Risky (8%) and 1,080 Invalid (6%). Send to the 15,480 Valid addresses first. Had you mailed all 18,000 unverified, the Invalid group alone would have produced roughly 1,080 bounces. Risky addresses don't always bounce, but a catch-all address can't be confirmed as a working mailbox, so keep it out of early sends.
For comparison, the Free plan's 25 lists of 150 emails cap at 3,750 emails a month. An 18,000-row file would need 120 separate lists, which is why this import needs Pro.
Bottom line: For roughly one month's Pro fee, the import can be split into Valid, Risky and Invalid groups, with counts you can show anyone who asks.
What are the most common mistakes?
- Comparing a blended rate to an industry average. Your overall number may hide one failing source.
- Mixing definitions. Sent and delivered denominators, or hard and soft bounces, can make two identical campaigns look different.
- Treating planning bands as published data. Our bands are recommendations. Your own per-source numbers are the real benchmark.
- Relying on ESP suppression as your cleanup. It stops repeat sends to addresses that already failed. It doesn't remove bad addresses before the first bounce.
- Verifying only new imports. Lists you have mailed for years also age, and a 12-month-old list can carry many dead addresses.
- Ignoring repeated soft bounces. An address that soft-bounces across several sends often behaves like a hard bounce. Suppress it.
- Sending Risky addresses early. A catch-all result means the server accepts every address, so the individual mailbox can't be confirmed.
- Assuming a valid mailbox means consent. Verification supports email verification compliance and hygiene, but it doesn't replace opt-in. The FTC's CAN-SPAM compliance guide sets the US baseline.
- Losing suppression history during a migration. Keep your own copy of unsubscribes, complaints and bounces, because a new platform may not carry them over.
Bottom line: Many bounce problems trace back to measuring the wrong way or sending before verifying, rather than to the industry itself.
How we compared (and limitations)
This article is based on public documentation: Amazon SES's published thresholds, Google's and Yahoo's sender requirements, RFC 3463 for enhanced status codes, and the FTC's CAN-SPAM guidance. We have not run controlled tests of any ESP's review process or of any benchmark report.
- Planning bands in the industry table are recommendations based on list source and age. They are not measured averages.
- Benchmark reports differ in sample, method and definition, so their figures should not be compared directly. Check the denominator and bounce type before comparing.
- Unlimited Verifier plan details come from the company's published facts. Its 99.5% accuracy figure for deep verification is the company's stated figure, not an independent benchmark.
- Worked examples are illustrative. The trade-show verification split is hypothetical, and the arithmetic is shown so you can rerun it with your own numbers.
Bottom line: Measure your own rate per source, and use these bands only to decide where to verify first.
Per-source bounce rate calculation
Blending sources hides problems. Here is a worked example with three sources:
| Source | Sends | Hard + soft bounces | Bounce rate |
|---|---|---|---|
| Checkout signups | 20,000 | 100 | 0.50% |
| Trade-show import | 2,000 | 120 | 6.00% |
| Blended total | 22,000 | 220 | 1.00% |
The blended 1.00% looks on target, but the trade-show import is at 6%, above the 2% ceiling. Fix or remove that source before the next send, then recalculate each source separately.
Frequently asked questions
What is a good email bounce rate?
A good email bounce rate is under 1% of sent emails. Many teams treat 2% total bounces as the ceiling, meaning anything above it should trigger a list review before the next send. These thresholds are planning guides, not universal standards, so compare your figure against your own sources over time.
Does industry really affect email bounce rate?
Industry has a smaller effect than most people expect. The bigger drivers are how addresses were captured and how old they are. A checkout-captured list in one sector often bounces less than a scraped list in another, so segment your data by source before comparing against any industry average.
What is the difference between a hard bounce and a soft bounce?
A hard bounce is a permanent failure, such as a mailbox that does not exist or a domain that will not accept mail. A soft bounce is temporary, such as a full mailbox or a server outage. Hard bounces hurt sender reputation most, so remove those addresses promptly.
Should I count soft bounces in my bounce rate?
Report hard and soft bounces separately, and only compare your figure to benchmarks that use the same definition. Blending them inflates the number and can make a healthy list look problematic. Track hard bounces as your main quality signal.
Is bounce rate calculated on sent or delivered emails?
Bounce rate is usually calculated on sent emails, but some reports divide by delivered emails instead. The result differs slightly, and the gap can push you across a threshold. Always check the denominator before comparing your number to a published benchmark.
Why does my bounce rate spike after importing a list?
Imported lists often include old, incorrect, or role-based addresses that were never confirmed by the person who owns them. Trade-show badges and business cards also lack a confirmation step. Verify imported addresses before the first send and start with the most engaged segment.
How do I lower my email bounce rate?
Use double opt-in or a verified checkout flow, verify addresses before sending, remove hard bounces immediately, and avoid purchased or scraped lists. Re-check lists that have not been mailed in a long time, since address decay causes many bounces.
Do high bounce rates affect deliverability?
Yes, high bounce rates can hurt inbox placement because they signal poor list quality to receiving providers. Sustained bounces can lead to throttling or blocking by some mailbox providers. Keeping bounces low protects your sender reputation as well as your reporting accuracy.
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.