What is a hard bounce?
A hard bounce is a permanent delivery failure: the receiving server rejected the message and retrying won't change the answer. The usual causes are a mailbox that doesn't exist, a domain that doesn't exist, or a malformed address.
A hard bounce happens when the receiving mail server returns a permanent error, a reply code starting with 5, or when the domain can't receive mail at all. Your sending platform gets a bounce notice back, records the failure, and should never send to that address again.
Hard bounces are the bounce type mailbox providers pay most attention to, because a sender who keeps hitting mailboxes that don't exist is probably using an old, bought or guessed list. One or two per campaign is normal. A cluster of them points to a list problem.
Hard-bounce codes you'll see
SMTP replies come in two parts: a basic code like 550 and an enhanced status like 5.1.1. The middle digit of the enhanced code tells you what kind of problem it is.
| Code | Typical text | What it means | What to do |
|---|---|---|---|
550 5.1.1 | User unknown, mailbox not found | The mailbox doesn't exist | Remove the address |
551 5.1.6 | User not local, mailbox has moved | The recipient isn't on this server any more | Remove it, or update it if a new address is given |
553 5.1.3 | Mailbox name not allowed, bad address syntax | The address is malformed | Fix the typo or remove it |
5.1.2 | Bad destination system, host or domain not found | The domain doesn't exist or doesn't take mail | Remove it, or correct the domain |
552 5.2.2 | Mailbox full, over quota | Storage exceeded. Many servers send this as a temporary 452 4.2.2 instead | Hold and retry; remove it if it keeps failing |
550 5.7.1 | Rejected for policy reasons | A sender problem: reputation, authentication or content, not the address | Keep the contact; fix SPF, DKIM, DMARC or reputation first |
Exact wording varies by server. Read the enhanced code when it's there: 5.1.x is about the address, 5.2.x about the mailbox, 5.7.x about you.
How to fix a hard-bounce problem
- 01
Suppress, don't just delete
Put bounced addresses on a suppression list so they can't come back in with the next import.
- 02
Find the source
Group bounces by list, form or lead source. One bad source usually explains most of them.
- 03
Verify before the next send
Run the rest of that source through a bulk check and remove
undeliverablerows before they bounce too. - 04
Check for 5.7 rejections
If many bounces are policy blocks rather than unknown users, the list isn't the problem. Look at authentication and /glossary/sender-reputation.
How MailVet predicts a hard bounce
Verification asks the receiving server the same question a send would, without sending anything. When the server rejects the mailbox, MailVet returns undeliverable with reason mailbox_not_found. A domain that doesn't exist or has no mail servers returns invalid_domain, and a malformed address returns invalid_syntax before any network check, free.
One case a basic check misses: on a catch-all domain the server accepts every address, so a dead one passes and bounces later. MailVet checks those too and returns catch_all_no_mailbox when no real mailbox is behind the address. See /glossary/catch-all-email.
Hard bounce questions
What is the difference between a hard bounce and a soft bounce?
A hard bounce is permanent: the address or domain can't receive mail, so retrying won't help. A soft bounce is temporary, such as a full mailbox or a busy server, and the sending server will usually retry. Hard bounces should be suppressed straight away.
Should I remove hard-bounced email addresses?
Yes, for address problems like unknown users and domains that don't exist: suppress them so they're never mailed again. The exception is a policy rejection with a 5.7.x code, which is about your sending, not the address.
Can a hard-bounced address become valid again?
Occasionally, for example when a company re-creates a mailbox or a lapsed domain comes back. It's rare, and an address that bounced for a long time and then starts accepting mail again is exactly what a recycled spam trap looks like. Re-verify before mailing any old bounce.
How many hard bounces are too many?
There's no official number. A common rule of thumb is to keep total bounces under 2% of a send, with hard bounces well below that. A sudden jump on one campaign matters more than the exact figure: it usually means one bad list source.
Catch the bounces before your sending tool does
Upload your list and remove undeliverable rows, including dead addresses on catch-all domains that basic checks pass.
Related
Last updated November 13, 2026