How a hard bounce works
When your platform hands a message to the receiving mail server, that server answers. A permanent failure — the mailbox does not exist, the domain does not exist, the recipient is blocked at the domain level — is recorded as a hard bounce, and the address is normally suppressed automatically so it is never mailed again. A temporary failure, such as a full mailbox or a server that is briefly down, is a soft bounce, and the platform retries for a while before giving up.
The usual causes are mundane. A typo made on a form, an address invented to get past a download gate, an employee who left and had their mailbox closed, a company that changed domain or went out of business. Occasionally a hard bounce is not really about the address at all: a domain-wide block on your sending reputation can be reported the same way, which is worth checking if a batch of them appears at once from the same recipient domain.
Why hard bounces matter
Mailbox providers treat repeated sends to addresses that do not exist as evidence you do not know who is on your list, and that judgement affects everyone else you mail from the same domain. A single bad import can move a domain from trusted to suspect faster than almost anything else, which is why bounce handling belongs in the foundations of email deliverability rather than in the tidy-up afterwards.
They are also a useful signal about the business, not just the mail. A steady trickle of bounces from your enquiry form points at a form with no validation. A cluster from one company suggests a contact who has moved on and a relationship worth checking. Bounces are the cheapest data quality report you will ever receive, and most businesses delete them unread.
Common mistakes with hard bounces
Re-adding bounced addresses is the worst of them, and it happens by accident more often than by decision: the sales spreadsheet is imported again next quarter and every dead address comes back with it. That is why suppression has to sit above the import, not inside a single campaign.
The second mistake is accepting bounces as the cost of doing business after a large import. If an old list bounces heavily on its first send, the answer is to stop, not to continue and hope the rate improves — each further send adds to the damage. Also worth watching: mistaking soft bounces for a harmless category, since an address that soft bounces every time is effectively dead, and guessing at addresses in a pattern such as first name at company, which produces bounces and, worse, delivers to people who never asked to hear from you.
How to act on it
Fix the collection point first, because that is where dead addresses enter. Confirmed signup removes typos and fake entries before they ever reach the list, and a form that checks the address format catches the obvious errors. Where addresses come from an offline event or a spreadsheet, mail them promptly rather than months later.
Then handle what arrives. Let the platform suppress hard bounces automatically, never re-import a suppressed address, and read the bounce report rather than only the headline number so you can spot a blocked domain masquerading as bad addresses. Make routine list hygiene part of the calendar, and if you are about to mail a list that has been sitting untouched for a long time, send to a small, recent portion of it first and read the result before committing the rest.
