Email deliverability glossary: 40 terms every sender should know
Forty email deliverability terms defined in one or two sentences each: bounces, SPF, DKIM, DMARC, spam traps, greylisting, sender reputation, inbox placement and verification.
Keep hard bounces under 2% or mailbox providers start throttling you. Hard versus soft bounces, the main causes, a step by step cleanup plan and sunset policies.
To reduce your email bounce rate, remove the addresses that cannot receive mail before you send, verify every new address at the point of capture, and retire subscribers who have stopped engaging before their mailboxes die. Keep the hard bounce rate under 2%, because that is roughly where mailbox providers begin throttling and filtering your mail, and aim for well under 1% on a healthy list.
A hard bounce is a permanent failure. The mailbox does not exist, the domain has no mail servers, or the receiving server has rejected the address outright with a 5xx code such as 550 5.1.1. A hard-bounced address should be suppressed immediately and never mailed again.
A soft bounce is a temporary failure. The mailbox is full, the server is busy or greylisting, the message is too large, or the recipient's provider is deferring your mail for reputation reasons. Soft bounces are retried by your sending platform for a day or two. An address that soft-bounces on several consecutive campaigns should be treated as if it had hard-bounced.
Most platforms count only hard bounces in the headline bounce rate, but repeated soft bounces are an early warning that something on the list, or in your reputation, is slipping.
Mailbox providers watch bounce rates because a sender who keeps mailing dead addresses is either careless or working from a purchased list, and both correlate strongly with spam. Around 2% is the level at which the major providers and most ESPs start reacting: your mail is throttled, deferred into the soft-bounce pile, or diverted to the spam folder. Keep going and your sending domain or IP earns a block.
Gmail and Yahoo formalised their expectations for bulk senders in February 2024. Senders must authenticate with SPF, DKIM and DMARC, offer one-click unsubscribe and honour it within two days, and keep the reported spam rate under 0.3%, ideally under 0.1%. Bounces are not spam complaints, but the two travel together: a list full of dead addresses is a list nobody asked to be on, and the complaints follow. Check your authentication with the SPF and DMARC checker before you worry about anything else.
The formula is simple: bounces divided by emails sent, multiplied by 100. If you sent 20,000 messages and 500 bounced, your bounce rate is 2.5%, which is already over the line. Our bounce rate calculator does the arithmetic and tells you how many addresses you would need to remove to get back under 2%, and under 1%.
Measure per campaign and per segment, not just overall. A healthy main list can hide a disastrous imported segment.
Addresses decay at roughly 22% per year as people change jobs, close accounts and abandon old mailboxes. A list you have not mailed for six months is already carrying a meaningful share of dead addresses, and two years of decay at that rate leaves well over a third of the list dead. Age is the single biggest predictor of bounces.
Roughly 15% of addresses entered into forms are invalid at the moment of entry. Some are deliberate fakes, but many are honest mistakes: gmial.com, hotmail.con, a missing letter in a surname. Each one bounces on the welcome email. The email typo fixer shows how these are caught and corrected at the form.
Addresses like info@, sales@ and admin@ are shared, often unmonitored, and frequently retired without notice. They bounce more than personal addresses and they complain more too, because nobody in the shared inbox remembers subscribing. The role email checker finds them, and our role account guide covers what to do with them.
Bought lists are the fastest route to a blocked domain. The addresses are old, were never verified, and were never given to you, so bounces and complaints arrive together. Verification can remove the dead addresses, but it cannot create consent. If you must use third-party data, treat it as a separate, low-volume, heavily monitored segment.
A catch-all domain accepts every address at the SMTP stage and may bounce later from the mailbox system. These addresses show up as risky in verification results, and they are a common source of bounces that "verified" lists still produce. See catch-all domains explained for how to handle them.
Temporary inboxes die within hours of signup. Every later send to them bounces or vanishes. Block them at the form with the disposable email checker logic and clean out the ones already on your list.
Verification removes addresses that are already dead. A sunset policy removes addresses before they die, which is better for your reputation because mailbox providers also score you on engagement.
A simple policy: anyone who has not opened or clicked in six months gets a short re-engagement series, two or three emails asking whether they want to stay. Anyone who does not respond is moved to a suppressed segment and no longer mailed. You lose nothing, because they were not reading anyway, and you stop sending to the mailboxes most likely to go dark.
Re-verify the suppressed segment before any win-back campaign. Addresses that have been quiet for a year are precisely the ones that decay.
Everything above is maintenance. Prevention is cheaper. Checking addresses at the moment they are entered stops most of the problem at the source: typos are corrected, disposable addresses are refused, role accounts are flagged, and undeliverable addresses never reach your database.
The form validation widget drops into any signup, checkout or lead form and runs the full verification in the background while the user types. For custom builds, the email verification API returns the same result in a single request. Either way, every address that enters your list has already passed the check your cleanup would otherwise run months later.
Work out where you stand with the bounce rate calculator, then clean your current list with bulk list cleaning and put real-time verification on every form so the number stays low. The deliverability page explains how the pieces fit together.
Related reading
@Forty email deliverability terms defined in one or two sentences each: bounces, SPF, DKIM, DMARC, spam traps, greylisting, sender reputation, inbox placement and verification.
@Real-time email validation checks an address as it is typed: syntax, typos, disposable domains, role accounts, MX and an optional mailbox check. Here is how it works.
@Gmail, Outlook and Yahoo addresses carry no company signal, so B2B teams segment them. When free addresses are legitimate, how the free and role flags route them, and bulk detection.
Photos: Freepik