What Is an Email Bounce and How Do You Reduce It?
A bounce is a message that could not be delivered. Learn the two types, what causes them and the steps that bring your rate down.
An email bounce is a message that the receiving server refused or could not deliver. The sender gets a notice, called a bounce message or a non-delivery report, that explains why. Bounces are normal in small numbers and harmful in large ones.
The two types
- Hard bounce: a permanent failure. The mailbox does not exist, the domain is wrong or the server refuses the sender. Stop sending to the address. See the error code library for codes such as 550 5.1.1.
- Soft bounce: a temporary failure. The mailbox is full, the server is busy or the message was delayed. Retry, and stop only if it keeps happening.
Typical causes
- Typos in addresses entered by hand.
- Old lists where people left or mailboxes were closed.
- Purchased or scraped lists.
- Missing SPF, DKIM or DMARC, which makes servers refuse your mail.
- A sending IP or domain on a blocklist.
- Sending too fast from a new domain.
What a healthy rate looks like
Aim for a hard bounce rate that stays well below one percent on a clean list, and keep a close eye on anything above two percent. Providers treat a rising bounce rate as a sign of careless sending.
How to reduce bounces
- Verify before you send. Remove invalid addresses with bulk email verification.
- Check at sign-up. Catch typos while the person is still on the form.
- Authenticate your domain. Use the SPF, DKIM and DMARC checker to confirm.
- Remove hard bounces immediately from every list and automation.
- Warm up new domains gradually.
- Re-check old lists before any big send.
Read the message
The bounce message carries a code and a sentence. Look the code up in the email error codes to learn whether the address is bad or your setup is. A single address can be tested with the free email checker, and plans are on the pricing page.
Reading a bounce message
A bounce message has three parts worth reading: the status code, the address that failed and the explanation from the remote server. The code tells you the type:
- Codes starting with 5 are permanent. Stop sending.
- Codes starting with 4 are temporary. Retry.
- Codes starting with 2 mean success.
The second group of numbers adds detail, for example 5.1.1 for a bad mailbox, 5.2.2 for a full mailbox and 5.7.1 for a policy refusal.
A simple decision table
- 5.1.1, 5.1.2, 5.2.1: remove the address.
- 5.7.1, 5.7.26: fix your setup, not the list. Check SPF, DKIM and DMARC with the checker.
- 4.2.2, 4.4.1, 4.7.0, 4.7.1: retry later; stop only after repeated failures.
What to do after each campaign
- Export the bounce report from your sending platform.
- Remove permanent bounces from every list.
- Move repeated soft bounces to a quiet segment.
- Look at bounces by domain: many failures at one domain can point to a block or a setup issue.
- Compare the rate with the previous campaign.
Prevention beats cure
Most hard bounces come from addresses that were never checked. Verify first with bulk email verification, keep typos out with a check at sign-up and re-verify before big sends. The full list of codes with fixes is in the email error codes library.
Bounce messages are free diagnostics
Every bounce comes with a code and a short explanation from the receiving server. Group them by reason once a week: unknown user, full mailbox, blocked by policy, temporary failure. The biggest group tells you where to act, and it is rarely the one you expected.
Track the trend
Plot the bounce rate of each campaign on a simple line chart. A flat or falling line means your habits work; a rising line means something changed in your list, your sources or your sending, and it is time to look.
What is happening when a message bounces
When you send a message, your server hands it to the recipient's server. If the receiving server refuses it, either immediately or after trying, it returns a notice to the sender. That notice is the bounce. It contains a code and a short explanation, and reading it is the quickest way to learn what went wrong. Bounces are not an error in your system; they are information about your list or your sending setup.
The most common causes in practice
- The address does not exist. A typo, a closed account or an invented address. This is the largest group.
- The domain is wrong. A mistyped domain or one that has expired.
- The mailbox is full or disabled. Usually temporary, but permanent if the mailbox is abandoned.
- The message is too large or has content the receiver rejects.
- Your sender reputation is poor. The receiver refuses the message because of who you are, not because of the address.
- Your authentication is missing or broken. SPF, DKIM or DMARC failures can lead to rejection.
Only the first three are about the address. If you treat every bounce as an address problem you may remove good contacts while the real cause, your reputation or authentication, stays unfixed.
How bounces affect delivery
Mailbox providers watch the share of your messages that bounce. A high rate suggests that you do not manage your list, and they respond by filtering more of your mail to the junk folder or throttling it. Because the effect builds slowly, many senders notice only when open rates fall. Keeping the bounce rate low protects every message you send, not only the ones that bounce.
A reduction plan you can follow
- Verify addresses at sign-up so bad ones never enter the list.
- Verify any imported or old list before sending to it.
- Remove hard-bounced addresses after the first bounce and keep a record.
- Retry soft bounces a limited number of times, then suppress.
- Check your authentication records once a quarter.
- Review each campaign's bounce report and note the cause of every group.
When the rate stays high
If bounces remain high after cleaning, the cause is usually the source: an acquisition channel that produces poor addresses, a form without validation, or a purchased list. Find which source the bounced addresses came from and fix or stop it. Verification removes the symptoms, but the best result comes from fixing where the bad addresses enter.