# Hard bounce

> A permanent delivery failure, commonly caused by an invalid address or a definitive policy rejection.

- **Category:** Deliverability
- **Updated:** July 2026
- **Canonical page:** [https://emailbump.com/glossary/hard-bounce](https://emailbump.com/glossary/hard-bounce)

## Definition

A hard bounce is a delivery failure the sender classifies as permanent. SMTP 5xx responses often indicate permanent failure, but the enhanced status code and diagnostic text are more useful than the label alone.

An address that does not exist should usually be suppressed immediately. Some permanent policy rejections can be specific to the message, domain, or sender rather than proof that the recipient address is invalid.

## Why it matters

Repeatedly sending to known-invalid recipients wastes capacity and signals weak audience controls. Correct classification protects reputation while avoiding the accidental suppression of valid recipients after ambiguous failures.

## How it works

1. The receiving server rejects the recipient or message with a permanent response.
2. The sending provider parses the SMTP and enhanced status codes.
3. The event is classified by cause, such as unknown user, policy, authentication, or content.
4. The address or route is suppressed when the cause justifies it.

## Example: Unknown recipient

```text
550 5.1.1 The email account that you tried to reach does not exist

Class: permanent
Action: suppress this address and inspect how it entered the list
```

## Common mistakes

- Retrying a confirmed nonexistent address.
- Treating every 5xx policy response as an invalid recipient.
- Deleting bounce evidence instead of retaining classification and source context.
- Importing old lists without validating consent and recent reachability.

## Key takeaways

- Suppress confirmed unknown users promptly.
- Read the enhanced status code and diagnostic.
- Track bounce source so acquisition problems can be fixed.

## Related definitions

- [Soft bounce](https://emailbump.com/glossary/soft-bounce.md) — A temporary delivery failure that may succeed when retried under a controlled policy.
- [Suppression list](https://emailbump.com/glossary/suppression-list.md) — A durable do-not-send control containing recipients or destinations that must not receive certain email.
- [List hygiene](https://emailbump.com/glossary/list-hygiene.md) — The ongoing practice of keeping audience permission, reachability, source, and engagement data trustworthy.
- [Email deliverability](https://emailbump.com/glossary/email-deliverability.md) — The ability to reach the part of the mailbox where a wanted recipient can find and act on an email.

## Related guides

- [Gmail reputation-based bounces: diagnose, contain, and recover](https://emailbump.com/blog/gmail-reputation-bounces.md) — An incident guide to Gmail 4.7.x and 5.7.x responses, sender-level classification, safe retries, Postmaster Tools, abuse containment, and reputation recovery.
- [Email bounces: how to classify, retry, suppress, and recover](https://emailbump.com/blog/email-bounce-handling-guide.md) — A practical operating guide to SMTP failures, enhanced status codes, retries, suppression, webhooks, and the product workflows that protect sender reputation.
- [Why customers mark transactional email as spam—and how to stop it](https://emailbump.com/blog/reduce-transactional-email-spam-complaints.md) — An operational guide to expectation, message purpose, notification controls, duplicate prevention, form abuse, suppression, and complaint monitoring.
- [The email deliverability checklist for every campaign](https://emailbump.com/blog/email-deliverability-checklist.md) — A practical pre-send routine for protecting your sender reputation and reaching more inboxes.

## Primary sources

- [RFC 3463: Enhanced mail system status codes](https://www.rfc-editor.org/rfc/rfc3463)