Why Do Emails Bounce Back? Causes, Codes and Fixes
Emails bounce back when the recipient's server rejects them. Learn hard vs soft bounces, what bounce codes mean and how to stop emails bouncing.
TL;DR: Emails bounce back when the recipient's mail server refuses them. The most common reasons are an address that doesn't exist or has a typo (a hard bounce), a full mailbox or busy server (a soft bounce), and a server that blocks you because of your sending reputation or missing authentication.
An email bounces back when the recipient’s mail server can’t or won’t accept it and sends you a failure notice instead, often called a non-delivery report (NDR). The notice includes an SMTP code that tells you why. Codes starting with 5 are permanent failures (hard bounces), and codes starting with 4 are temporary (soft bounces).
The most common reasons an email bounces back:
- The address doesn’t exist: it has a typo (
jane@gmal.com), or the mailbox was deleted when someone left a company. - The domain can’t receive mail: it has expired, doesn’t exist, or has no mail server set up in its DNS.
- The mailbox is full or the server is busy: a temporary problem that often clears on a retry.
- The receiving server blocks you: your domain or IP is on a blocklist, your reputation is poor, or SPF, DKIM and DMARC aren’t set up.
- The message is rejected: it’s too large, or content filters refuse it.
To stop emails bouncing, remove hard bounces right away, let soft bounces retry, verify your list before you send, and authenticate your sending domain.
Your Quick Guide to Bounced Emails

Understanding why emails bounce is the first, most crucial step to improving your deliverability. After all, if your messages aren’t even reaching the inbox, the rest of your email strategy doesn’t matter much.
These rejections fall into two main categories, and the difference is pretty important:
- Hard Bounces: These are the permanent dead ends. A hard bounce means the email address is invalid, doesn’t exist, or has been deleted. There’s no fixing it; the address is a lost cause.
- Soft Bounces: These are temporary hiccups. The email address is perfectly valid, but something is preventing delivery right now. Maybe their inbox is full, or their company’s email server is down for maintenance.
Ignoring bounces, especially hard bounces, is a fast track to a bad sender reputation. Internet Service Providers (ISPs) pay close attention to this.
Think of it this way: if you keep sending mail to a demolished building (a hard bounce), the post office will eventually flag you as a spammer who isn’t paying attention.
This is a big deal because a poor reputation means even your legitimate emails to valid addresses might start getting filtered into spam or blocked entirely.
To help you get a quick handle on what might be going wrong, here’s a look at the most common reasons your emails might be bouncing back.
Common Reasons Your Emails Bounce
| Bounce Category | Common Reason | Example |
|---|---|---|
| Hard Bounce | Invalid Email Address | john.doe@gmal.com (typo in domain) |
| Block (hard bounce) | Blocked by Server | Your sending domain or IP is on a blocklist the recipient’s server uses. |
| Soft Bounce | Mailbox Full | The recipient has no storage space left to receive new mail. |
| Soft Bounce | Server Unavailable | The recipient’s mail server is temporarily offline or too busy. |
Keeping an eye on these issues is key. A few soft bounces are normal, but a sudden spike in hard bounces signals a serious problem with your email list that you need to address immediately.
Hard Bounce vs Soft Bounce

A hard bounce is a permanent failure: the receiving server says the message will never be delivered, so you should stop emailing that address at once. A soft bounce is a temporary failure: the address may be fine, but the message couldn’t be delivered this time, so your sending platform tries again.
| Hard bounce | Soft bounce | |
|---|---|---|
| What it means | Delivery will never succeed | Delivery may succeed later |
| SMTP code | 5xx, e.g. 550 5.1.1 | 4xx, e.g. 421 4.3.2 or 452 4.2.2 |
| Common causes | Address or domain doesn’t exist, typo, deleted mailbox, permanent block | Full mailbox, server down or busy, rate limiting, greylisting |
| What your platform does | Stops sending to the address | Retries for hours or days |
| What you should do | Suppress the address immediately (unless it’s a block, see below) | Watch it, and suppress it after 3–5 soft bounces in a row |
| Effect on reputation | High: providers read it as a sign of an old or bought list | Low, unless the same addresses keep failing |
What Causes a Hard Bounce
- The address doesn’t exist. This is the most common cause: a typo at sign-up, a made-up address, or a mailbox deleted after someone left a company.
- The domain doesn’t exist or can’t receive mail. The domain has expired, is misspelled (
gmial.com), or has no mail server set up in its DNS (no MX record and no address record to fall back on). - The receiving server permanently rejects you. Blocklist listings and strict security policies also come back as 5xx codes, even when the address is real. These “block bounces” are fixed by repairing your reputation or authentication, not by cleaning your list, so don’t suppress addresses that bounce this way.
What Causes a Soft Bounce
- The mailbox is full. Common with abandoned inboxes that no one checks.
- The server is down or overloaded. The receiving server can’t take mail right now.
- Rate limiting or greylisting. Some servers deliberately defer mail from senders they don’t recognize, or that send too much too fast, and accept it on a later retry.
- Temporary reputation deferrals. Gmail and Outlook sometimes slow down mail from senders they’re unsure about instead of rejecting it outright.
One case sits in between: a message that’s too large usually gets a permanent 552 code, but sending a smaller version fixes it.
When a Soft Bounce Becomes a Hard Bounce
Most sending platforms retry a soft bounce for 24 to 72 hours before giving up on that message. If the same address soft bounces on three to five sends in a row, treat it as dead and suppress it. Abandoned mailboxes often sit “full” for months before the provider deletes them, and then they start hard bouncing.
The surest way to prevent hard bounces is to check addresses before you send: our free email bounce checker flags invalid and dead addresses. Soft bounces depend on conditions at send time, so manage those as they happen.
The Hidden Reasons Your Emails Get Rejected
Sometimes, you do everything right—the email address is perfect, the spelling is checked—and your email still bounces. What gives? Often, the problem isn’t the recipient’s address; it’s you. Or more specifically, your sender reputation.
Think of inbox providers like Google and Yahoo as the gatekeepers of a very exclusive club. Their job is to protect their users from unwanted mail. They scrutinize every single sender, and if your reputation is shaky, your emails get turned away at the door.
Past sins like high bounce rates, spam complaints, or sending to a ghost town of unengaged contacts all chip away at your reputation. These signals tell providers that your messages might be junk, prompting them to block you before you even get a chance.
This infographic breaks down the most common culprits that tarnish a sender’s reputation and lead to frustrating rejections.

As you can see, a spotty sending history and a failure to properly verify who you are can be major red flags for email providers.
Proving Your Identity to Mail Servers
A huge part of building a solid reputation is simply proving you are who you say you are. This is where email authentication comes in. These are technical standards that work like a digital passport, verifying your identity to receiving mail servers around the world.
There are three key protocols you need to know:
- SPF (Sender Policy Framework): This is a public list of all the mail servers that are officially allowed to send emails from your domain.
- DKIM (DomainKeys Identified Mail): This adds a digital signature to your emails, proving they haven’t been tampered with on their journey.
- DMARC (Domain-based Message Authentication, Reporting & Conformance): This tells receiving servers how to handle emails that fail the SPF or DKIM checks—whether to quarantine them or reject them outright.
Sending emails without these in place makes you look suspicious. It’s no surprise, then, that major providers are far more likely to reject your messages. Even for legitimate senders, getting into the inbox is tough; top providers like Google and Microsoft only have inbox placement rates of 87.2% and 75.6%, respectively. That’s a lot of mail that never makes it.
Failing to set up proper authentication is like showing up to that exclusive club without an ID. The bouncers (email providers) have every reason to turn you away, meaning your campaign fails before it even has a chance to succeed.
For anyone serious about email deliverability, implementing these protocols isn’t optional—it’s essential. SMTP-level authentication is the foundation here, so it helps to also understand what SMTP authentication is and how reverse DNS lookups play into the trust signals receiving servers evaluate.
How to Understand Email Bounce Codes
When an email bounces back, that failure notice you get—often called a non-delivery report (NDR)—is packed with useful information. The most important clues are the SMTP bounce codes, which are three-digit numbers explaining exactly why your email didn’t make it.
Think of these codes like the check engine light in your car; they’re diagnostic tools telling you what went wrong under the hood.
The good news is you don’t need to memorize a huge list. You can figure out most of what’s happening just by looking at the very first number. This simple trick separates temporary glitches from permanent dead ends.
4xx codes almost always point to a temporary problem (a soft bounce), while 5xx codes signal a permanent failure (a hard bounce). Getting this difference right is the key to managing your email list effectively.
Knowing this tells you whether to give it another shot or to cut your losses and remove the address for good.
Decoding the Most Common Bounce Codes
To really get a handle on this, you just need to know a few of the most common codes you’ll run into. For example, a 421 code often means the recipient’s email server is just too busy at the moment. This is a classic soft bounce, and your email service provider will usually try sending it again automatically. No action needed on your part.
A 550 code, on the other hand, is a major red flag. This code typically translates to “Mailbox not found” or “Recipient address rejected,” which is a dead giveaway that the email address doesn’t exist. This is a hard bounce, and you should remove that contact from your list immediately to protect your sender reputation.
Here’s a quick-reference guide to help you translate these codes and decide on your next move.
Common Bounce Codes and What to Do About Them
This table breaks down the most frequent bounce codes you’ll see, what they actually mean in plain English, and the best way to respond.
| Bounce Code | What It Means | Your Next Step |
|---|---|---|
| 550 (or 5.1.1) | User Unknown / Mailbox Not Found | Hard Bounce. Remove the email address from your list immediately. |
| 421 | Service Unavailable / Busy Server | Soft Bounce. No action needed; your ESP will retry sending. |
| 452 (or 4.2.2) | Mailbox Full | Soft Bounce. Wait and see if the user clears space. |
| 554 | Transaction Failed / Blocked | Hard Bounce. Your IP or domain may be blocklisted; investigate immediately. |
Getting comfortable with these codes turns a frustrating bounce notification into a clear, actionable insight. It’s a small skill that pays off big in deliverability.
The Full SMTP Bounce Code Taxonomy
Once you’ve got the basics down, the full set of SMTP reply codes is short enough to memorize. The 4xx range covers transient failures (soft bounces); the 5xx range covers permanent failures (hard bounces).
The 4xx soft-bounce codes worth recognizing:
- 421 — Service not available. Receiving server is busy or briefly offline.
- 450 — Mailbox unavailable. Address is valid but the mailbox is locked or throttled; retrying later almost always works.
- 451 — Local error in processing. Something went sideways on the recipient side (greylisting, internal queue issue, DNS hiccup).
- 452 — Insufficient system storage. Mailbox or server is full. Common on long-dormant consumer accounts.
The 5xx hard-bounce side of the table:
- 550 — Mailbox unavailable / user unknown. The single most common hard bounce. The address either never existed or has been deleted.
- 551 — User not local. Recipient server says the user lives elsewhere and it won’t forward. Often an expired forwarding rule.
- 552 — Exceeded storage allocation. Looks like 452, but the server treats it as permanent.
- 553 — Mailbox name invalid. A syntax problem in the address itself — worth a sanity check against the format of an email address.
- 554 — Transaction failed. The catch-all hard bounce, usually a policy reject: IP or domain blocklisted, content filter, or failed authentication. If 554s spike, check your domain spam rating immediately.
Extended DSN codes like 5.1.1 (“bad destination mailbox address”) or 4.2.2 (“mailbox over quota”) sit alongside these and add a second layer of detail. Modern ESPs surface both numbers in the bounce event payload.
Mailbox-Provider-Specific Bounce Patterns
Not every mailbox provider speaks the same dialect of bounce. Two identical messages can bounce for completely different reasons depending on whether you’re sending to Gmail, Microsoft, or Yahoo. Knowing the patterns saves a lot of debugging.
- Gmail is engagement-obsessed and loud about reputation. Expect 452/552 “mailbox full” on dormant personal accounts, 550-5.7.26 when your domain isn’t trusted or your SPF/DKIM/DMARC alignment is broken, and 421-4.7.28 throttling when a cold IP sends too fast.
- Microsoft (Outlook.com, Office 365, Hotmail) is the most policy-driven. The big ones: 550 5.7.1 “Service unavailable; client host blocked” (IP on an internal blocklist), 550 5.7.606 “Access denied, banned sending IP” (explicit block requiring a delisting request), and 550 5.4.1 “Recipient address rejected” on B2B sends where the company firewall doesn’t recognize you.
- Yahoo and AOL lean on reputation deferrals.
421 4.7.0 [TSS04]or[TS01]is a temporary deferral that usually clears if you slow down.554 “Message not allowed - [PH01]”is a content or phishing-style block. - Apple iCloud quietly returns
554 5.7.1 mail server IP rejected by RBLwhen your sending IP is on a public blocklist. Watch for iCloud-only bounce spikes — they’re a fast tell.
When you see a wave of bounces clustered at a single provider, the reply text tells you whether it’s a reputation problem (fix sender trust) or an address problem (clean the list).
Bounces and Sender Reputation
Bounce rate isn’t a vanity number — it’s a direct input into the email sender reputation score every mailbox provider keeps on your domain and sending IP. Every hard bounce tells receivers “this sender is mailing addresses they can’t verify,” and your domain spam rating follows the same curve.
Rough thresholds most teams use: under 2% is healthy, 2–5% is the yellow zone where reputation starts sliding, and over 5% is red — expect throttling at Gmail and outright blocks at Microsoft within a few sends.
If you’re in the yellow or red zone, the tactical fix is to pause the campaign, validate against an email address existence checker, and only resume to addresses that pass. For ongoing hygiene, an email list cleaning service keeps bounce rate from drifting back up. If you’re already blocklisted, run the email blacklist removal process first.
Modern Bounce Handling: Webhooks and Suppression Lists
A decade ago, processing bounces meant parsing the raw NDR email yourself. Today, every serious ESP — SendGrid, Postmark, Mailgun, Resend, Amazon SES, Customer.io — emits structured bounce events through webhooks. If you’re sending transactional email, you should be consuming those events in your application, not staring at an inbox.
A typical bounce webhook payload includes the recipient address, a classification (hard vs soft, or provider-specific tags like block, spam, quota), the full SMTP reply, and a timestamp plus message ID for correlation.
The standard pattern for acting on these events:
- Receive the webhook, verify the signature.
- Look up the contact by message ID or recipient.
- Hard bounce: mark suppressed in your database immediately.
- Soft bounce: increment a counter, and after 3–5 consecutive soft bounces promote to hard suppression.
- Skip suppressed addresses on every future send.
If you’re newer to transactional sending, our roundup of transactional email examples shows what these events look like in production.
Suppression-List Management
A suppression list is the catalog of addresses you’ve decided never to email again. Most ESPs maintain one for you, but the scoping matters: SendGrid, Mailgun, and Postmark auto-suppress hard bounces per-account, so none of that history transfers when you switch providers. Always export and re-import on day one of a migration.
Two gotchas worth knowing. First, some ESPs (notably Amazon SES) do not auto-suppress repeated soft bounces — you have to track those repeats and promote them yourself. Second, unsubscribes and spam complaints belong on the suppression list too, treated the same as hard bounces.
Teams that send at scale usually centralize all of this through dedicated email list management software, so a bounce in one stream — marketing, transactional, lifecycle — protects every other stream.
Actionable Steps to Lower Your Bounce Rate

Knowing why emails bounce is one thing, but actually doing something about it is what separates the pros from the spammers. A high bounce rate is a huge red flag for inbox providers, telling them your email list isn’t well-maintained. Over time, that can seriously tank your ability to land in anyone’s inbox.
Think of these strategies as your game plan for keeping your email list healthy and your campaigns effective.
One of the best first moves you can make is to set up a double opt-in process. When someone signs up, they get a quick confirmation email with a link they have to click. It’s a simple but powerful way to make sure the email address is real and the person actually wants to hear from you, filtering out typos and bogus sign-ups right from the start.
Practice Proactive List Hygiene
You can’t just let your email list sit there and collect dust. Regular cleanups are absolutely essential if you want to keep your bounce rate low. Think of it like gardening: you have to pull the weeds (the bad emails) so the flowers (your real, engaged subscribers) have room to grow.
Here’s how to get your hands dirty:
- Remove Hard Bounces Immediately: The moment an email hard bounces, it needs to be gone. Your system should automatically and permanently remove that address from your list. There’s zero value in trying to send to a dead end.
- Monitor Soft Bounces: A soft bounce here and there is no big deal. But if the same address keeps soft bouncing campaign after campaign, you’re likely looking at an abandoned inbox. It’s time to either try to win them back with a re-engagement campaign or cut them loose.
- Validate Before You Send: Before any big send, run your list through an email bounce checker or a free email validation tool. This quick pre-flight check catches typos, disposable addresses, and other duds before they can ever hurt your sender score.
An ounce of prevention is worth a pound of cure. Cleaning your list before you send is a whole lot easier than trying to fix a trashed sender reputation later on.
Warm Up Your Sending Infrastructure
If you’re sending from a brand new domain or IP address, you can’t just go from zero to a hundred. Inbox providers get really suspicious when a new sender suddenly starts blasting out thousands of emails. It looks spammy, and they’ll treat you accordingly.
The key is to “warm up” your IP. You start small, sending to just a handful of your most active subscribers. Then, day by day, you gradually increase the volume over a few weeks. This slow-and-steady approach builds a track record with providers like Google and Microsoft, proving you’re a legitimate sender, not a spammer.
To manage your subscriber lists and keep bounce rates down as part of a bigger strategy, it’s worth looking into what good customer communication management software can do.
Frequently Asked Questions
Why do my emails bounce back?
Your emails bounce back when the recipient’s mail server refuses them. Usually the address doesn’t exist or has a typo, the recipient’s mailbox is full or their server is unavailable, or the server blocks your domain or IP because of a poor sending reputation or missing SPF, DKIM and DMARC records. The bounce message’s SMTP code tells you which.
What is the difference between a hard bounce and a soft bounce?
A hard bounce is a permanent failure, such as an address that doesn’t exist, and comes with a 5xx SMTP code. Stop emailing that address immediately. A soft bounce is a temporary failure, such as a full mailbox or busy server, and comes with a 4xx code. Your sending platform retries it automatically.
If an email address doesn’t exist, will it bounce back?
Usually yes, within seconds or minutes, with a code like “550 5.1.1 user unknown”. The exception is a catch-all domain, which accepts mail for any address at that domain. Mail to a non-existent address there may be accepted and then silently discarded or bounced later, which is why catch-all addresses need separate handling.
Can a soft bounce turn into a hard bounce?
Yes. If the same address keeps soft bouncing, the mailbox is probably abandoned, and many providers eventually delete those mailboxes, after which they hard bounce. Suppress an address after three to five soft bounces in a row.
What is an acceptable email bounce rate?
Keep your hard bounce rate under 2% of each send, and ideally under 1%. Email platforms watch hard bounces closely, and many will review or suspend accounts that stay above that, because high permanent failures suggest an old or purchased list. Soft bounces can spike briefly without meaning anything is wrong with your list.
What’s the difference between a bounce and a block?
A bounce is any delivery failure reported back to you. A block is a bounce caused by the receiving server refusing you because of your IP or domain reputation, not because the address is bad. Blocks can show up as temporary 421 or 451 deferrals, or as permanent 550 or 554 errors mentioning a policy, “access denied” or a blocklist such as Spamhaus. The fix is reputation work, not list cleaning: start with an email blacklist check.
Find the addresses that would bounce before you send with our free email bounce checker, or verify a whole list.
