Healthy Email Bounce Rate: Targets, Diagnosis, and Fixes

A healthy email bounce rate tells you that your list is current, your sending setup is sound, and mailbox providers are accepting your messages. It is an early-warning metric, not a complete measure of inbox placement: an email can be accepted by a receiving server and still land in spam.

What is a healthy email bounce rate?

For a permission-based email program that sends to a maintained list, a practical operating target is below 1% total bounces per campaign, with hard bounces below 0.5% wherever possible. Treat 1% to 2% as a warning range that deserves investigation, and treat a sudden rate above 2% as a reason to pause expansion of the affected send until you know why it happened.

Those are operational guardrails, not a universal rule imposed by every inbox provider. Definitions vary between email service providers (ESPs): some reports count all failed deliveries, while others distinguish hard bounces, soft bounces, blocks, deferred messages, and messages rejected before a send is attempted. Compare like with like before comparing campaigns.

The important external constraint is that some sending platforms enforce their own thresholds. Amazon SES, for example, says to keep hard bounce rate below 5%; it may place an account under review at 5% or above and may pause sending at 10% or above. That does not mean 4.9% is healthy. It is an enforcement threshold, not a quality target.

A useful way to interpret your number is:

Use those bands as a starting point, then set stricter internal limits for high-value transactional mail, new domains, newly acquired audiences, or domains that have recently shown filtering problems. A long-running newsletter with confirmed opt-ins should be able to operate well below a 1% total bounce rate. A one-time reactivation campaign to an old list may produce more bounces, but that is a reason to isolate and clean the audience—not to redefine a high rate as healthy.

Email bounce rate: definition and formula

An email bounce occurs when the receiving mail system does not accept or cannot deliver a message to the intended recipient. Your ESP receives a delivery status notification or an SMTP response and records the result in its event data.

The basic calculation is:

Bounce rate = (bounced messages ÷ messages sent) × 100

If you send 12,000 messages and 84 bounce:

(84 ÷ 12,000) × 100 = 0.7%

That 0.7% is only useful once you split it into categories. Suppose 30 of those failures are hard bounces and 54 are soft bounces:

Hard bounce rate = (30 ÷ 12,000) × 100 = 0.25%
Soft bounce rate = (54 ÷ 12,000) × 100 = 0.45%
Total bounce rate = 0.25% + 0.45% = 0.70%

In that example, the overall rate is healthy. Still, the next question is whether the 54 soft bounces came from many unrelated domains, one receiving provider, or a single sending configuration error. A localized spike can matter even when the aggregate percentage looks acceptable.

Do not confuse bounce rate, delivery rate, and inbox placement

These metrics answer different questions:

• Bounce rate: What percentage of attempted messages failed delivery according to the sender’s reporting?
• Delivery rate: Usually, the proportion accepted by receiving mail servers. It is commonly calculated as sent minus bounced, divided by sent.
• Inbox placement: The share of accepted mail that appears in the primary inbox rather than spam, junk, quarantine, or another folder.
• Spam complaint rate: The proportion of recipients who mark a message as spam or junk. Gmail asks bulk senders to keep spam rates reported in Postmaster Tools below 0.3%.

A 99.5% delivery rate is not proof that 99.5% of recipients saw your email in their inbox. Delivery is necessary, but reputation, authentication, relevance, user engagement, and complaints all influence placement.

Hard bounces vs. soft bounces

The single most useful habit in bounce analysis is to separate permanent failures from temporary ones.

Hard bounces: permanent or treat-as-permanent failures

A hard bounce generally means the address cannot receive mail. Common examples include:

• The mailbox does not exist.
• The recipient domain does not exist.
• The address was typed incorrectly.
• The mailbox was disabled after an employee left a company.
• A recipient server returns a permanent rejection for a reason your ESP classifies as non-recoverable.

SMTP replies in the 5xx range are generally permanent failures. For example, a reply resembling 550 5.1.1 user unknown normally indicates a nonexistent mailbox. Do not repeatedly resend to a confirmed hard-bounced address. Suppress it from promotional sends immediately and retain the suppression record so it is not accidentally re-imported later.

A hard bounce can occasionally be misleading. A recipient server may issue a permanent-looking rejection because of an authentication failure, a reputation block, an IP policy, or a content-security decision. That is why you should read the actual SMTP diagnostic and examine whether many bounces share the same domain and message. If 200 different addresses at one provider all return the same 5xx policy error, the problem may be your sending setup rather than 200 invalid recipients.

Soft bounces: temporary or retryable failures

A soft bounce is usually a temporary delivery failure. Typical causes include:

• A recipient mailbox is full.
• The recipient server is temporarily unavailable.
• The receiving provider is rate-limiting or deferring traffic.
• A message is too large for the recipient system.
• A transient DNS, network, or TLS problem interrupts delivery.

SMTP 4xx replies generally signal temporary conditions. A response such as 421 or 451 often means the sender may retry later. Most established ESPs retry temporary failures automatically according to their own schedules, so do not create a second manual resend workflow until you understand what your platform already does.

The distinction is not absolute. Mailchimp notes that some receiving servers do not return properly formatted standard SMTP replies, forcing ESPs to infer a category. Vendor-specific classification rules can also change. For reporting, use your ESP’s categories consistently, but preserve raw event data or diagnostic text when possible.

Blocks and deferrals deserve their own view

Do not bury policy blocks inside soft bounces. A recipient provider can defer or reject a message because of weak domain reputation, an unaligned sender identity, excessive volume, missing authentication, an IP listing, or suspicious content. Those failures are not proof that the recipient address is bad.

Create a reporting category called provider blocks/deferrals when your ESP exposes the data. A 0.4% total bounce rate composed mostly of isolated nonexistent mailboxes is very different from a 0.4% rate caused by one major mailbox provider deferring your entire campaign.

Why bounce rates affect deliverability

Mailbox providers use many signals to decide whether to accept, filter, or block mail. A high hard-bounce rate signals that a sender may be using stale, scraped, purchased, or poorly managed addresses. Amazon SES explicitly describes high bounce rates as a sign that a sender may not be managing its recipient list properly.

Repeated bounces can damage sending reputation at several levels:

1. Domain reputation: The reputation associated with the domain recipients see in the visible From address and authenticated mail stream.
2. IP reputation: Especially relevant for dedicated IPs or self-hosted mail infrastructure.
3. ESP account reputation: Shared sending providers protect their networks and may warn, review, throttle, or suspend accounts with harmful metrics.
4. Campaign and audience reputation: A sudden jump after a new lead source, migration, or reactivation effort can influence how future messages are treated.

Bounces also waste your best opportunity to establish positive engagement. If a new sending domain begins by mailing thousands of unverified addresses, it creates negative signals before real subscribers have a chance to open, click, reply, or move messages to the inbox.

This is why a healthy email bounce rate is a list-quality metric as much as a technical metric. Authentication will not make nonexistent mailboxes valid, and list cleaning alone will not fix a broken SPF, DKIM, or DMARC configuration.

How to calculate and monitor your healthy email bounce rate

Track the metric at more than one level. A monthly account-wide average can conceal a disastrous new campaign, while a campaign-level percentage can exaggerate a tiny sample. For example, two hard bounces from a 50-person B2B test is 4%, but it may not demonstrate a system-wide reputation problem.

Build a minimum bounce dashboard

For every campaign, automation, and transactional stream, retain these fields:

Review the dashboard after each large send and at least weekly for automated programs. Compare the current campaign with its own baseline: the same audience type, the same acquisition channel, and similar volume. A 0.8% bounce rate may be normal for a long-running B2B list with natural employee turnover, while a jump from 0.15% to 0.8% in one send is a material regression.

Segment before deciding what to fix

Start with four cuts of the data:

1. Hard versus soft. Permanent failures require suppression; temporary failures require a cause assessment.
2. By recipient domain. A spike concentrated at one provider points toward provider-specific policy, reputation, throttling, or authentication issues.
3. By contact source and age. Old imports, webinar exports, gated-content lists, CRM syncs, and third-party data often behave differently.
4. By sending stream. Transactional mail and promotional mail should not be mixed. A password-reset system should not inherit the reputation damage from a poorly targeted newsletter.

This segmentation is how you prevent a bad source from contaminating a good list. Do not respond to one bad imported segment by mailing less frequently to your confirmed, engaged subscribers.

The most common causes of a high bounce rate

Stale contacts and one-time imports

Email addresses decay as people change jobs, abandon inboxes, or organizations close domains. A list can be permission-based when collected and still become stale if you do not email it for a long time. Mailchimp specifically warns that old or invalid addresses can drive bounces, complaints, and unsubscribes, and recommends reconfirming stale contacts.

A high-bounce campaign often follows one of these events:

• Importing an old CRM export without checking consent status or engagement.
• Restarting a newsletter after a long inactive period.
• Combining multiple historical lists after an acquisition or migration.
• Sending to leads collected through a low-intent giveaway or event.
• Uploading addresses supplied by a partner, agency, or data broker.

The remedy is not to keep retrying the full list. Isolate the source, suppress known failures, and send a small, clearly permission-based reconfirmation campaign to the remaining dormant contacts. Remove or archive people who do not reconfirm rather than treating silence as renewed consent.

Form errors, bots, and bad integrations

A typo at acquisition becomes a hard bounce at send time. Watch for common domain misspellings, invisible whitespace, malformed addresses, duplicate records, and API field mapping errors. An integration that copies email_work into a personal-email field or imports blank values as placeholders can create a sharp failure spike overnight.

Use client-side validation for basic formatting, but do not rely on it as your only control. Server-side validation, confirmation emails, bot protection, and double opt-in provide stronger evidence that a person controls the submitted address.

Buying, renting, scraping, or appending lists

Purchased and scraped lists are high-risk even when a vendor claims they are verified. A mailbox can be technically deliverable while its owner never asked to hear from you, creating spam complaints instead of bounces. Purchased data can also include old addresses and spam traps.

Never use a low bounce rate as permission to mail a list that lacks consent. The goal is not simply server acceptance; it is wanted mail delivered to an engaged recipient.

Technical identity and authentication failures

Large mailbox providers require authentication and make it a core part of deliverability. Gmail requires all senders to use SPF or DKIM, while senders that send more than 5,000 messages per day to Gmail accounts must use SPF, DKIM, and DMARC. Gmail also requires one-click unsubscribe for applicable marketing and subscribed mail at that volume.

Authentication failures can appear as bounces, blocks, spam placement, or reduced delivery depending on the recipient provider. Check the real sending path—not just what appears in a DNS dashboard. Your visible From: domain, envelope sender/return-path domain, DKIM signing domain, and ESP configuration must work together.

New infrastructure or a sudden volume increase

A new domain, new dedicated IP, or new ESP does not have established reputation. Sending a large blast immediately after a migration can trigger deferrals or filtering even if your addresses are valid. Postmark recommends gradually increasing volume when warming a domain and reducing volume if bounce or engagement behavior suggests deliverability is suffering.

Start with subscribers most likely to engage, increase volume gradually, and watch provider-level results. Do not use a warm-up process as a workaround for an unpermissioned list; gradual sending cannot turn bad data into a healthy audience.

Fixing a high bounce rate: a practical recovery plan

When a campaign exceeds your normal bounce rate, act in the correct order. The first priority is to stop adding harm, not to find a clever way to resend every failed message.

Step 1: Pause the affected expansion, not necessarily all email

Stop scheduled sends to the suspected segment, source, or recipient domain group. Keep critical transactional mail running if it uses a clean, separate stream and is performing normally.

If the issue affects every stream and every recipient domain, pause broad sends until you verify your ESP account, DNS, authentication, and sending configuration. If it affects only one imported list, do not punish your healthy subscribers by shutting down the whole program.

Step 2: Suppress confirmed hard bounces

Add permanently failed addresses to a centralized suppression list. The suppression list must survive CSV imports, CRM syncs, platform migrations, and manual uploads. Removing an address from a marketing audience without retaining a suppression record invites the same bad address back later.

Do not automatically suppress every recipient based on one ambiguous provider policy block. Confirm whether the error identifies a nonexistent mailbox or a sender-side problem. Keep the raw diagnostic, timestamp, ESP message ID, and recipient-domain grouping for review.

Step 3: Read the actual error pattern

Look for repeated response text and enhanced SMTP status codes. A few examples of how to reason about results:

• 5.1.1 across unrelated domains: likely invalid or nonexistent recipient addresses.
• 5.1.1 only at one corporate domain: investigate whether the organization changed its domain, directory, or mail gateway.
• 4.2.2: often mailbox storage or temporary recipient-side capacity issue; let the ESP retry according to its policy.
• 4.7.0, 421, or 451 clustered at one provider: possible throttling, reputation, rate, or policy issue.
• Authentication-related messages: check SPF, DKIM, DMARC alignment, reverse DNS, TLS, and the ESP’s sending-domain configuration.

Do not treat codes as a universal dictionary. SMTP text and classification vary by receiver, and an ESP may normalize events differently. The pattern across many events is more valuable than one code in isolation.

Step 4: Trace failures to acquisition source

For hard bounces, calculate the rate by signup form, lead magnet, CRM owner, import file, event, partner, and date added. If contacts from a single source produce 3% hard bounces while the rest of the database produces 0.2%, stop ingesting that source until you fix it.

This is where a source-of-truth contact model matters. Store fields such as source, source_date, consent_timestamp, consent_method, last_engaged_at, and verification_status. Without those fields, teams blame email copy or the ESP when the real issue is invisible lead provenance.

Step 5: Repair authentication and sender identity

At a minimum, confirm that your sending domain has the records and vendor configuration your ESP specifies. A simplified example for example.com might look like this:

example.com. TXT "v=spf1 include:spf.your-esp.example -all"
selector1._domainkey.example.com. CNAME selector1.example-com.dkim.your-esp.example.
_dmarc.example.com. TXT "v=DMARC1; p=none; rua=mailto:dmarc-reports@example.com"

Do not copy the SPF include value or DKIM hostname from that example. Your ESP provides vendor-specific values, selectors, and DNS targets. SPF has a limit on DNS-mechanism lookups, so adding every SaaS platform blindly can break authorization rather than improve it.

The DMARC record above begins in monitoring mode with p=none. That lets you receive aggregate reports and inventory legitimate mail streams before moving toward enforcement. DMARC is defined by RFC 9989, which describes how domain owners publish handling preferences and request reporting. Move to p=quarantine or p=reject only after confirming every legitimate sender—including support tools, CRM systems, invoice platforms, and HR software—is authenticated and aligned.

Step 6: Rebuild sending volume carefully

After cleanup, resume with the most engaged and recently confirmed contacts. Keep campaign frequency predictable, use a recognizable From name and domain, and include a visible unsubscribe link. Yahoo’s sender guidance similarly emphasizes sending timely, relevant messages to an active, engaged audience and supporting easy opt-out.

Monitor hard bounces, soft bounces, complaints, and provider-level deferrals after each increment. If the rate improves only when volume is tiny and worsens as you scale, investigate volume ramping and reputation. If it remains high even in a small highly engaged segment, investigate technical configuration or incorrect event classification.

Worked example: diagnosing a 3.4% bounce campaign

Imagine a SaaS company sends a product webinar follow-up to 10,000 contacts. The ESP reports 340 bounces, or 3.4% total. The team should not declare the list unhealthy based on the total alone; it should split the result.

The event export shows:

Next, the marketer groups the 250 hard bounces by source:

The diagnosis is clear: the old spreadsheet created the problem. The correct response is to suppress the 200 hard-bounced addresses, stop mailing the remaining unverified event-export contacts, and consider a narrowly targeted reconfirmation attempt only where prior permission can be demonstrated. The company should not resend the webinar email to every bounce.

The 90 soft bounces are then grouped by recipient domain. If 70 came from one mailbox provider with temporary 421 responses, the ESP’s retry behavior and sending volume should be reviewed. If they are dispersed and resolve on retry, they may be ordinary transient events. If they persist across several sends, treat them as a developing deliverability problem.

The company can define success for its next campaign as follows:

• Hard bounce rate returns below its 0.5% operating target.
• Total bounce rate returns below 1%.
• No single contact source exceeds the threshold.
• The old event spreadsheet is tagged, quarantined, or removed from routine marketing sends.
• Authentication passes in test headers, and no provider-specific block pattern appears.
• Complaint rate and unsubscribes do not rise as the company resumes sending.

That is a recovery plan based on evidence, rather than a superficial attempt to improve a dashboard percentage.

Tools and checks that make bounce management easier

Your ESP is the first place to look because it has message-level events. Platforms such as Mailchimp, HubSpot, Klaviyo, Brevo, Twilio SendGrid, Amazon SES, Postmark, and Customer.io use different names and interfaces, but look for delivery events, bounce classifications, SMTP responses, recipient-domain breakdowns, suppression controls, and webhooks or exports.

For deeper monitoring:

• Google Postmaster Tools: Provides eligible Gmail senders with data about spam rate, domain and IP reputation, authentication, and delivery errors.
• DMARC reporting tools: Parse aggregate XML reports so you can see all systems sending mail on behalf of your domain. Many commercial and open-source parsers exist; choose one that lets you identify unauthorized senders and alignment failures.
• Email validation at intake: Use formatting checks, DNS/MX checks, confirmation flows, and bot controls. Third-party validation services can be useful as a secondary screen, but no validator can guarantee continued mailbox ownership or recipient consent.
• ESP webhooks or event exports: Send bounce events into your CRM, data warehouse, or customer-data platform so suppression and source analysis happen automatically.
• Seed testing and inbox-placement tools: Useful for examining placement, but not a replacement for real recipient engagement data.

The best tool stack does not eliminate bounces. It makes it possible to identify whether a failure came from address quality, acquisition process, recipient infrastructure, authentication, reputation, or a vendor configuration change.

Healthy bounce-rate practices to build into your program

A sustainable email program prevents bad data from entering and keeps old data from quietly degrading. Put these controls into routine operations:

1. Collect clear permission. Document what people signed up for, when, and through which form or workflow.
2. Use double opt-in where list quality matters most. It adds friction, but it confirms address ownership and reduces typo and bot-driven signups.
3. Authenticate every sending domain. Set up the SPF, DKIM, and DMARC configuration required by your ESP and mailbox-provider requirements.
4. Separate transactional and promotional streams. Use distinct subdomains or streams when supported, so marketing-list problems do not interfere with receipts, security alerts, or password resets.
5. Suppress hard bounces permanently. Keep suppression centralized across systems and imports.
6. Reconfirm or retire stale contacts. Do not revive old lists with a full blast.
7. Track acquisition-source quality. Measure hard bounces, complaints, and engagement by source, not just overall volume.
8. Ramp volume gradually after major changes. New domains, IPs, ESPs, and dormant audiences need measured reintroduction.
9. Make unsubscribing easy. A clean opt-out is safer for reputation than forcing an unhappy recipient to complain.
10. Review trends, not only thresholds. A rate that doubles from 0.2% to 0.4% can expose a new problem before it becomes an incident.

Conclusion

A healthy email bounce rate is normally under 1% overall and under 0.5% for hard bounces in a well-maintained permission-based program. But the most valuable insight is not the headline percentage. It is knowing which addresses failed, why they failed, where they came from, whether failures cluster at a recipient provider, and whether your sender identity is properly authenticated.

Use bounces as a diagnostic signal. Suppress confirmed permanent failures, let legitimate temporary failures follow your ESP’s retry process, isolate questionable contact sources, and verify SPF, DKIM, DMARC, volume, and complaints alongside the bounce data. That approach protects both your sender reputation and the inbox access that makes email marketing valuable.

FAQ

Is a 2% email bounce rate good?

A 2% total bounce rate is not automatically catastrophic, but it is high enough to investigate—particularly if hard bounces make up most of it or the rate rose suddenly. A maintained, permission-based list should generally aim lower than 1% total bounces.

What is a good hard bounce rate?

A practical target is below 0.5% hard bounces per campaign. Any sustained increase should trigger a review of list age, signup source, imports, CRM integrations, and recipient-domain error patterns.

Should I resend emails that soft bounce?

Usually, let your ESP handle temporary retries because it understands the recipient server’s response and has its own retry policy. Manually resend only after checking the error type, your provider’s behavior, and whether the message remains relevant; never blindly resend confirmed hard bounces.

Does a low bounce rate mean emails reach the inbox?

No. A low bounce rate means receiving servers accepted most of your mail. Messages can still be filtered to spam or junk, so monitor complaints, authentication, sender reputation, engagement, and inbox-placement signals as well.

Can an email validation service guarantee zero bounces?

No. Validation can identify formatting problems and some risky or undeliverable addresses, but it cannot guarantee that a mailbox will remain active, that a server will accept future mail, or that the recipient wants your messages. Permission-based collection and ongoing list hygiene remain essential.