Hard bounce vs soft bounce: what they mean and what to do

A bounce is a delivery failure -- your email could not be delivered to the recipient's mail server. Bounces are divided into two categories based on whether the failure is permanent or temporary. Getting this distinction right matters because the correct response to each is different, and handling them incorrectly damages your sender reputation.

The difference

The practical difference is what you do next. A hard bounce means the address is permanently undeliverable and must be removed from your list immediately. A soft bounce means delivery failed this time but may succeed on a future attempt -- though repeated soft bounces from the same address often indicate a real problem worth investigating.

What the SMTP codes actually tell you

When a mail server rejects a message, it returns a three-digit SMTP response code. The first digit tells you the category: 5xx codes are permanent failures (hard bounces), 4xx codes are temporary failures (soft bounces).

Hard bounces in practice

A hard bounce tells you the address is permanently undeliverable. The correct response is immediate suppression -- remove the address from your active list and do not attempt to send to it again.

This is not optional. Continuing to send to hard-bounced addresses is one of the fastest ways to damage your sender reputation. Gmail, Microsoft, and Yahoo all track bounce rates as a signal of list quality. Keep your hard bounce rate below 2% -- above that, you will see inbox placement deteriorate. Above 5%, you risk account suspension from most sending providers.

Common causes of hard bounces

• Typos at signup -- gmai.com instead of gmail.com, missing dots, transposed characters
• Address no longer exists -- someone left a company and their email was deactivated
• Domain no longer exists -- a company shut down or changed domains
• Role addresses that were closed -- info@ or sales@ addresses that were retired
• Old lists -- email addresses change over time; a list that is two years old will have meaningfully more invalid addresses than a fresh one

Soft bounces in practice

A soft bounce means delivery failed this time for a temporary reason. Most sending platforms retry soft bounces automatically over a period of hours or days. That is usually the right response for server-side temporary failures like 421 or 450 codes.

However, soft bounces need monitoring. An address that soft bounces repeatedly -- say, three or more times over several sends -- is no longer behaving like a temporary problem. A mailbox that has been full for three months is probably abandoned. An address that consistently returns 452 is worth suppressing.

Soft bounces that are really sender problems

Not all soft bounces are about the recipient's mailbox. Some temporary failures point at your own sending infrastructure:

• IP or domain on a block list -- returns a 4xx code from the receiving server but the problem is on your side
• Message too large -- exceeding size limits returns a temporary failure on some servers
• Rate limiting -- sending too fast to a provider triggers temporary throttling responses
• Authentication failures -- some servers return soft failures when SPF or DKIM checks fail

If you see a sudden spike in soft bounces across many different addresses, the problem is almost certainly on your side -- check your sending IP reputation, authentication configuration, and whether you have hit a sending rate limit.

What bounce rates to watch

How to keep bounce rates low

Verify addresses before sending. Email verification checks whether an address exists before you send to it. Running verification on a new list or before a first send catches invalid addresses before they bounce. No verification service is perfect -- catch-all domains and some corporate servers return valid responses for any address -- but verification catches the obvious invalids and typos.

Use confirmed opt-in for new subscribers. Double opt-in -- sending a confirmation email before adding someone to your list -- ensures the address is real and the inbox is accessible. It adds friction to signup but removes invalid addresses at the point of entry rather than after bouncing.

Suppress bounced addresses permanently. Hard bounces should never be retried. Most platforms maintain a suppression list automatically -- make sure yours does and that suppressed addresses stay suppressed even if you import the same list again later.

Watch your engagement over time. A list that was clean six months ago has more invalid addresses now. Subscribers leave companies, abandon email addresses, and change providers. Regularly removing disengaged subscribers -- those who have not opened in 12 months, for example -- catches address decay before it shows up as bounces.