Skip to content
Faisal Mahmud TusherDigital marketing, SEO & analytics
with Faisal Tusher

Glossary term

Hard Bounce

An email rejected permanently by the receiving server, usually because the address does not exist or the domain cannot receive mail.
AnalyticsconceptUpdated

Definition

When a sending platform hands a message to the recipient's mail server, the server either accepts it or refuses it and says why. A hard bounce is a refusal for a permanent reason. The common causes are an address that never existed, often a typing mistake at sign-up; a mailbox that has been closed, as when someone leaves an employer; a domain that has lapsed or has no mail server configured; and an address so malformed that no server could deliver it. Sending again will produce the same answer.

Hard bounces are counted per send and usually reported as a share of messages sent, alongside soft bounces, complaints and unsubscribes. They are an email measure only: the web analytics metric called bounce rate describes sessions on a website and shares nothing with them but the word.

Hard versus soft bounces

A soft bounce is a temporary failure. The mailbox may be full, the receiving server may be busy or deliberately slowing a sender down, or the message may be too large. Platforms retry soft bounces for a period and, if the failure continues, stop trying. A soft bounce says nothing certain about the address.

The distinction matters because the two need opposite handling. A hard-bounced address is suppressed after one failure; a soft-bounced address stays on the list but is watched. The email list hygiene SOP sets out the practical bridge between them: an address that soft-bounces repeatedly is treated as a hard bounce under a rule the team agrees in advance, so that dead mailboxes reporting a temporary error do not stay on the list indefinitely.

In practice: suppression and source checks

Most sending platforms suppress hard-bounced addresses automatically. The work that remains is making sure the suppression reaches every system that can send email, so that a CRM, a second platform or a sales tool does not mail the address again. The email sending domain setup checklist asks for hard bounces to be exported as their own suppression file when moving to a new platform, imported before any contact is mailed. In automated flows, a hard bounce should end the sequence for that contact; the guide to building a welcome series includes it among the exits every flow needs.

The second task is to ask where the bouncing addresses came from. Hard bounces cluster by source: an old export, a purchased or rented list, a trade-show scanner, a form with no confirmation step or a sign-up field that accepts obvious typos. Tracing the bounces to their source turns a cleanup into a fix.

What a spike in hard bounces means

Mailbox providers watch how a sender treats addresses that do not exist. A sender that keeps mailing them looks like one that does not maintain its list, and the email deliverability guide explains how that behaviour feeds into the reputation that decides inbox or spam placement for everyone else on the list. A sudden rise in hard bounces on one send is therefore a warning about the next send, not just a cost on this one.

Because the cause is almost always the addresses, the sensible reading is by segment and source. The guide to email metrics and testing places bounces in the delivery layer of the metric stack, where the useful question is whether the message reached a mailbox at all, and the email marketing fundamentals section includes reviewing bounces after every send and clearing them monthly in its routine.

Illustrative example — not a real result

A pottery studio imports an old spreadsheet

Glazewick Pottery Studio had 2,300 newsletter subscribers who had all opted in through its booking form. Before launching a winter workshop programme, the owner added a spreadsheet of 1,100 past workshop customers going back seven years. The first send went to 3,400 addresses, and 260 hard-bounced, all but 9 from the spreadsheet. The studio suppressed every one of them the same day, removed the remaining spreadsheet contacts from regular sends and mailed them once, separately, with an invitation to join the newsletter. The next two sends went only to subscribers and to the 140 who joined, and hard bounces fell to 3 per send. Bookings came mostly from the subscriber list, as before.

Deliverability is what repeated hard bounces damage, through the reputation providers keep for each sender. A Suppression List is where every hard-bounced address goes so that no system mails it again. List Growth Rate is reduced by hard bounces, which remove addresses as surely as unsubscribes do. Spam Complaint Rate is the other per-send signal providers weigh most, and the two often rise together when a list comes from a weak source.

Common confusions

  • Email bounce rate and website bounce rate are related. They measure different things in different systems and share only a name.
  • A hard bounce can be retried later. The failure is permanent; retrying only repeats the signal providers read as poor list care.
  • The platform handles it. It usually suppresses the address in that platform; other sending systems need the same suppression.
  • Soft bounces can be ignored. Most clear on their own, but persistent ones need a rule that eventually treats them as hard.
  • Hard bounces are a content problem. The message rarely causes them; the list source almost always does.

More terms to look up

Where this term is used

Related