How to cut your email bounce rate below 2% before your next campaign
Most sending platforms start asking questions somewhere between 2% and 5% bounces. Here's what Gmail, Yahoo, Outlook and the big email platforms actually say, and six steps to get under 2% before your holiday sends.
Rafael Herrera, Director of Alliance Sales, North America, DQE
7 min read

On this page
Every platform you send email through keeps a scorecard on you, and bounces sit near the top of it.
Amazon SES, the sending service behind a lot of marketing tools, is blunt about it: "maintain a bounce rate below 2%." At 5% it puts your account under review. At 10% it may pause your sending altogether. HubSpot lists a 5% hard bounce rate as one of the reasons it suspends marketing email.
So think of 2% as your buffer. Below it, you decide what happens to your sending. Above 5%, somebody else starts deciding for you. With Black Friday and Cyber Monday campaigns about to go to the whole list, now is the time to check where you stand.
What is a good email bounce rate?
Under 2% is safe, and under 1% is good. There's no single industry standard, but the platforms that actually enforce limits say much the same thing:
Where the platforms draw the line on bounces
Published limits from the platforms that enforce them, on one scale from 0% to 10%.
- 1%
- Klaviyo: under 1% is healthy
- 2%
- Amazon SES: keep it below 2%
- Brevo: hard bounces above 2% can trigger suspension
- Klaviyo: over 2% needs attention
- 5%
- Amazon SES: account goes under review
- HubSpot: a 5% hard bounce rate is a reason to suspend
- Twilio SendGrid: keep hard bounces under 5%
- 10%
- Amazon SES: sending may be paused
| Who | What they say | What it is |
|---|---|---|
| Amazon SES | Keep it below 2%. Review at 5%, possible pause at 10%. | Account policy |
| Klaviyo | Under 1% is healthy, 1% to 2% has room for improvement, over 2% needs attention. | Help center guidance |
| Brevo | A hard bounce rate above 2% is a trigger for suspension. | Account policy |
| HubSpot | A 5% hard bounce rate is a reason for suspension. | Account policy |
| Twilio SendGrid | Keep hard bounces under 5% of the messages you attempt. | Guidance |
Around 5%, the platforms stop warning you and start acting.
Hard bounce vs soft bounce: which one hurts?
A soft bounce is temporary. The inbox is full or the receiving server is down, and the message may get through on the next try. A hard bounce is permanent: the mailbox doesn't exist, or the domain doesn't.
The thresholds above are mostly about hard bounces, and for good reason. M3AAWG, the industry group that writes sender best practices, says large volumes of hard bounces "can subtract points from an IP's reputation score." Those points come off the reputation of every email you send, including the ones to customers who wanted them.
Soft bounces still count when they repeat. M3AAWG's rule of thumb is to remove an address once it "bounces consecutively at least two times over two weeks or more."
What Gmail, Yahoo and Outlook require from bulk senders
Since 2024, Gmail, Yahoo and Outlook have all tightened the rules for bulk senders.
- Gmail treats anyone sending more than 5,000 messages a day to Gmail accounts as a bulk sender. Those senders need SPF, DKIM and DMARC, plus one-click unsubscribe, and must keep their spam rate below 0.10%. Starting November 2025, Google said it was ramping up enforcement, including "temporary and permanent rejections."
- Yahoo asks for the same authentication, a spam rate under 0.3%, and this line: "Remove invalid recipients from your list promptly."
- Outlook has rejected mail from high-volume domains (more than 5,000 a day) that fail SPF, DKIM or DMARC since May 5, 2025. Its advice: "Remove invalid addresses regularly."
All three ask senders to get rid of bad addresses. When the people running the inbox ask you to clean your list, clean your list.
What causes email bounces?
Hard bounces usually start in one of three places.
The first is a typo at signup. Someone types gmail.con at checkout or in a webinar form, and that address lives in your CRM forever. M3AAWG warns that with single opt-in, "typos or outright forgeries can be added unchecked."
The second is a job change. A work email dies when the person leaves. The median US worker had been with their employer 4.1 years in January 2026, and in leisure and hospitality it was just 2.4 years (Bureau of Labor Statistics). If your B2B list is a few years old, a real share of it now belongs to people who left those companies.
The third is old or imported data: event scans, purchased lists (please don't) and contacts nobody has emailed since 2023. One forgotten segment like that can push a healthy campaign past the 5% line.
How to reduce your email bounce rate: six steps before your next send
1. Get your real number
Pull the hard bounce rate for your last few campaigns, separate from soft bounces. Some platforms blend the two into a single "bounced" figure. If yours does, export the bounce reasons and count the permanent ones yourself.
2. Validate the list before you hit send
Run the list through an email validation tool. A proper check looks up the domain's mail servers, asks the receiving server whether that specific mailbox exists (no email is actually sent), and flags disposable addresses, role addresses like info@, and known spam traps.
Then sort by result. Remove the clear failures: mailbox not found, domain doesn't exist, disposable. Put the "can't confirm" results in their own segment. Some company domains accept everything at the server and bounce later, so a validator can only tell you the domain is real.
Sort the results before you send
Six rows from a list after validation. Remove the clear failures, hold back what can't be confirmed, send the rest.
- olivia.grant@northwindgoods.comMailbox existsSend
- sam.patel@harborline.coMailbox not foundRemove
- info@brightpathevents.orgRole addressSegment
- kai.r@mailinator.comDisposable addressRemove
- j.moreno@acmewholesale.comDomain accepts everything, mailbox unconfirmedSegment
- dana.reyes@gmail.conDomain doesn’t existRemove
1 to send2 to mail last, in a small batch3 off the list before they bounce
3. Hold back the stale segment
Contacts who haven't opened or clicked in a long time are where hard bounces and spam traps hide. Pick a window that fits how often you send, validate that segment separately, and mail it last in a smaller batch. If that batch bounces, it won't take your main send down with it.
4. Authenticate your domain
SPF, DKIM and DMARC are now table stakes at Gmail, Yahoo and Outlook. Outlook rejects unauthenticated high-volume mail outright (the error is 550 5.7.515), and a rejection looks a lot like a bounce in your reports. Ask whoever manages your DNS to check all three before a big campaign.
5. Check addresses at the signup form
A real-time check on the signup or checkout form catches the typo while the person is still there to fix it. M3AAWG rates confirmed opt-in, where the subscriber clicks a link to confirm, as best practice. Google's guidelines point the same way: "Confirm each recipient's email address before subscribing them." Developers can wire the check in with a single API call; the developer docs have examples.
6. Clean up after every send
Remove hard bounces as soon as the campaign finishes. Apply the two-bounces-in-two-weeks rule to soft bounces. Google suggests you "automatically unsubscribe recipients who have multiple bounced messages," and many sending platforms have a setting for it.
What email validation won't fix
Validation removes addresses that can't receive mail, and that's all it does.
If your spam complaints are high, the problem is usually who you're mailing or what you're sending them, and a clean list won't hide that from Gmail's 0.10% spam-rate line. Validation also can't confirm every mailbox behind a catch-all domain. Treat it as the step that takes bounces off the table, so you can work on everything else with a clean baseline.
Where DQVerify fits
DQVerify email validation checks email addresses, along with postal addresses and phone numbers, through the dashboard or the API. Upload a CSV, map the email column, and you get a result code and risk score on every row. For signup forms, the same check runs in real time through the API.
Each email check uses one credit. In the 20,000-credit packs that's $0.035 per address (see pricing), and you get 100 free credits for 14 days with no credit card, enough to test a sample of your list before a campaign. We don't store your validation data.
If your peak-season plan also includes parcels, our holiday shipping checklist covers the address side. And if you can't say what your hard bounce rate was on the last campaign you sent, step one is waiting for you.
Sources
- Amazon Web Services, Amazon SES enforcement FAQ, accessed October 2, 2026.
- Klaviyo Help Center, bounce-rate benchmarks, updated March 10, 2026.
- Brevo Help Center, account suspension criteria, accessed October 2, 2026.
- HubSpot, Why is my email suspended?, updated September 23, 2026.
- Twilio SendGrid docs, bounce and block classifications, accessed October 2, 2026.
- M3AAWG, Sender Best Common Practices, version 4.0, August 2026.
- Google, Email sender guidelines and Email sender guidelines FAQ, accessed October 2, 2026.
- Yahoo, Sender best practices, accessed October 2, 2026.
- Microsoft Defender for Office 365 blog, Outlook requirements for high-volume senders, April 2, 2025, updated April 30, 2025.
- US Bureau of Labor Statistics, Employee Tenure Summary, September 24, 2026.
Questions people ask
More answers in the full FAQ.



