The difference in one line
A hard bounce means the message can never be delivered to that address as it stands: the mailbox does not exist, the domain is wrong, or the server refuses mail for it. A soft bounce means delivery failed this time but might succeed later: the mailbox is full, the server is down, or the message was temporarily deferred.
- Hard bounce examples: a mistyped address, a deleted account, a domain with no mail server.
- Soft bounce examples: a full mailbox, a server outage, a greylisting delay, a message that was too large.
How to read the code
SMTP replies start with a three-digit code. Codes beginning with 5 are permanent failures and codes beginning with 4 are temporary ones. Many servers add an enhanced status code such as 5.1.1, which usually means the recipient address does not exist.
In practice, 550 with a message like user unknown is the classic hard bounce. 452 (insufficient storage) or 421 (service not available) are typical soft bounces. Servers are not always consistent, and some return a 5xx code for what is really a temporary condition, so the wording of the message matters as much as the number.
550 5.1.1 The email account that you tried to reach does not exist -> hard
554 5.7.1 Message rejected as spam -> hard (policy)
452 4.2.2 The email account is over quota -> soft
421 4.7.0 Try again later -> softWhat to do with each
Suppress hard bounces immediately and permanently. There is no reason to try an address again once the server has said it does not exist, and repeated attempts are exactly what mailbox providers read as poor list hygiene.
Retry soft bounces a few times over a day or two. Most email platforms do this automatically. If the same address keeps soft bouncing across several campaigns, stop sending to it, because a mailbox that is permanently full or abandoned is as useless as a deleted one.
Why it matters for deliverability
Mailbox providers watch how often your mail bounces. Google and Yahoo both publish requirements for bulk senders, including keeping spam complaints low and authenticating your domain, and a high hard-bounce rate is one of the clearest signs of an unmaintained list. The simplest way to keep it low is to avoid sending to bad addresses in the first place.
The cheapest bounce is the one you never send. Verify addresses before the first message, not after the first bounce.
How verification reports it
Email verification checks the same things a receiving server would tell you, but before you send. VeriDock returns undeliverable for addresses that would hard bounce, with a reason such as invalid_syntax, no_mx_record or rejected_email. A full mailbox is also reported as undeliverable with the reason mailbox_full, even though some platforms count it as a soft bounce, so read the reason code if you want to treat it differently.
When the receiving server will not give a clear answer, the result is unknown rather than a guess. Unknown results are never billed, and you can retry them later or treat them as risky.
Key takeaways
0/4Try it on a real address
Run syntax, DNS, MX, disposable, and role checks on any address. No signup needed.
Enter an address and press Check.
Runs real syntax, DNS and mail-server checks.
This demo checks syntax, domain, mail server, disposable and role-address rules. Sign up free for live mailbox checks.
Frequently asked questions
Verify addresses with one API call.
250 free checks to start, no card required. Unknown results are never billed.
Put it into practice
Keep reading
- GuidesHow to Reduce Your Email Bounce Rate
- GuidesWhat Is Email List Hygiene and Why Does It Matter?
- GuidesEmail Verification Results Explained: What Each Status Means
- GuidesSpam Traps Explained: Types, Risks and How to Avoid Them
- BusinessHow Often Should You Verify Your Email List?
- GuidesWhat Is a Catch-All Email Address?
- Guides550 5.1.1 and Other SMTP Bounce Codes: When to Suppress