# Hard Bounce vs Soft Bounce: Which Ones You Can Catch Before Sending

Canonical page: https://email-deliverability-desk.vercel.app/tools/bounce-email-checker/

Predicts whether one address will hard bounce, using a live SMTP probe before you send.

Tool: [Bounce Email Checker](https://billionverify.com/bounce-email-checker)

## What it checks

- Address format
- MX records for the domain
- Live SMTP probe of the mailbox, no message sent
- Verdict: Low bounce risk, Likely hard bounce or Risky
- Deliverable, Not deliverable or Deliverability unknown chip

Hard bounce vs soft bounce is the split that decides what you can prevent. A hard bounce is a permanent failure, and a probe can find it before you send. A soft bounce is a temporary failure, and no pre-send check can promise it will not happen. The BillionVerify Bounce Email Checker targets the first kind.

**Key facts:**

- A hard bounce is an SMTP 5xx permanent rejection, and a soft bounce is a 4xx temporary one, per RFC 5321.
- The BillionVerify Bounce Email Checker takes one address and runs a live SMTP probe without delivering a message.
- Its verdicts are Low bounce risk, Likely hard bounce and Risky, plus Invalid syntax and No MX records for early stops.
- It shows a Deliverable, Not deliverable or Deliverability unknown chip next to the verdict.
- The limit is 20 free full checks per IP every 24 hours, no sign-up.

## Hard bounce vs soft bounce: what a probe can see

A hard bounce means the receiving server refuses the recipient for good. The mailbox does not exist, or the domain cannot take mail. Repeated hard bounces hurt your sender reputation, so these are the ones worth removing in advance.

A soft bounce depends on conditions at delivery time. A full mailbox, a server outage and greylisting are typical causes. The same address may work an hour later. A probe sees the server's answer at the moment of the check. It cannot predict a later outage.

## How to check an address for bounce risk

1. Enter one address.
2. Pass the security check and press the check button.
3. Read the verdict, the meaning line and the Deliverable chip.

The tool opens an SMTP session with the receiving server and tests the recipient. No message is sent. It handles one address per run, so it suits spot checks on bounce log entries and new leads.

## How to read each verdict

### Low bounce risk

The server accepted the recipient during the probe. A hard bounce is unlikely for a normal send. Soft bounces and engagement still need to be watched separately. Re-check the address if the list has been sitting for months.

### Likely hard bounce

The probe returned a permanent rejection, or the status came back invalid. Move it to a suppression list with the reason noted, so a later import cannot bring it back.

### Risky

The probe did not give a clear accept or reject. A server may have deferred the request, or the answer was inconclusive. The mailbox may exist, and it may not. Do not treat Risky as safe. Retry later, or look at the full result to see which signal caused the doubt. To [check if an address will bounce](https://billionverify.com/email-checker) with the multi-signal view, open the Email Checker. It separates disposable, role and catch-all flags.

### Invalid syntax or No MX records

The address fails the format rules, or the domain publishes no mail route. Fix the typo or drop the address.

## What to do next

Use the verdict to split your list into send, suppress and retry. Then measure the effect. After the next campaign, count the bounces and run the numbers through the bounce rate calculator on this site.

When you need direct proof that a mailbox accepts mail, use the [email verifier](https://billionverify.com/email-verifier). It is the same check, framed around the SMTP answer itself.
