What is a hard bounce vs a soft bounce?

A hard bounce is a permanent delivery failure: the address does not exist or the domain is dead, so it will never accept mail. A soft bounce is a temporary failure, like a full mailbox or a busy server, that may clear on a retry. Hard bounces hurt sender reputation most.

Hard bounce vs soft bounce: the core difference

Every bounce is your recipient's mail server refusing a message. The refusal code tells you why. Servers return a three-digit SMTP status. Codes in the 5xx range are permanent. Codes in the 4xx range are temporary. That single digit is the line between a hard bounce and a soft bounce, and it decides how you should react.

A hard bounce means stop sending. The mailbox is gone, the domain has no mail exchanger, or the server has flatly rejected the address. Retrying does nothing. A soft bounce means wait. The mailbox exists but could not receive right now. Most email service providers retry soft bounces automatically for 24 to 72 hours before giving up.

What causes a hard bounce?

A hard bounce is caused by a permanent problem the sending server cannot fix. The most common triggers are a mistyped or nonexistent mailbox, a domain with no valid MX record, a domain that has expired, or a recipient server that blocks your sending domain outright. None of these resolve on their own.

The usual culprits, in order of how often they show up:

• Typos in the local part, like jhon@ instead of john@, or a fat-fingered domain like gmial.com.
• The mailbox was deleted, often when an employee leaves a company.
• The domain no longer exists or has no MX record, so there is nowhere to deliver.
• A block or policy rejection where the receiving server refuses your domain or IP for reputation reasons.

Hard bounces are the ones that damage you. Mailbox providers read a high hard-bounce rate as a sign you are mailing a stale or purchased list. Keep it under 2%. Above that, spam filtering tightens and inbox placement drops for everyone on your sending domain.

What causes a soft bounce?

A soft bounce is caused by a temporary condition on the receiving side. Typical causes are a full mailbox, a message that exceeds the size limit, a mail server that is down or overloaded, or greylisting, where an unfamiliar sender is deliberately deferred and asked to retry a few minutes later.

Soft bounces are normal. A small percentage on any send is expected and not a reputation problem by itself. The risk is a soft bounce that never clears. If the same address soft bounces on send after send, treat it like a hard bounce and remove it. Most platforms suppress an address automatically after a set number of consecutive soft bounces, often around five.

How do hard and soft bounces affect your reputation?

Hard bounces hurt reputation directly because they prove you mailed invalid addresses. Mailbox providers track your bounce rate and throttle or filter senders who repeatedly hit dead mailboxes. Soft bounces have little immediate effect, but repeated soft bounces to the same address signal list decay and eventually behave like hard bounces.

Bounce types at a glance

How do you prevent bounces before you send?

You prevent most bounces by verifying your list before the send, not after. Verification checks each address for valid syntax, a live MX record, and a real mailbox at the SMTP level. That catches the typos and dead domains that cause hard bounces, so you never mail them and never take the reputation hit.

A practical pre-send routine looks like this:

1. Run new addresses through verification at signup or import, so bad data never enters your list.
2. Batch-verify any list older than 90 days, since B2B addresses decay as people change jobs.
3. Remove every address that verifies as Invalid. These are your future hard bounces.
4. Review Risky verdicts (catch-all, role, disposable) and decide case by case whether to mail them.
5. Fix or confirm typo suggestions before you delete, since a real subscriber may sit behind a misspelled domain.

You can run this without installing anything. Paste a list or drop a CSV into the free Free Email Verifier and it flags bad syntax, duplicates, and disposable domains instantly, then runs MX and SMTP-level mailbox checks on the rest. The file is parsed in your browser and never uploaded, which matters when the list holds customer data. Verdicts come back as Deliverable, Risky, Invalid, or Unknown, and you can export the clean list as CSV or JSON.

What to do when a bounce happens

Read the code first. A 5xx hard bounce comes off the list on the same day. There is no upside to keeping it and every send to a dead mailbox drags your rate up. A 4xx soft bounce stays, but tag it. If it keeps failing across several sends, it has effectively become a hard bounce, so suppress it.

Watch the trend, not just single events. A sudden spike in hard bounces usually means a bad import or a scraped list slipped into your sending. A slow climb in soft bounces often means an authentication or reputation issue on your side, worth checking against your DMARC and SPF setup. Clean data at the front end is the cheapest fix. If verifying and warming lists is not where you want to spend time, Synthisia runs lead generation and meeting booking on verified pipeline so your team works replies instead of bounce logs.

The habit that keeps a sender healthy is simple. Verify before you send, remove hard bounces the day they happen, and give soft bounces a short leash. Do that and your bounce rate stays under 2%, your inbox placement holds, and one dead mailbox never costs you the whole list.