Your bounce rate is the share of messages a receiving server refuses to accept for a recipient. A little is unavoidable — mailboxes close, people leave jobs, domains lapse. But a high or rising bounce rate tells providers like Gmail, Yahoo and Outlook that you’re mailing a list you don’t maintain, which is exactly the signal spammers give off. As a widely-cited industry benchmark, staying under about 2% keeps you in safe territory; sustained rates above it invite throttling, spam-foldering and outright blocks. The levers below are ordered by impact.
1. Verify and clean the list before every send
The single biggest cause of bounces is mailing addresses that were never valid or have since died. You cannot fix this after the send — the damage to your reputation is already recorded. So clean before you hit send, not after.
- Run the whole list through the Email Verifier. It performs a live SMTP probe without actually sending a message, so it flags mailboxes that don’t exist before a receiving server ever counts a bounce against you.
- Drop anything that comes back undeliverable, and segment out risky, role-based and catch-all results so they don’t drag your average up. The full workflow is in how to clean an email list.
- Never mail a purchased or scraped list. Those are packed with dead addresses and spam traps, and no amount of cleaning makes them safe.
2. Suppress hard bounces immediately — and permanently
A hard bounce is a permanent failure: a 5.x.x reply such as 550 5.1.1 (mailbox doesn’t exist) or 5.2.1 (mailbox disabled). Retrying it never helps, and every repeat is a fresh strike against your reputation. Add these addresses to a suppression list the moment they bounce and never mail them again unless they re-confirm through a fresh sign-up. If your platform doesn’t auto-suppress hard bounces, that’s the first setting to fix. For the full distinction between the two kinds of failure and what to do with each, see hard bounce vs soft bounce.
Not sure which category a specific bounce falls into? Paste it into the Bounce Message Analyzer and it will tell you whether the failure is permanent (suppress) or transient (retry).
3. Fix SPF, DKIM and DMARC
Not every bounce is a bad address. Authentication failures produce 5.7.x rejections — 550 5.7.26 from Gmail, 550 5.7.515 from Outlook — that look like bounces but are entirely sender-side. If your SPF, DKIM and DMARC aren’t set up and aligned with your visible From: domain, providers will reject perfectly valid recipients. Confirm all three at once with the Email Health Check, and if you’re seeing provider-specific rejections, follow how to fix Gmail and Outlook rejections. A clean reverse-DNS (PTR) record matters too — check it with the Reverse DNS Checker and confirm your policy with the DMARC Checker.
4. Warm up and keep your volume steady
A cold IP or domain that suddenly sends thousands of messages looks like a compromised account, and receivers respond with deferrals (421 4.7.0) that can turn into hard blocks. Ramp volume gradually over days or weeks on a new sending identity, and once you’re established, keep your daily volume roughly consistent — big erratic spikes trigger rate-limiting even on a warm domain. Steady, predictable sending is itself a reputation signal.
5. Segment by engagement
Addresses that haven’t opened or clicked in six to twelve months are the ones most likely to have gone dead or turned into recycled spam traps. Mailing them harms you twice: more bounces, and more “no engagement” signals that push you toward the spam folder. Build a re-engagement segment, give dormant contacts one or two last-chance campaigns, then suppress the non-responders. This keeps your active list tight and your bounce rate low. Reputation and engagement are tightly linked — see how to check and repair your sender reputation.
6. Monitor so you catch problems early
Bounce rate is a lagging indicator — by the time it spikes, the reputation damage is done. Watch it per-send and per-provider so you can spot a bad import or a broken authentication change before it compounds. If bounces suddenly jump for one provider only, it’s almost always an authentication or reputation issue, not the list. Run a periodic Email Blacklist Check to make sure you haven’t been listed, and keep re-verifying on a schedule since lists decay 20–30% a year.
Verify your setup right now
Two checks close the loop. Run your sending domain through the Email Health Check to confirm SPF, DKIM, DMARC, PTR and blacklist status are all clean, then push a sample of your list through the Email Verifier to catch dead addresses before they bounce. If both come back clean and your volume is steady, your bounce rate should settle well under 2%.
Common failure modes
- Cleaning after the send. Removing bounces afterward protects future sends but does nothing for the reputation hit you just took. Always verify first.
- Not suppressing hard bounces. If the same dead address bounces on every campaign, your platform isn’t auto-suppressing. Fix that setting today.
- Blaming the list for a 5.7.x block. Authentication rejections aren’t bad addresses — no amount of list cleaning fixes them. Check SPF/DKIM/DMARC alignment.
- Reactivating an old list without re-verification. A list dormant for a year can be 20–30% dead. Re-verify before the first send back.
Sources
SMTP reply codes and their permanent-vs-transient semantics are defined in RFC 5321; the enhanced status codes (the 5.1.1-style numbers) come from RFC 3463; and the delivery status notification format that carries them is RFC 3464. Provider throttling thresholds vary, but keeping bounces under roughly 2% is a widely-used industry benchmark rather than a single published rule.