A bounce is an email that never reaches the recipient because the receiving server rejected it. For cold outreach, bounce rate is one of the two numbers that decides whether your sending domain survives: the other is your spam complaint rate. Keep both low and you can scale. Let either one climb and every email you send after that gets harder to deliver.
The benchmark is under 2%. Most major mailbox providers, and the sending platforms that gate on deliverability, treat 2% as the line. Gmail and Microsoft both use bounce rate as a reputation signal, and a sustained rate above 2% is one of the fastest ways to get your IP or domain filtered. For cold outreach specifically, where the list quality is inherently worse than for transactional or opt-in mail, aim for under 1% if you can. A rate between 2% and 5% means your list has real problems. Above 5% you are actively damaging your sender reputation and should stop sending until you fix it.
Not all bounces are the same, and the fix depends on which kind you are seeing. A hard bounce means the address does not exist: the domain has no mail server, the mailbox was deleted, or the address is malformed. Hard bounces are permanent. You should remove the address from your list immediately and never send to it again, because retrying a hard-bounced address is itself a reputation penalty. A soft bounce is temporary: the mailbox is full, the server is down, or the message was too large. Soft bounces are worth one or two retries, but if the same address soft-bounces repeatedly, treat it as a hard bounce and remove it.
Stale or purchased lists. This is the most common cause in cold outreach. A list that was built months ago, or bought from a vendor, is full of addresses that no longer exist. People change jobs, companies rename their domains, and mailboxes get deleted. The fix is to validate every address before you send, and to re-validate regularly if the list is large.
Typo domains and role accounts. Addresses like gmail.com typos, or role accounts like info@ and sales@ that get deleted when a team changes, bounce at a higher rate. Role accounts are not a deal-breaker, but they should be validated like everything else.
A sending domain that is not set up. If your SPF, DKIM, or DMARC records are missing or wrong, some receiving servers will reject the mail outright, which shows up as a bounce. The DMARC checker runs all three records in one pass and tells you which one is the problem. For the exact records, the SPF, DKIM and DMARC guide covers each one.
A blocklisted sending IP. Even with a clean list and clean records, a listed IP gets rejected. The IP blacklist checker tests the sending IP against nine major lists. If you are listed, the Spamhaus delisting guide covers the request. Delisting only sticks if the underlying cause is fixed first.
Work in this order. First, stop sending to the addresses that hard-bounced; keep them off every future campaign. Second, validate the rest of the list against a live mailbox check, and remove anything that fails. Third, check your sending domain's authentication records and your IP reputation, because a domain-level problem will keep producing bounces no matter how clean the list is. Fourth, resume sending at a reduced volume and watch the bounce rate over the next few days; it should drop back under 2% quickly if the list is the only problem. If it does not, the issue is the sending infrastructure, not the list.
Validate before every campaign, not just the first one. Suppress every hard-bounced address permanently. Keep your volume gradual, especially on a new domain, so a small list problem does not become a reputation problem. And monitor the sending domain continuously, because a new include in your SPF, a provider change, or an expired DKIM key can break deliverability silently. The free deliverability checker runs all of these signals at once and points at the first thing to fix.
Want this checked automatically every day? Inboxproof Pro monitors your domain around the clock and alerts you the moment a record breaks or an IP gets listed. See pricing →