What is a hard bounce in email?
A hard bounce is an email that the recipient's mail server permanently rejects, so it will never be delivered. The usual cause is an address or domain that does not exist, and the server returns a 5xx error such as 550 5.1.1 (user unknown). Remove hard-bounced addresses from your list right away, because repeated sends to them damage sender reputation and deliverability.
| Hard bounce | Soft bounce | |
|---|---|---|
| What it means | Permanent delivery failure | Temporary delivery failure |
| Typical SMTP code | 5xx, for example 550 5.1.1 | 4xx, for example 421 or 451 |
| Common causes | Address or domain does not exist, permanent block | Mailbox full, server busy, message too large, greylisting |
| Retry? | No. Suppress the address | Usually retried automatically for a period |
| Effect on reputation | Strong negative signal if frequent | Mild unless it repeats for the same address |
What a hard bounce is
When you send an email, the receiving mail server either accepts it or rejects it. A hard bounce is a rejection the server marks as permanent: the message cannot be delivered now and will not be deliverable later either. Your email service provider receives a non-delivery report, often called a bounce message or NDR, with an SMTP status code that starts with 5.
The most common example looks like this:
550 5.1.1 The email account that you tried to reach does not exist.
The 5 at the start of the code means permanent failure. A code that starts with 4 means a temporary failure, which is a soft bounce. The exact wording varies by provider, but the class of the code tells you which kind of bounce you are dealing with.
Common causes of a hard bounce
Most hard bounces come from a short list of reasons:
- The mailbox does not exist. The address was mistyped, guessed from a pattern that the company does not use, or never existed. Status code
5.1.1is typical. - The person left the company. In B2B this is a frequent cause. When someone changes jobs, their old work mailbox is usually deactivated, and mail to it starts hard bouncing.
- The domain does not exist or cannot receive mail. The domain has lapsed, was misspelled (for example
northwind.cminstead ofnorthwind.co), or has no MX record. Status code5.1.2is common here. - A permanent policy block. Some servers reject mail permanently because of the sender's reputation, authentication failures or content rules, often with a
5.7.xcode. Many senders treat these separately from "address does not exist" bounces, since the address itself may be fine.
Classification is not perfectly consistent across providers. A full mailbox, for example, sometimes returns a 5xx code but is usually handled as a soft bounce because it can clear up. Check how your sending tool labels each code rather than assuming. For a wider look at every reason mail comes back, see why do emails bounce.
Why hard bounces hurt deliverability
Mailbox providers watch how many of your messages go to addresses that do not exist. A high hard bounce rate suggests the list was bought, scraped or left to go stale, which are patterns associated with spam. The result can be more of your mail landing in spam folders, throttling, or outright blocks, including for recipients whose addresses are valid.
Hard bounces also distort your campaign numbers. Open, reply and click rates are calculated on a smaller real audience than you think, and sequences keep scheduling follow-ups to people who will never see them.
A commonly cited rule of thumb is to keep total bounces under about 2% of sends, with hard bounces as close to zero as you can manage. Our page on what a good email bounce rate is covers benchmarks in more detail.
What to do after a hard bounce
- Suppress the address immediately. Do not retry it. Most sending platforms add hard bounces to a suppression list automatically; confirm yours does, and make sure the suppression syncs back to your CRM so another tool does not re-import the address.
- Read the code. A
5.1.1means the mailbox is gone. A5.7.xpolicy block points to a sender problem (authentication, reputation or content) that you should investigate, because it may affect other recipients too. - Find the person's current address, if they moved. If the contact changed jobs, the old address is dead but the person may still be a good prospect at their new company. Look up their current role and a new work email, then verify it before sending.
- Look for patterns. If many bounces come from one source, list or import date, that source is the problem, not the individual addresses.
How to prevent hard bounces before you send
The reliable fix is to verify addresses before they enter a campaign. Email verification checks syntax, confirms the domain has working mail servers, and then asks the mail server whether a specific mailbox exists, without sending a message. Our guide on how email verification works walks through each step.
Verification cannot give a clear answer for every address. Catch-all domains accept mail for any address at the domain, so the server never confirms whether a specific mailbox exists. Some of those messages are delivered and some bounce later. Treat them as a separate, lower-volume segment rather than as valid. See what is a catch-all email for how to handle them.
Timing matters too. An address that verified six months ago may hard bounce today because the person left. Re-verify lists that have been sitting unused, and re-check right before a large send.
Example
Maya Chen, VP Revenue Operations at Northwind Analytics, is on a prospect list as maya.chen@northwind.co. If she leaves Northwind and her mailbox is deleted, the next email in a sequence returns 550 5.1.1 user unknown. That is a hard bounce. The right response is to suppress the old address, then check whether she has a new role and a new verified work email elsewhere.
Where Leadsets fits
If you build lists with an AI agent or an API, Leadsets can reduce hard bounces at the source. Its verify_email tool runs a verification waterfall (syntax, DNS and MX, a mailbox-level check, and a second opinion on uncertain or catch-all results) and labels each address verified, catch-all, unknown or invalid with a confidence score. Uncertain results are never rounded up to valid, and addresses labelled invalid are never served as contact emails. Emails returned by enrich_person are already verified.
The free skills library includes a pre-send campaign check and a bounce recovery skill that looks up current, verified emails for contacts who moved. You can try it on the email verification page with 1,000 free records. No verification provider can promise zero bounces, and Leadsets does not.
Questions and answers
What is the difference between a hard bounce and a soft bounce?
A hard bounce is a permanent delivery failure, usually because the address or domain does not exist, and it returns a 5xx SMTP code. A soft bounce is temporary, such as a full mailbox or a busy server, and returns a 4xx code. Soft bounces are usually retried; hard bounces should be suppressed.
Should I resend an email that hard bounced?
No. A hard bounce means the server has permanently refused the address, so resending will bounce again and adds to your bounce rate. Suppress the address and, if the person changed jobs, look up and verify their new email instead.
Do hard bounces hurt sender reputation?
Yes, when they are frequent. Mailbox providers read a high rate of mail to non-existent addresses as a sign of a poor or stale list. That can push more of your mail to spam or lead to throttling and blocks.
What is an acceptable hard bounce rate?
There is no single official number, but a common rule of thumb is to keep total bounces under about 2% of sends and hard bounces as close to zero as possible. Verifying lists before sending is the main way to stay there.
Why did a verified email address hard bounce?
Verification reflects the moment it was run, and mailboxes can be deleted afterwards, often when someone leaves a company. Catch-all domains also cannot be confirmed at the mailbox level, so some of their addresses bounce later. Re-verify older lists before large sends.
What does the error 550 5.1.1 mean?
It means the receiving server reports that the mailbox does not exist. It is one of the most common hard bounce codes. The address should be removed from your sending list.
Go deeper