Hard bounce vs soft bounce: what is the difference?

What a hard bounce actually is

A hard bounce is a permanent, unrecoverable rejection. The receiving server is telling you, in effect, that this message will never be deliverable no matter how many times you try. In SMTP terms these arrive as 5xx errors — the 500-range response codes that signal a permanent failure.

The moment you receive a hard bounce, that address should be suppressed forever. Continuing to send to it does nothing but signal to inbox providers that you don't maintain your list, which is one of the fastest ways to end up in the spam folder for everyone else.

• The mailbox doesn't exist (the classic 'user unknown' / 550 5.1.1).
• The domain doesn't exist, has no mail servers, or has been abandoned.
• The recipient's server has blocked your domain or IP outright.
• The address is malformed or was mistyped at signup (john@gmial.com).

What a soft bounce actually is

A soft bounce is a temporary delivery failure. The address and domain are usually fine — something just got in the way of this particular delivery. These typically show up as 4xx SMTP errors, the 400-range 'try again later' codes. Most email platforms will automatically retry a soft-bounced message several times over 24–72 hours before finally classifying it as undeliverable.

Because the cause is transient, a soft bounce is not a reason to remove an address on the first occurrence. It's a reason to watch it.

• The recipient's mailbox is full and can't accept more mail.
• The message is too large for the recipient's size limit.
• The receiving mail server is temporarily down or overloaded.
• Greylisting — the server deliberately defers a first attempt from an unknown sender.
• The message was flagged by a content or spam filter.

The key differences at a glance

• Permanence — hard bounce = permanent; soft bounce = temporary.
• SMTP code — hard bounces return 5xx errors; soft bounces return 4xx errors.
• Retry behaviour — soft bounces are retried automatically; hard bounces are not.
• Your action — remove hard bounces immediately; monitor soft bounces and remove only after repeated failures.
• Reputation impact — a high hard-bounce rate is far more damaging, because it signals you're sending to a list you never cleaned.

Why the distinction matters for deliverability

Mailbox providers like Gmail, Outlook, and Yahoo treat your bounce rate as a proxy for how carefully you manage your audience. A clean sender rarely hits addresses that don't exist; a careless one hits them constantly. So a rising hard-bounce rate directly erodes the reputation of your sending domain and IP — and once that reputation drops, even your valid recipients start seeing your mail land in spam.

The widely cited industry guidance is to keep your overall bounce rate under about 2%, with hard bounces the number to guard most closely. Some hard bounces are also spam traps — addresses planted specifically to catch senders who don't clean their lists — and hitting those can get you blocklisted outright.

Soft bounces matter too, but differently. An occasional soft bounce is normal and harmless. A soft bounce that keeps recurring for weeks, however, is really a hard bounce in slow motion — the mailbox has probably been abandoned — and should eventually be suppressed.

What to do about each

Your email service provider will usually flag bounces as hard or soft for you, but the handling policy is yours to set. A sensible approach:

• Hard bounces — suppress on the first occurrence, permanently. Never re-add them, even if a contact re-subscribes with the same typo'd address.
• Soft bounces — let your platform retry automatically, then suppress after a set number of consecutive failures (three to five sends is a common threshold).
• Keep a permanent suppression list so removed addresses can never sneak back in through a re-import or a purchased list.
• Investigate sudden spikes — a jump in soft bounces often means a content or authentication problem (SPF, DKIM, DMARC) on your side, not the recipient's.

The best fix is preventing bounces before you send

Reacting to bounces is damage control. The real win is not sending to bad addresses in the first place — because every hard bounce you avoid is reputation you never had to spend. That's exactly what email verification does: it checks whether an address is real, deliverable, and safe to send to before a single message goes out.

EmailClik Verify runs each address through independent layers — syntax, domain and MX records, disposable and role detection, catch-all resolution, and a mailbox check — and returns a 0–100 deliverability score plus machine-readable reason codes, sorted into good, risky, and bad. The bad bucket is, in effect, your hard bounces caught in advance. It even rescues obvious typos (gmial.com → gmail.com) that would otherwise bounce, and flags catch-all domains that make delivery uncertain.

You can upload a CSV, TXT, or XLSX list of up to a million rows — it auto-detects the email column, dedupes, and preserves every column you uploaded so the cleaned file drops straight back into your platform — or call the REST API for real-time single checks at signup. Pricing is pay-as-you-go (10,000 emails for $37, 100,000 for $149, 1,000,000 for $549), credits never expire, and there's no subscription. EverClean can even auto-clean lists directly inside your ESP or CRM integration, so bad addresses are removed before they ever cost you a bounce.

Frequently asked questions