A hard bounce is a permanent rejection, and the address should never be mailed again.
Key points
- Hard bounces are signaled with a permanent 5xx reply during the SMTP conversation, often with an enhanced status code such as 5.1.1 (bad destination mailbox) [1][2].
- Common causes are a mistyped or deleted mailbox, a domain with no working MX Record, or a policy block against the sender [2][3].
- Every hard-bounced address should go straight onto a Suppression List so it is never retried [4].
- A high share of hard bounces inflates your Bounce Rate and tells mailbox providers the list is old or unverified, which hurts Sender Reputation [3][5].
- Running Email Verification before sending, and removing stale contacts affected by Data Decay, is the main way to prevent hard bounces [5].
How a hard bounce happens
When your server hands a message to the recipient's server over SMTP, the receiving side answers each command with a three-digit reply code. RFC 5321 defines codes starting with 5 as permanent negative completions, meaning the same request will fail again if repeated [2]. RFC 3463 adds enhanced status codes that explain the reason: 5.1.1 means the mailbox does not exist, 5.1.2 points to a bad destination domain, and 5.7.x codes signal a security or policy refusal [1]. If the rejection happens after the message was accepted, the server instead returns a bounce message to the Return-Path address. Either way, the result is the same: the message was not delivered and will not be delivered by trying again later, unlike a Soft Bounce.
Why hard bounces damage deliverability
Mailbox providers read bounces as a signal of list quality. A sender whose messages keep hitting nonexistent addresses looks like someone mailing a purchased or scraped list, which is also the pattern that leads to Spam Trap hits. Gmail's sender guidelines tie inbox access to sound list practices and warn that poor practices lead to rate limiting or rejection [3]. Email platforms commonly review accounts whose bounce rate climbs above a few percent, and for Cold Email a common working target is to stay below 2 percent. Because a single campaign to an outdated list can spike bounces at once, hard bounces are one of the fastest ways to erode Domain Reputation and Inbox Placement, especially on a new or recently warmed domain.
Preventing and handling hard bounces
Prevention starts before the first send. Verify addresses, especially ones guessed by an Email Finder, with an Email Verification step, be cautious with a Catch-All Email Address domain that accepts everything at the connection stage, and refresh contact data regularly because people change jobs and mailboxes are deleted. After sending, parse bounce responses and add every hard-bounced address to a Suppression List immediately; services such as SendGrid do this automatically and block future sends to those addresses [4]. Do not re-add suppressed contacts through a later import. It also helps to separate policy rejections (5.7.x) from unknown-user errors (5.1.1): the first points to an authentication or reputation problem with your mail, such as missing SPF (Sender Policy Framework) or DKIM (DomainKeys Identified Mail), while the second points to bad data [1][3].
Related terms
Outreach without the busywork.
PineLead finds new B2B prospects every day, qualifies them against your criteria and writes the first email in your voice. You approve — PineLead sends.
Start free with 100 credits →