Email bounces are the clearest signal a mailbox provider has that you are sending to addresses that do not exist, and few things damage deliverability faster. The good news is that most bounces are preventable, and you can reduce your email bounce rate well below the danger line with a little list hygiene and a verification step before you hit send. This guide covers what a bounce is, the difference between hard and soft bounces, why a high rate wrecks your sender reputation, and how verifying and re-verifying lists keeps the number low.
What an email bounce is, and what a healthy rate looks like
An email bounce happens when a receiving mail server refuses your message and returns it instead of delivering it. Your bounce rate is simply the share of messages that bounce out of the total you send, and mailbox providers watch it closely as a proxy for how carefully you manage your list. There is no single official threshold, but as a rough guide a bounce rate under about 2 percent is usually healthy, anything above 3 to 5 percent starts to draw throttling or filtering, and a spike into double digits can get a sending domain or IP flagged quickly. These numbers vary by provider, but the direction is always the same: lower is safer.
Hard bounces vs soft bounces
Not every bounce means the same thing. A hard bounce is permanent: the address does not exist, the domain has no mail server, or the mailbox has been shut off, and the server is telling you plainly that it will never accept mail for that address. A soft bounce is temporary: the mailbox is full, the server is briefly down, the message is too large, or the receiver is greylisting you. Providers tolerate the occasional soft bounce, but repeated hard bounces are the ones that erode your reputation, because they prove you are mailing addresses you never checked.
| Bounce type | What it means | Common causes | What to do |
|---|---|---|---|
| Hard bounce | Permanent failure, the address will never accept mail | Address does not exist, domain has no mail server, mailbox disabled or closed | Remove it from your list and do not retry |
| Soft bounce | Temporary failure, delivery may succeed later | Mailbox over quota, server down or overloaded, message too large, greylisting | Retry a few times, then treat a persistent soft bounce as a hard one |
Bounces behave a little differently when you are doing outbound to people who never opted in, where list accuracy matters even more. For the full picture, see bounce rate in a cold email campaign.
Why a high bounce rate hurts your sender reputation
Mailbox providers build a reputation score for every sending domain and IP, and bounces are one of the heaviest inputs. A high hard-bounce rate tells Gmail, Outlook and Yahoo that you are either buying lists, letting your data go stale, or not verifying what you collect, and all three are hallmarks of spam. Once your reputation drops, the damage is not limited to the bad addresses: your legitimate mail to real, engaged recipients starts landing in spam too, because the provider has decided your stream as a whole is risky.
Bounces also raise the odds of hitting a spam trap, an address that exists only to catch senders with poor hygiene. Some traps are recycled addresses that now hard-bounce, others are planted and never bounce at all, and hitting either can get you listed on a blocklist that is slow to leave. Keeping your bounce rate low is the single clearest way to signal that you mail a clean, consenting list.
How to reduce your email bounce rate with verification
The most reliable way to reduce your email bounce rate is to stop sending to addresses that were always going to bounce, and that means verifying them before they ever reach your sending tool. Email verification checks each address without sending a message: it looks up the domain's mail servers, opens an SMTP conversation with the right one, asks whether it would accept mail for that address, and hangs up before anything is delivered. Nobody on your list receives an email during the check.
Sends Verified scores eight signals for every address (syntax, domain, mail server, mailbox, catch-all, disposable, role and spam traps) and returns a clear category you can act on. The categories that matter most for bounce prevention are the ones that flag an address as undeliverable before you send:
| Result | Will it bounce? | How to treat it |
|---|---|---|
| Safe | Unlikely, the mailbox exists and accepted the check | Keep and send |
| Role | No, but it is a function address like support@ | Keep if you intend to mail roles, otherwise review |
| Catch-all | Uncertain, the domain accepts any address | Send with care; Microsoft 365 domains are confirmed further |
| Inbox full | Likely a soft bounce right now, the mailbox is over quota | Hold and recheck later |
| Disposable | Yes, it is a throwaway inbox | Remove |
| Invalid | Yes, it is not registered or has no mail server | Remove |
| Disabled | Yes, the provider switched the account off | Remove |
| Spam trap | Do not send, it is a typo of a big provider or a known trap | Remove immediately |
Pulling the Invalid, Disabled, Disposable and Spam trap addresses out before a send is where most of the bounce-rate reduction comes from. Catch-all domains accept any address, so a mailbox cannot always be confirmed by SMTP alone. Sends Verified tests them with a made-up address first, so a catch-all is flagged rather than passed off as Safe, and for Microsoft 365 catch-all domains it confirms the specific mailbox against the provider's directory and promotes it to Deliverable with a confidence score. When a server will not give a definite answer in time, the result is Unknown, and Unknown results are always free: the credit returns automatically, so you are never charged for an address the server refused to confirm.
Re-verify stale lists before you send
A clean list does not stay clean. People change jobs, companies fold, and mailboxes get closed, so a list that verified perfectly six months ago will have quietly decayed since. This is email list decay, and it is why a list you have not touched in a while can bounce even though every address was valid when you collected it. As a rough rule, a meaningful share of a B2B list goes stale every month, which adds up fast over a quarter.
The fix is to re-verify, not just verify once. A Safe result is a snapshot of the moment it was checked, and an address can still bounce later for sending-side reasons such as SPF, DKIM or DMARC misalignment, a blocklisted IP, a server temporarily refusing, or the mailbox simply closing after the check. Re-verify any list older than about three months before you mail it, and re-verify the inactive segment of your database more often than the part you email every week.
A workflow that keeps bounce rate low
Reducing bounce rate is less about one big clean-up and more about a habit. Verify addresses at the point of capture so a bad one never enters your database, run a full-list verification before any large or re-engagement send, and remove every Invalid, Disabled, Disposable and Spam trap result before the list reaches your sending platform.
For the mechanics, you have two routes. You can upload a CSV or TXT file, and the tool detects the email column and keeps every other column in the download, so your list comes back intact with a result on each row. Or you can call the API to verify addresses as they are collected, checking one at signup in real time and sending a large list as a single bulk task. Because big mail providers rate-limit how fast anyone can query them, a company-heavy list takes longer to finish, and greylisted or slow servers simply read as Unknown and cost nothing. Duplicates in a task are checked and charged once, so routine re-verification stays inexpensive.
Do those few things consistently and your bounce rate stays well inside the safe zone, your sender reputation holds, and the mail you actually care about keeps reaching the inbox.
FAQ
What is a good email bounce rate?
There is no universal standard, but a bounce rate under about 2 percent is generally considered healthy for most senders. Above roughly 3 to 5 percent, mailbox providers start to throttle or filter your mail, and a sudden spike into double digits can get a domain or IP flagged quickly. Opted-in lists tend to run lower than cold outbound, so judge against your own baseline too.
What is the difference between a hard bounce and a soft bounce?
A hard bounce is permanent: the address does not exist, the domain has no mail server, or the mailbox is disabled, and you should remove it and never retry. A soft bounce is temporary, caused by a full mailbox, a server that is briefly down, a message that is too large, or greylisting, and delivery may succeed on a later attempt. If an address soft-bounces repeatedly over several sends, treat it as a hard bounce and remove it.
Does email verification guarantee my emails will not bounce?
No, and any service that promises zero bounces is overselling. Verification removes the addresses that were always going to bounce, such as invalid, disabled, disposable and trap addresses, which is the large majority of the problem. A Safe address can still bounce later if the mailbox closes after the check or your own authentication, IP or server has a sending-side issue, so verification plus good sending practice is what keeps the rate low, not verification alone.
How often should I re-verify my email list?
Re-verify any list that is older than about three months before you send to it, because addresses go stale continuously as people change jobs and mailboxes close. Verify new addresses at the point of capture so bad data never builds up, and re-check your inactive or long-dormant segments more often than the contacts you email every week. A quick re-verification before a large or re-engagement campaign is the cheapest insurance against a reputation-damaging bounce spike.