A hard bounce is a permanent delivery failure: the receiving server has said the email can’t be delivered and won’t be deliverable if you try again. The most common reasons are an address that doesn’t exist (“user unknown”), a domain that doesn’t exist or has no mail servers, and an address that has been disabled. Hard bounces usually come back with an SMTP status code starting with 5, such as 550.
Mailbox providers watch how often you send to addresses that don’t exist, because spammers who buy or guess lists hit dead addresses all the time. A sender with many hard bounces looks like someone who isn’t maintaining their list. That is why every hard bounce should be suppressed immediately and permanently: sending again gains nothing and costs reputation.
Not every 5xx response is a true hard bounce. Some providers use permanent-looking codes for policy blocks, such as content rejected as spam or a sender blocked for reputation. These are a sign of a sending problem rather than a bad address, and the fix is to address the cause, not to delete the contact. Good platforms read the full bounce message and classify accordingly.
Preventing hard bounces starts at collection. Double opt-in catches typos before they reach your list. A form check that warns about common misspellings such as “gmail.co” or “yaho.com” helps too. For older or imported lists, run them through an email verification service before the first send, and never use bought lists.
A Vadodara real-estate developer emails 5,000 enquiries from property exhibitions. 410 come back as hard bounces, many with addresses like “rahul@gmial.com”. The platform suppresses all of them automatically, and the developer adds double opt-in to its website enquiry form.
MailNesto suppresses hard-bounced addresses automatically, shows recent bounces with their reasons on the deliverability page, and can verify a list before you send to it.