What triggers a hard bounce
The most common causes are: the mailbox never existed or was deleted (550 5.1.1 User unknown), the domain itself doesn’t exist or has no mail server, or the receiving server has the sender’s domain/IP permanently blocklisted. All of these map to SMTP 5xx response codes in RFC 5321, which signal a permanent failure rather than a temporary one.
Why hard bounces matter more than soft bounces
Mailbox providers like Gmail and Yahoo track hard-bounce rate as a direct signal of list quality and sender hygiene. A high hard-bounce rate suggests the sender isn’t verifying addresses or removing invalid ones, which is treated as a strong spam-risk indicator — independent of how well-crafted the email content itself is.
The correct response to a hard bounce
Immediately suppress the address from future sends. Continuing to mail a hard-bounced address doesn’t just waste a send attempt — each repeated hard bounce further damages your domain and IP reputation with that specific receiving provider, and a pattern of ignored hard bounces across many addresses is one of the clearest signals ESPs and mailbox providers use to identify careless or malicious senders.
Hard bounce vs. invalid at verification time
Email verification run before sending catches most future hard bounces before they happen — an address classified “undeliverable” by a verifier would have hard-bounced had you mailed it. The two signals (pre-send verification and post-send bounce) should agree almost all the time; persistent disagreement usually points to a catch-all domain or a verification provider with poor catch-all handling.
Look up a specific bounce code
See the full SMTP bounce code reference for what specific codes like 550 5.1.1 (user unknown) or 550 5.7.1 (policy rejection) actually mean and whether to suppress the address.