Topic · Deliverability
Hard bounce
A hard bounce is a delivery failure typically considered permanent, such as an invalid recipient mailbox or policy rejection.
How it works
The receiving SMTP system returns a permanent failure response or a delivery status notification signals non-delivery.
What can go wrong
Repeated attempts to invalid mailboxes can harm sender reputation and waste resources.
What to check or do
Classify bounce codes and suppress confirmed invalid recipients rather than retrying indefinitely.
How to investigate Hard bounce
- Signal to investigate
- A campaign repeatedly sends to an address returning enhanced SMTP status 5.1.1 after the recipient stage.
- Evidence to collect
- Inspect enhanced SMTP status, diagnostic text, retry history and the ESP suppression state.
- Common wrong conclusion
- Every 5xx response should not be casually treated as a permanently nonexistent mailbox; policies vary.
How to interpret the evidence
Hard-bounce categories often include permanent mailbox or domain failures, but receivers can use 5xx for policy rejections that need a different remedy.
What to change and how to verify it
Classify by status and context; suppress invalid addresses, but investigate authentication and policy failures separately.
Put this into practice
Run a focused check, then explore protection if your domain needs it.