Email bounce rate is the percentage of emails you send that get rejected instead of delivered. Calculate it by dividing bounced emails by emails sent, then multiplying by 100. Keep it under 2%. Above that, mailbox providers start treating your mail as suspect, and sustained high rates can get your sending account suspended.
That short answer covers the number. This guide covers the mechanics behind it: why bounces happen, how hard and soft bounces differ, what your email service provider actually does when the rate climbs, and the specific fixes that bring it back down. None of this requires expensive tooling. Most of it is discipline, plus a verification pass before you hit send.
How to calculate email bounce rate
The formula is simple: divide bounced emails by emails sent, then multiply by 100. Send 2,000 emails, get 40 bounces, and your bounce rate is 2%. Right at the danger line. Most ESPs (Mailchimp, Brevo, Klaviyo, and the rest) calculate this per campaign and show it next to opens and clicks. Look at it per campaign, not just as an account average, because a single bad list import can hide inside a healthy average.
One nuance worth knowing: sent and delivered are different denominators. Some platforms report bounce rate against attempted sends, others against accepted messages. Check the definition your platform uses before comparing your numbers to benchmarks. Also remember that a bounce is not a spam complaint or an unsubscribe. Bounces are delivery failures. The receiving server refused the message or could not deliver it at all.
Why obsess over a percentage? Because bounce rate is the one deliverability metric that is fully within your control before you send. Open rates depend on subject lines and timing. Complaint rates depend on content and expectations. Bounce rate depends only on list quality, and list quality is checkable in advance.
Hard bounces vs soft bounces
Every bounce comes back with an SMTP response code from the receiving server. Codes starting with 5 signal permanent failures, and codes starting with 4 signal temporary ones. That single digit determines what you should do next: delete the address forever, or let the system retry. Getting this distinction right is most of bounce management, so it is worth getting the vocabulary straight.
Hard bounces
A hard bounce is a permanent failure. The classic example is SMTP code 550 5.1.1, user unknown: the mailbox does not exist. Causes include typos (gamil.com instead of gmail.com), employees who left a company, abandoned accounts, and domains that no longer resolve. A good verifier will flag the typo cases and suggest the fix, as in did you mean gmail.com. Hard bounces should never happen twice. Remove the address the moment it hard bounces, because repeatedly mailing dead addresses is one of the strongest careless-sender signals a mailbox provider can see, and many dead addresses get recycled into spam traps.
Soft bounces
A soft bounce is a temporary failure. The mailbox is full, the receiving server is down or busy, the message is too large, or the server is greylisting you (deliberately deferring first-time senders with a 4xx code to filter out spam bots). Most platforms retry soft bounces automatically for up to 72 hours. The rule of thumb: a soft bounce is fine once, suspicious twice, and effectively a hard bounce after three to five consecutive campaigns. Set a strike policy and stick to it.
What is a safe email bounce rate?
A safe email bounce rate is under 2%. That is the widely accepted industry ceiling, and most mailbox providers and ESPs treat anything above it as a warning sign. Strong senders stay under 1%. If you are sending cold outreach from a young domain, aim for under 1% because you have no reputation cushion.
Where does the 2% figure come from? It reflects what mailbox providers tolerate before they start reading your traffic as a stale or purchased list. In practice, senders with well-maintained lists sit between 0.2% and 1%. If a list has not been mailed in six months, expect far worse: email addresses decay at roughly 20 to 30% per year as people change jobs and abandon inboxes. That decay is why an old list should always be verified before you send to it.
What happens if your bounce rate is too high?
Exceed the safe threshold and two things happen. Your ESP flags the campaign, and repeated offenses lead to sending pauses, forced list reviews, or account suspension. Meanwhile mailbox providers downgrade your sender reputation, so even your valid addresses start landing in spam. Both effects compound with every bad send.
ESPs enforce bounce thresholds because they share sending infrastructure. Your bad list burns IP addresses that thousands of other customers rely on, so they act quickly. Typical escalation looks like this: an automated warning after one bad campaign, then a paused campaign and a request to explain where the list came from, then suspension if it repeats. Getting reinstated usually requires proof that you cleaned the list. It is much cheaper to verify first.
The quieter damage happens at the mailbox providers. Gmail, Outlook, and Yahoo score every sending domain and IP. High bounce rates lower that score, and a lower score means more of your mail routed to spam, slower acceptance, and stricter rate limits. Since 2024, Gmail and Yahoo also require bulk senders to authenticate with SPF, DKIM, and DMARC and to keep spam complaint rates under 0.3%. Bounce rate is not the only signal they watch, but it is the one you control completely.
Check your list right now, free
10 checks a day with no signup. 100 a day with just your email.
Bounce types, causes, and fixes
| Bounce type | What it means | Typical SMTP code | Fix |
|---|---|---|---|
| Hard: unknown user | The mailbox does not exist | 550 5.1.1 | Remove the address immediately; never retry |
| Hard: domain not found | The domain has no valid DNS or MX records | 550 / NXDOMAIN | Remove it; check for obvious typos like gamil.com first |
| Soft: mailbox full | The account exists but is over quota | 452 4.2.2 | Let retries run; suppress after 3 to 5 consecutive failures |
| Soft: server unavailable | The receiving server is down or busy | 421 4.3.2 | No action needed unless it persists across campaigns |
| Soft: message too large | The message exceeds the recipient's size limit | 552 | Trim images and attachments; link to hosted files instead |
| Greylisting | The server defers first-time senders to filter out bots | 451 | Normal retries clear it; keep consistent sending IPs |
| Block or policy rejection | A filter refused your mail for reputation or content reasons | 554 / 571 | Fix SPF, DKIM, and DMARC; check blocklists; review content |
| Catch-all acceptance | The domain accepts every address, so the mailbox cannot be confirmed | n/a | Segment catch-all addresses and mail them cautiously |
Two of these categories deserve special attention. Blocks are not really bounces in the classic sense; they mean the recipient's filter rejected you for reputation or policy reasons, and no amount of list cleaning fixes a broken SPF record. And catch-all domains accept everything during verification, so they can never be fully confirmed. Treat them as a separate risk tier rather than lumping them in with confirmed valid addresses.
How to reduce your email bounce rate
Reducing bounce rate is mostly about controlling what enters your list and removing what goes stale. You do not need every tactic on day one. Work through this sequence in priority order, because the first three items eliminate the majority of bounces on a typical list.
- Verify before every significant send. Run any list that is new, imported, or older than three months through an email verifier and remove invalid addresses before they can bounce.
- Remove hard bounces immediately and automatically. Most platforms do this by default; confirm yours does.
- Set a soft bounce strike policy. Suppress any address that soft bounces three to five campaigns in a row.
- Validate at the point of capture. Use double opt-in, block obvious typos and disposable domains on your signup form, and confirm addresses collected at events or over the phone.
- Authenticate your domain. Publish SPF, DKIM, and DMARC records so receiving filters can trust your mail and block-type rejections drop.
- Sunset unengaged subscribers. Addresses with no opens in 6 to 12 months are the most likely to have decayed. Run a win-back campaign, then let them go.
- Never buy or scrape lists. Purchased lists are where spam traps live, and no verification pass makes a scraped list safe to mail.
On the verification step: this is where a dedicated check earns its keep. A verifier looks up each domain's MX records to confirm it accepts mail at all, then talks to the mail server at the SMTP level to test whether the specific mailbox exists, all without sending anything. Our tool at FreeEmailVerifier gives you 10 checks a day with no signup, and any CSV you drop in is parsed in your browser rather than uploaded, which matters when a list contains customer data.
Also watch your cadence after a cleanup. If a list has been dormant, do not blast the whole thing at once even after verification. Warm back in with your most recently engaged segment first, watch the bounce and complaint numbers, then expand. Verification removes invalid addresses, but it cannot tell you whether a valid address belongs to someone who still wants your email.
Treat bounce rate like a smoke alarm
Bounce rate is the smoke alarm of email deliverability. It is the first metric to move when something is wrong with your list, and it moves before the expensive damage happens: reputation loss, spam foldering, account suspension. Treat any reading above 2% as an alarm rather than a statistic, and investigate the same day. Find which segment bounced, where those addresses came from, and whether the failures were hard or soft.
The habit that keeps the number low is boring and cheap. Verify new lists before mailing them, remove failures immediately, and re-check anything that has sat idle for a quarter. Senders who do those three things rarely think about bounce rate at all, which is exactly the goal.