Glossary
Definition
A hard bounce is a permanent email delivery failure. The message is rejected for good because the recipient address is invalid, the mailbox does not exist, or the domain cannot receive mail. Unlike a temporary glitch, a hard bounce will not resolve on a retry, so the address should never be mailed again.
We verify billions of email addresses, and the hard bounce is the failure we exist to prevent. It is the bluntest message a mail server can send back: this address is dead, do not try again. A single hard bounce is harmless, but a list full of them quietly destroys the sender reputation that decides whether any of your mail reaches the inbox. Here is what a hard bounce actually is, what causes it, and how to keep it out of your sends.
A hard bounce happens when a receiving mail server permanently rejects a message, returning a 5xxresponse code that means “this will never be deliverable.” Unlike a temporary failure, there is no point retrying, because the underlying condition will not change on its own. A handful of permanent conditions account for almost every hard bounce we see.
jhon@company.com or a guessed address that was never real.@ is misspelled, expired, or has no mail server (no MX record), so there is nowhere to deliver the message.In each case the server is certain the address cannot receive mail, so it closes the door for good rather than asking you to come back later.
The distinction matters because the two demand opposite responses. A hard bounce is permanent and final. A soft bounce is temporary: the mailbox is full, the server is briefly overloaded, the message is too large, or a greylist is asking you to retry. Soft bounces frequently clear on their own, and most email platforms automatically retry them for a day or two before giving up.
So you treat them differently. A soft-bounced address stays on your list and gets a few automated retries. A hard-bounced address should be suppressed immediately and never mailed again, because every repeat attempt is another guaranteed failure that counts against you. Confusing the two, and continuing to mail hard bounces as if they might recover, is one of the fastest ways to damage your standing with mailbox providers.
Mailbox providers like Gmail, Outlook, and Yahoo judge senders on behavior, and a high hard-bounce rate is one of the loudest negative signals there is. Sending repeatedly to invalid addresses is exactly what spammers do when they blast scraped or purchased lists, so providers read a spike in hard bounces as evidence that you have not verified who you are mailing. The point of email verification is to make sure that signal never fires.
Once your bounce rate crosses a provider threshold, the penalties stack up fast. They throttle how much of your mail they accept, divert more of it to the spam folder, and in the worst cases block your domain entirely. Because reputation is shared across a sending domain, those penalties hit your good mail too: the receipts, password resets, and newsletters your real subscribers actually want start landing in spam. As a rule of thumb, keeping hard bounces under 2 percent, and ideally under 1 percent, of any send is what keeps you on the safe side of those thresholds.
The damage compounds, too. A degraded reputation means even your valid mail gets less inbox placement, which lowers engagement, which providers read as a further quality problem. Hard bounces are how that downward spiral usually begins, which is why stopping them at the source is the highest-leverage thing a sender can do.
Every hard bounce is preventable, because every cause is detectable before you hit send. That is precisely what our engine does. Each address runs through nine checks, the same engine behind the free email checker and the paid API, that together catch the conditions that produce hard bounces.
It validates syntax to catch typos, confirms the domain resolves and publishes a real mail server, and runs an SMTP check to confirm the specific mailbox actually exists, all without sending a message. Invalid addresses, dead domains, and non-existent mailboxes are flagged as undeliverable so you can remove them before they ever bounce. The result is a list that lands well under a 1 percent bounce rate instead of the double-digit rate an unverified list can post.
Done consistently, verification turns the hard bounce from an expensive surprise into a non-event, and it protects the sender reputation you have spent real effort building. For teams verifying at scale, the volume tiers are on the pricing page.
Keep learning
A hard bounce sits inside a wider set of deliverability concepts. These are the terms most worth understanding next.
A temporary delivery failure, like a full inbox or a server that is briefly down.
A domain that accepts mail for any address, valid or not, hiding bad data in your list.
Throwaway addresses from temporary-mail services that self-destruct after minutes.
The protocol mail servers speak to hand a message from sender to recipient.
Confirming an address is real, reachable, and safe to send to before you send.
A shared inbox like info@ or support@ that belongs to a team, not a person.
Hard bounces come from addresses our engine flags in two seconds. Paste an address into the free email checker and see whether it is deliverable, before it ever costs you a bounce. No signup.
Common questions
The questions we get most about hard bounces, answered with the same logic our verification engine uses.
It means your email was rejected permanently and will never be delivered to that address. The most common reason is that the mailbox simply does not exist, usually because of a typo like jhon@company.com or because the person left and their account was closed.
A hard bounce is final. The receiving server is telling you, plainly, that this address is a dead end, so resending the same message will only produce another hard bounce.
A hard bounce is permanent: the address is invalid or the domain does not exist, so the failure will never clear. A soft bounce is temporary: the mailbox is full, the server is briefly down, or the message is oversized, and a later retry often succeeds.
The practical rule is to suppress hard-bounced addresses immediately and keep them out of every future send, while giving soft bounces a few automated retries before you give up on them.
The usual causes are all permanent conditions:
The local part is wrong and no such mailbox exists; the domain is misspelled or has no mail server; the account was deleted or deactivated; or the receiving server has flatly blocked your sender. In every case the address cannot accept mail, so the server returns a permanent 5xx rejection.
Yes, significantly. Mailbox providers treat a high hard-bounce rate as a signal that you are mailing a list you have not verified, which is a classic spammer pattern. They respond by throttling you, routing more of your mail to spam, or blocking you outright.
That is why a clean bounce rate is one of the most important deliverability metrics you control, and why verifying before you send matters so much.
Aim to keep hard bounces under 2 percent of a send, and ideally below 1 percent. Many mailbox providers start penalizing senders once the bounce rate climbs past a couple of percent, and some abuse thresholds trigger even lower.
A verified list routinely lands well under 1 percent, because the invalid and non-existent addresses that cause hard bounces are removed before the campaign ever goes out.
Verify every address before you send. Running a list through the free email checker flags invalid syntax, dead domains, and mailboxes that do not exist, which are the exact conditions that produce hard bounces.
For ongoing protection, add verification at the point of capture with the email verifier so bad addresses never enter your list, and re-verify older segments before you mail them again.
Always, and immediately. A hard bounce confirms the address is permanently undeliverable, so keeping it on your list only inflates future bounce rates and erodes your sender reputation with every send.
Most email platforms suppress hard bounces automatically, but the better fix is upstream: verify with our email verifier so those addresses are caught and removed before they ever cost you a bounce.
Occasionally, yes. An address that was valid can hard bounce later if the mailbox is deleted, the employee leaves, or the domain lapses. This is why a list decays over time, roughly a couple of percent every month, even if it was clean when you built it.
Periodic re-verification catches that decay. You can re-check any list against the same nine-stage engine described on the email verification page, and review volume tiers on the pricing page.