Cold Email Bounce Rate: What Google and Microsoft Say
Google publishes no bounce threshold. Only Amazon SES gives numbers, 5% and 10%. What the providers say, and how a small cold sender should read them.

You sent 40 cold emails this morning and checked the inbox at lunch. Six bounce notices sat at the top, each one a polite wall of SMTP text that boils down to "nobody lives here." You now want to know whether six in 40 is a problem, so you
You sent 40 cold emails this morning and checked the inbox at lunch. Six bounce notices sat at the top, each one a polite wall of SMTP text that boils down to "nobody lives here." You now want to know whether six in 40 is a problem, so you search for a cold email bounce rate benchmark. The results are vendors with a number, a product and no source. This post reads what the mailbox providers themselves publish, which is less than you hope, and then says what we would do with it.
Google publishes a spam rate and no bounce rate
Google's email sender guidelines contain exactly one numeric deliverability rule: keep the spam rate reported in Postmaster Tools below 0.10% and never reach 0.30%. There is no bounce threshold anywhere on the page.
Bounces do show up twice. The first is in the volume advice: if messages start bouncing or getting deferred, reduce the sending volume until the SMTP error rate decreases, then increase slowly again. If bounces and deferrals continue at a low volume, Google says to review individual messages for problems. The second is in the unsubscribe section, which lists "automatically unsubscribe recipients who have multiple bounced messages" as good hygiene.
Google also documents what a dead address looks like from your side. In its SMTP error reference, 550 5.1.1 reads "The email account that you tried to reach does not exist," and 5.1.2 means Google could not find the recipient domain. Nowhere does that page say that repeated sends to dead addresses lower your reputation. Anyone quoting you a Google bounce threshold is quoting a vendor, not Google.
Microsoft and Yahoo describe bounces and skip the number
Microsoft's non-delivery report reference for Exchange Online lists 5.1.1 as "Bad destination mailbox address." The causes it gives include an address that does not exist in the destination system, and it adds that the error "can occur if the recipient's email address was previously valid but later changed or removed." A separate row, 5.1.10, means the recipient was not found. That reference page has no bounce-rate figure either.
Yahoo's sender best practices are the blunt ones. Their "remove invalid recipients" section says to monitor hard and soft bounces and to remove invalid recipients from your list promptly. The only number on the page is the same 0.3% spam rate.
Amazon SES publishes the only hard numbers, and they are for its own customers
The one primary source with percentages is Amazon's reputation dashboard documentation. It says to keep the bounce rate below 5% for best results, that a rate of 5% or more automatically puts the account under review, and that at 10% or more Amazon might pause the account's ability to send. Those numbers govern an SES account. They do not describe how Gmail or Outlook score you.
Two definitions on that page matter for a cold sender. SES builds the rate from hard bounces only, which it defines as mail sent to an address that does not exist, and it ignores soft bounces, which happen when an address is temporarily unable to receive. It also calculates over a "representative volume" of mail rather than any 40-message morning, so one bad address in a tiny batch does not trip a wire.
The page gives the reasoning too, and the reasoning is the transferable part. Email providers read a high bounce rate as a sign that a sender is not managing the recipient list properly and might be sending unsolicited email. That is Amazon's reading of the mailbox providers, and it fits what Yahoo says about removing invalid recipients.
Nobody publishes a safe bounce rate for cold email. They publish what a dead address looks like and tell you to stop sending to it.
Six bounces in 40 emails is a list problem, not a percentage problem
Run your own numbers. 6 of 40 is 15%. Against the SES ladder, that would be far past the pause line. Against Google, it means nothing numeric, because Google publishes no line, and the guidance it does give says to cut volume and read your messages.
Small volume makes the percentage jumpy in the other direction as well. At 20 emails a day, a single bounce is 5%. We watch the number over a week of sends instead of one day. That is our habit, not a rule from any source above.
What we would not do is treat 15% as an acceptable tax. A cold list full of dead addresses almost always means one of two things: the addresses were guessed from a name and a domain pattern and never verified, or the list is old and people changed jobs. Microsoft's own wording covers the second one, because an address that was valid once and later changed or removed is the textbook 5.1.1.
Pattern-guessed addresses are where most cold bounces come from
If you build lists by hand, you know the move. You find a founder on LinkedIn, guess firstname@company.com, and send. When the pattern is wrong, you get the bounce, and the bounce is the only verification you ever ran. Our enrichment workflow post puts an SMTP verification step before the first send for exactly this reason, and it is the cheapest bounce control you can add.
Verification has limits. A check tells you whether a server accepts the address at that moment, and some servers accept everything and bounce later, so a clean check lowers your bounce rate without zeroing it.
What we would do when the bounces start
This section is our opinion, built on Google's advice to cut volume and increase slowly.
Pause the sequence for any domain that returns more than one 5.1.1 in a batch, and check the address pattern before you send anything else there. Cut the next day's volume for the whole mailbox if bounces cluster, then raise it again only while replies hold. Send to the address you verified and not to a variant you think is probably right. Keep an eye on your complaint rate in Postmaster Tools as well, since the published spam-rate targets are the number Google actually names.
Bounces at a large provider can also show up as an outright rejection instead of a bounce notice. If the error says your sending domain or IP is the problem and not the recipient, you have a different issue, and our write-up of why Outlook rejects cold email with error 5.7.515 covers that side. Our cold email playbook for 2026 has the volume and list rules we run before any of this comes up.
Replying in a thread cannot bounce
Here is the part that is specific to how we work. A Reddit or Hacker News post that says "anyone recommend a tool for X" has no email address attached, so the first contact is a public reply in the thread. A reply cannot bounce, never touches your sending reputation, and lands in front of someone who just asked. That is the whole reason the reply rate math favors a short list of people who raised their hand over a long list of guessed addresses.
Shadow Inbox is our product. It does not send email and it does not fix a bad list. It watches Reddit and Hacker News, scores each post for buying intent, and hands you the likely buyers, so the email you eventually write goes to someone who asked for it, at an address you looked up rather than guessed.
● FAQ
- What is a good bounce rate for cold email?
- No mailbox provider publishes one. The only hard numbers come from Amazon SES, which asks senders to stay under 5% and may pause an account at 10%. Treat that as an outer wall for a bulk sending service, not as a target for a founder emailing a hand-built list.
- What is the difference between a hard bounce and a soft bounce?
- A hard bounce means the address does not exist, so the message can never arrive. A soft bounce means the address is temporarily unable to receive mail, for example because the mailbox is full. Amazon SES counts only hard bounces toward its bounce rate.
- Does Gmail penalize you for emailing addresses that do not exist?
- Google's sender guidelines do not say so in as many words. They tell senders to reduce volume when messages start bouncing and to review individual messages if the bounces continue. The numeric rule Google does publish is a user-reported spam rate under 0.10%.
- How do I lower my cold email bounce rate?
- Stop sending to addresses you guessed and never checked, and remove any address that bounces as soon as it does. Verify the address before the first send, and drop the whole batch if more than a few in a hundred fail. Fixing the list beats sending more and hoping.
- What does a 5.1.1 error mean?
- Gmail's 550 5.1.1 says the account you tried to reach does not exist. Microsoft lists 5.1.1 as a bad destination mailbox address, usually a typo, or an address that was valid once and later changed or removed. Either way the fix is the address, not the message.
Three more from the log.
Cold Email Open Tracking: Turn It Off or Keep It?
Apple pre-loads your tracking pixel, security bots click your links, and Google's rules mention neither. What to switch off in cold email, and what to watch.
Nov 12, 2026 · 6 min
Does Gmail Detect AI-Written Email? Not Per Google
Google's spam filter docs list no AI-authorship signal. Gmail flags cold email for authentication, reputation and complaints, not for who wrote it.
Sep 22, 2026 · 6 min
Do You Need DMARC for Cold Email? What Google Says
Google lists DMARC under its 5,000-a-day rules and Microsoft says smaller senders benefit too. What a founder sending 30 emails a day should publish.
Nov 17, 2026 · 7 min