A bounced email is not just a missed send. In cold outbound, bounces are one of the clearest signals inbox providers use to score your domain, and treating a hard bounce the same way you treat a soft bounce is how a clean sending domain quietly turns into a burned one. This guide covers what each bounce type means for cold email specifically, how to read your bounce data, and what to actually do about each kind.
What Counts as a Hard Bounce in Cold Email
A hard bounce is a permanent delivery failure. The receiving server has told you, unambiguously, that the message cannot be delivered to that address — now or ever, until something about the address itself changes. In cold outbound the common causes are a mistyped address, a domain that no longer exists, or a mailbox that was deleted when the contact left the company. Prospect data decays constantly, so a portion of hard bounces on any list is expected even on a freshly verified list.
A hard bounce is not a signal to retry. The address is confirmed invalid, and every further send to it is a wasted attempt that still counts against your domain.
What Counts as a Soft Bounce in Cold Email

A soft bounce is a temporary delivery failure. The receiving server accepted the attempt but could not deliver the message right now — a full mailbox, a server timeout, a message that was too large, or a greylisting delay while the receiving system decides whether to trust your domain. Most sequencers will retry a soft bounce automatically for a set window before giving up.
A hard bounce tells you the address is gone. A soft bounce tells you nothing on its own — only a pattern across multiple soft bounces from the same domain tells you something is actually wrong.
Why the Distinction Matters More in Cold Outbound Than in Marketing Email
Marketing email lists are opt-in and get cleaned by unsubscribes and list-hygiene tools running continuously. Cold email lists are built from third-party data that is wrong from the moment it is scraped, sent from domains with a much thinner reputation history, and judged by inbox providers against bulk-sender thresholds that do not distinguish your intent from a spammer’s. A hard-bounce rate that a marketing platform would barely flag can be enough to push a new sending domain into filtering, because the domain has no established trust to absorb the hit.
This is also why bounce handling belongs upstream of sending, not downstream of it. Our B2B email list cleaning guide covers the verification step that should catch most future hard bounces before they ever reach a sequence.
How to Read Your Bounce Data
A single bounce tells you almost nothing. What matters is the rate and the pattern:
- Rate by domain, not by list. A 1% hard-bounce rate across five sending domains could mean one domain at 5% and four at 0% — and that one domain is the actual problem.
- Rate over time, not a single day’s snapshot. A spike after importing a new list source is a data-quality signal. A rate that creeps up steadily on an existing list is a decay signal.
- Soft-bounce repetition on the same address. One soft bounce is noise. The same address soft-bouncing three sends in a row behaves like a hard bounce and should be treated as one.
There is no single hard-bounce percentage that is safe for every domain, every list source, and every sending volume — a threshold pulled from a general email-marketing benchmark will not reflect what a young cold-sending domain can actually absorb. Compare each domain against its own recent history and act on the trend, not a borrowed number.
Corrective Actions by Bounce Type
The two bounce types call for different responses, and applying the hard-bounce response to a soft bounce — retrying it repeatedly — is one of the more common ways a temporary problem becomes a permanent one.
| Situation | What it usually means | Action |
|---|---|---|
| Hard bounce, any volume | Address is invalid or the domain no longer exists | Suppress immediately, remove from every future sequence |
| Isolated soft bounce | Full mailbox or momentary server issue | Let the sequencer’s automatic retry run; no manual action needed |
| Same address, repeated soft bounces | Behaving like an invalid or dormant mailbox | Suppress it — treat as a hard bounce after two to three failed retries |
| Soft-bounce rate rising on one domain | Receiving servers are throttling or greylisting that domain | Pause volume on that domain, check blacklist and spam-trap status before resuming |
| Hard-bounce rate rising on one domain | The list source feeding that domain is stale or was scraped, not verified | Stop sending from that source, re-verify before reintroducing it |
When a Soft Bounce Becomes a Domain-Health Problem
Soft bounces are graded as lower-risk than hard bounces, and individually they are. But a domain producing an unusually high volume of soft bounces — well above what its normal send pattern produces — is often showing an early symptom of the same reputation damage a hard-bounce spike causes, just expressed as receiving servers deferring instead of outright rejecting. Watching for that shift is part of the same monitoring discipline covered in our email deliverability checklist, and getting the sending domain itself set up correctly in the first place — dedicated domains, proper DNS, a real warmup period — is what keeps an isolated soft-bounce blip from ever compounding into one.
The Bottom Line
Hard bounces are permanent and need immediate suppression; soft bounces are temporary and need monitoring, not panic — unless they repeat on the same address or spike on the same domain, at which point they deserve the same seriousness as a hard bounce. Read bounce rate by domain and over time, not as a single number against a borrowed benchmark, and fix the list source before you fix the symptom.
If your domains are already carrying bounce damage you cannot diagnose from the outside, our cold email infrastructure services cover exactly this, or apply for the GTM Pilot and we will audit it directly.
FAQ
What is a good hard bounce rate for cold email?
There is no single safe number that applies to every domain. A young or newly warmed domain can be pushed into filtering by a hard-bounce rate a well-established domain would absorb without issue. Judge a domain against its own recent history, and treat any sustained upward trend as the signal, not a fixed percentage.
Do soft bounces hurt my sender reputation?
An isolated soft bounce barely registers. A domain producing an elevated rate of soft bounces across many sends is a different situation — that pattern often means receiving servers are already starting to defer or throttle your mail, which is an early form of the same damage a hard-bounce spike causes.
How many times should a sequencer retry a soft bounce before I intervene?
Let the automatic retry run its normal window first. If the same address soft-bounces on two or three separate attempts, stop retrying and suppress it — at that point it is behaving like an invalid address, not a temporary hiccup.
Can a clean, verified list still produce hard bounces?
Yes. B2B contact data decays continuously as people change roles and companies retire domains, so some hard bounces are expected even on a list verified right before sending. The goal of verification is to keep the rate low and predictable, not to reach zero.



