6 Ways to Reduce Your Email Bounce Rate (and Keep Hitting the Inbox)
6 Ways to Reduce Your Email Bounce Rate (and Keep Hitting the Inbox)
Hard bounces don't just hurt one campaign. They burn the domain your whole business emails from. Six fixes stop them, from your signup form to your first big send.
Say your app has 4,000 signups and 100 of the addresses are bad: a few typos, a test account you forgot to delete, some bots that slipped past the form. That's still 97.5% real users. Sounds fine, right?
Mailbox providers see it differently. Amazon's deliverability guidance puts it bluntly: "When email receivers detect a high rate of hard bounces, they assume that you don't know your recipients well." 1 Bounces are how spammers look, because spammers guess addresses. A bouncy list pattern-matches you with them.
And here's the part most builders miss: the reputation absorbing that damage usually isn't your email tool's. It's your domain's. The same domain your team, your support inbox, and your password resets send from.
The fix comes down to six moves: run addresses through an email verification service, add a confirmation email flow to your app, offer social login, add a CAPTCHA to your signup form, send from a dedicated subdomain, and warm up your sending in small batches. First, a quick look at what actually counts against you.
What is a hard bounce?
A hard bounce is a permanent delivery failure: the address doesn't exist, the domain has no mail server, or the mailbox was deleted. Soft bounces are temporary problems, like a full mailbox or a server timeout, and they usually resolve on their own.
Hard bounces are the ones that count against you. Amazon SES excludes soft bounces from its enforcement calculation entirely, and its advice for hard bounces is unambiguous: remove the address from your list immediately. 1 2
What bounce rate is acceptable in 2026?
Keep hard bounces under 2%. That's the long-standing convention for a healthy list. Enforcement kicks in well above it, and by then you're already in trouble:
| Platform | Published line | What happens |
|---|---|---|
| Amazon SES | 5% bounce rate | Account placed under review 2 |
| Amazon SES | 10% bounce rate | Sending can be paused 2 |
| Postmark | 10% bounce rate | Sending can be suspended 3 |
| SendGrid | 5% hard bounces | Recommended ceiling 4 |
| Dreamlit | 4% hard bounces | Workflows paused for review |
| Gmail | 0.1% spam complaints, never 0.3%+ | Mail filtered to spam 5 |
| Yahoo | 0.3% spam complaints | Mail filtered to spam 6 |
Gmail and Yahoo don't publish a bounce threshold. Their hard lines are spam-complaint rates, but bounces feed the same domain reputation score, and Yahoo explicitly tells senders to remove invalid recipients promptly. 6
One more thing these numbers hide: percentages get twitchy at low volume. If you send 150 emails and 4 bounce, you're at 2.7% off nearly nothing. Small senders should think in absolute bad addresses, not just the rate.
Why bounces put your whole domain at risk
Mailbox providers build reputation around your authenticated sending domain. Gmail's Postmaster Tools scores domain reputation on a four-tier scale from Bad to High, and mail from a low-reputation domain "is likely to be marked as spam." 7
If you send product email from your root domain, that score is carrying everything: founder outreach, support replies, password resets, receipts, and your marketing blasts. All of it rides on your email program's worst day.
What a bounce spike hits: root domain vs. subdomain
Mailbox providers build reputation around the authenticated sending domain. A dedicated subdomain gives product email its own record, so a bad day never spills into the mail your business runs on.
| Setup | What a bounce spike affects |
|---|---|
| Sending from the root domain (yourapp.com) | Everything: founder and team email, support replies, password resets, receipts, and marketing |
| Sending from a dedicated subdomain (mail.yourapp.com) | Only the subdomain's product and marketing email; the root domain's reputation is unaffected |
M3AAWG recommends assigning "a separate subdomain of the main domain name for each distinct sending purpose," keeping the main domain for the mail your business runs on. 8 The reason to care is that damage is asymmetric. A reputation drop takes minutes to earn.
Where do bad addresses come from?
Almost nobody sets out to build a dirty list. It builds itself, one unverified signup at a time. When ZeroBounce processed over 11 billion addresses in 2025, only 62% came back valid. 12
Only 62% of 11 billion checked addresses were valid
For a typical app signup form, the bad addresses arrive four ways:
- Typos.
gamil.com,hotmail.con,yaho.com. Real users, wrong address, guaranteed hard bounce. - Disposable domains. Addresses from mailinator.com or temp-mail.org work for about ten minutes, then everything you send bounces.
- Bots. Automated traffic passed human traffic on the web in 2024, with bad bots alone at 37%.
- Your own test accounts. The
test@test.comyou typed during a late-night debugging session will bounce every campaign you ever send.
How to stop bad addresses at signup
Now for the good stuff. The cheapest bounce is the one that never gets a row in your database, and four of the six fixes live right on your signup form. In rough order of impact:
- Run addresses through an email verification service. Services like Kickbox, NeverBounce, and ZeroBounce check the validity of an address. Call the API from your signup form to catch bad addresses in real time.
- Add a confirmation email flow to your app. Confirmed opt-in can help reduce bounces. An unclicked confirmation costs you one bounce.
- Offer social login. A Google OAuth button hands you a real, pre-verified address.
- Add a CAPTCHA. Stop bots and automated signups using services like Cloudflare Turnstile or Google reCAPTCHA.
How to rescue a list you already have
If you have signups already in your users table:
- Bulk-verify the whole list. Use a verification service to check validity.
- Discard all unverified addresses. Treat catch-all addresses as a maybe pile.
- Move to your subdomain.
- Warm up in batches. Start with a few hundred sends to your most engaged users and check the results before increasing volume.
Example warm-up batch schedule
| Batch | Sends |
|---|---|
| Batch 1 (most engaged users) | 250 |
| Batch 2 | 500 |
| Batch 3 | 1,000 |
| Batch 4 | 2,000 |
| Batch 5 | 4,000 |
Expect the full ramp to take weeks, not days. Clean batch? Double it. Bounces or spam complaints? Stop and clean the list.
How to keep your list clean going forward
- Make unsubscribing effortless. One-click unsubscribe is required for bulk senders.
- Sunset the unengaged. Regularly remove users who aren't engaging with your emails.
- Watch the scoreboard. Use tools like Google Postmaster Tools to track your domain reputation.
The boring work is the growth work
Deliverability compounds quietly in both directions. The builders who treat their sender reputation like uptime get to actually reach the users they worked hard to sign up.
Frequently asked questions
What is a good email bounce rate?
Keep hard bounces under 2%. Enforcement starts higher: Amazon SES reviews accounts at 5%.
What's the difference between a hard bounce and a soft bounce?
A hard bounce is a permanent failure, while a soft bounce is temporary.
Do email bounces hurt my domain reputation?
Yes. Mailbox providers score the reputation of your authenticated sending domain.
Should I send marketing email from my root domain?
No, use a dedicated subdomain for product and marketing emails.
How do I safely email a list of users who never verified their addresses?
Run the list through a verification service, then send in small batches.
How long does it take to warm up a sending domain?
Expect 3 to 6 weeks to establish a reputation at full volume.
Does Dreamlit stop me from re-emailing bounced addresses?
Yes, Dreamlit automatically suppresses hard bounces across future sends.