Guide
Email Bounce Codes: The Complete Guide to SMTP Errors, Hard vs Soft Bounces, and Fixes
By Unlimited Verifier Team ·

Summary
Email bounce codes are SMTP reply codes (like 550) and enhanced status codes (like 5.1.1) that explain why a message wasn't delivered. 4xx codes are temporary and 5xx codes are permanent. Classify bounces by the middle digit of the enhanced code: X.1.x means suppress the address, while X.7.x means fix your sending reputation or authentication.Email bounce codes are the three-digit SMTP reply codes (such as 550) and dotted enhanced status codes (such as 5.1.1) that a receiving mail server returns when it refuses or can't deliver your message. 4xx codes are temporary and 5xx codes are permanent. Reading them correctly tells you whether to retry, suppress the address, or fix your own sending setup.
That last distinction is where most teams go wrong. A 5xx code does not always mean "bad address." A 550 5.7.1 usually means the receiver doesn't trust you, not that the mailbox is gone. If you suppress every 5xx recipient, you can delete thousands of real customers after a single blocklisting incident. If you ignore 4xx codes forever, you keep mailing dead inboxes that quietly drag down your reputation.
This guide is the hub for the whole topic. It covers how to read any bounce, which codes are hard or soft, the codes you will actually see, provider-specific quirks at Microsoft and Gmail, a triage framework, two worked examples with real arithmetic, and how to stop address bounces before you hit send.
Quick answer
- Anatomy: A bounce line looks like
550 5.1.1 User unknown. It contains a basic reply code (RFC 5321), an enhanced status code (RFC 3463), and free-text that each server words differently. - 4xx = soft, 5xx = hard. For 4xx codes, RFC 5321 says retries should be spaced at least 30 minutes apart and a sender should keep trying for at least 4–5 days before giving up.
- Classify by the middle digit of the enhanced code, not just the first digit. X.1.x addressing failures (and X.2.1 disabled mailboxes) mean you should suppress the address. X.7.x security/policy failures mean you need to fix your sending reputation or authentication, and you should not purge the list.
- Thresholds: Aim for a hard-bounce rate under 1% per send and investigate at 2%. Amazon SES says in its FAQ that it may place accounts under review at a 5% bounce rate.
- Prevention: Address bounces (5.1.1, 5.1.2, Microsoft's 5.1.10 and 5.4.1) are preventable. Verify lists before sending with a tool like Unlimited Verifier, which checks syntax, domain/MX and the SMTP mailbox, detects catch-all domains, and sorts every address into Valid, Risky or Invalid.
What are email bounce codes, exactly?
Email bounce codes are standardized status messages exchanged during the SMTP conversation between your sending server and the recipient's server. They report success, temporary failure, or permanent failure. You see them either live in your ESP's logs (a synchronous bounce) or inside a returned "Undeliverable" email, also called a delivery status notification or DSN (an asynchronous bounce).
How do you read a bounce message?
Every bounce line has up to three layers:
550 5.1.1 <jane@example.com>: Recipient address rejected: User unknown in virtual mailbox table
| Layer | Example | Defined by | What it tells you |
|---|---|---|---|
| Basic reply code | 550 |
RFC 5321 | First digit = outcome class (2 success, 3 intermediate, 4 temporary, 5 permanent) |
| Enhanced status code | 5.1.1 |
RFC 3463, registry kept by IANA | Class.Subject.Detail. This is the precise reason. |
| Diagnostic text | User unknown in virtual mailbox table |
The receiving server (not standardized) | Context, and often a URL to the provider's help page |
The basic code is too coarse to act on alone. RFC 5321 defines 550 as "mailbox unavailable," with examples covering both "mailbox not found" and "command rejected for policy reasons." That one code spans a dead address and a spam block. The enhanced code separates them.
For a full reference to the three-digit codes, see our SMTP error codes list with meanings. The dotted codes are catalogued in our complete enhanced SMTP status codes reference.
What does the middle digit of an enhanced code mean?
The middle digit (the subject) is the single most useful field in any bounce. Here is how the RFC 3463 subjects map to the action you should take:
| Subject (X.n.X) | Category | Common examples | What it usually means for you |
|---|---|---|---|
| .0. | Other/undefined | 5.0.0, 4.0.0 | Read the text. The server didn't categorize the failure. |
| .1. | Addressing | 5.1.1, 5.1.2, 5.1.3 | The address, domain or syntax is bad. Suppress. |
| .2. | Mailbox | 4.2.2/5.2.2 (full), 5.2.1 (disabled) | The mailbox exists but can't accept mail. Retry or suppress depending on the detail. |
| .3. | Mail system | 5.3.4 (message too big) | A problem with your message or the receiving system. |
| .4. | Network/routing | 4.4.7 (expired), 5.4.4 (unable to route) | Delivery path failure. Microsoft also uses 5.4.1 for "access denied." |
| .5. | Protocol | 5.5.x | An SMTP command problem, usually your MTA's configuration. |
| .6. | Content/media | 5.6.x | Encoding or content conversion issues. |
| .7. | Security/policy | 5.7.1, 5.7.26 | Authentication, reputation, blocklists, or a policy refusal. Fix your sending setup. |
One practitioner caveat: providers don't always follow the registry. RFC 3463 defines X.4.1 as "No answer from host," yet Microsoft 365 returns 550 5.4.1 Recipient address rejected: Access denied for recipients that don't exist in a tenant. Always read the diagnostic text alongside the code.
Bottom line: Read every bounce as basic code, then enhanced code, then text. The enhanced code's middle digit tells you whether the problem is the address or your reputation.
What's the difference between 4xx and 5xx bounce codes?
A 4xx code is a transient failure: "not now, try again." A 5xx code is a permanent failure: "don't send this again as-is." Your mail server is expected to queue and retry 4xx messages automatically. A 5xx ends the attempt immediately.
The retry schedule is standardized. RFC 5321 (section 4.5.4.1) says the retry interval should be at least 30 minutes and the give-up time generally needs to be at least 4–5 days. When retries run out, your MTA generates a final failure. Microsoft labels this 4.4.7 Message expired. Depending on your ESP, an expired deferral may be logged as a soft or a hard bounce.
Three nuances the simple 4xx/5xx rule misses:
- Servers disagree on permanence. Gmail returns
452 4.2.2for over-quota mailboxes, which is temporary. Many other servers return552 5.2.2for the same condition, which is permanent. Identical situation, opposite class. - Some 5xx codes are reversible. A
550 5.7.1blocklist rejection disappears once you're delisted. The address was never the problem. - Some 4xx codes are effectively permanent. A mailbox that has been "full" for 60 days is almost certainly abandoned, so the right response is to treat it as dead.
For a deeper side-by-side, read 4xx vs 5xx SMTP errors: the practical difference.
Bottom line: 4xx means retry and 5xx means stop. But persistence over time and the enhanced code decide what you do with the address.
Which bounce codes are hard bounces and which are soft?
A hard bounce is a permanent failure tied to the recipient address: it doesn't exist, the domain doesn't exist, or the mailbox is disabled. A soft bounce is a temporary failure such as a full mailbox, a busy server, rate limiting or greylisting. A third category, the block bounce, is the one most guides skip. Block bounces carry 5xx codes, but they're caused by your reputation, authentication or content.
| Code | Typical meaning | Type | Suppress the address? | Right action |
|---|---|---|---|---|
| 550 5.1.1 | Mailbox doesn't exist | Hard | Yes, immediately | Remove; verify the source of the signup |
| 550 5.1.2 | Domain/host doesn't exist | Hard | Yes | Remove; check for typos like "gmial.com" |
| 553 5.1.3 | Bad address syntax | Hard | Yes | Fix at capture with validation |
| 550 5.2.1 | Mailbox disabled | Hard | Yes | Remove |
| 550 5.4.1 (Microsoft) | Recipient not in tenant / access denied | Hard | Yes, after confirming the text | Remove |
| 552 5.2.2 | Mailbox full (permanent wording) | Hard-ish | After repeats | Treat like a soft bounce with a short fuse |
| 452 4.2.2 | Mailbox full (temporary) | Soft | After your soft-bounce threshold | Retry; count consecutive failures |
| 421 4.7.0 | Try again later / rate-limited | Soft (deferral) | No | Slow down; check reputation |
| 450 / 451 | Mailbox unavailable / local error / greylisting | Soft | No | Let your MTA retry |
| 550 5.7.1 / 554 5.7.1 | Policy or spam rejection | Block | No | Fix authentication, reputation or content |
| 550 5.7.26 (Gmail) | Unauthenticated sender | Block | No | Fix SPF/DKIM/DMARC |
| 552 5.3.4 | Message too large | Content | No | Shrink the message or attachments |
The "Suppress the address?" column is the whole game. Get it wrong in one direction and you mail dead addresses. Get it wrong in the other and you delete live customers. Our guide to hard bounce vs soft bounce codes goes code by code.
What types of email bounces exist?
Beyond hard and soft, it helps to sort bounces by mechanism:
- Synchronous bounces are rejected during the SMTP session. Your ESP sees the code instantly.
- Asynchronous bounces happen when the server accepts the message (250 OK) and later sends back a DSN. These are common with forwarding and some corporate gateways.
- Address bounces cover non-existent mailboxes or domains.
- Block bounces are reputation, blocklist or authentication refusals.
- Transient bounces include full mailboxes, rate limits and greylisting.
- Content bounces cover size limits, attachment policies and malformed MIME.
- Not actually bounces: out-of-office replies and challenge-response messages. These sometimes get misfiled as soft bounces by naive parsers.
See each type with a real message sample in types of email bounces, with examples.
Bottom line: Use three buckets, not two. Address bounces get suppressed, soft bounces get retried and counted, and block bounces get fixed at the sender.
Why do bounce codes matter for deliverability?
Mailbox providers read your bounce rate as a proxy for list quality. A sender who repeatedly hits non-existent addresses looks like someone who bought, scraped or neglected a list. That same behavior correlates with spam traps and complaints. Reputation damage then shows up as more 4.7.x deferrals and 5.7.x blocks, so bounces breed more bounces.
The numbers that matter:
- Amazon SES states in its FAQ that it may place an account under review at a 5% bounce rate and may pause sending at 10%.
- Google's email sender guidelines require bulk senders (5,000+ messages a day to Gmail) to authenticate with SPF, DKIM and DMARC, offer one-click unsubscribe, and keep user-reported spam rates below 0.3%. Google recommends staying under 0.1%.
- Yahoo's sender best practices set similar authentication and complaint expectations.
- Industry rule of thumb: Many ESPs and deliverability practitioners treat 2% as the ceiling for bounces. Sources disagree on the exact line. We recommend under 1% hard bounces per campaign as your target, investigating at 2%, and treating anything near 5% as an emergency.
There's a direct revenue angle too. Every invalid address inflates your contact count (and often your ESP bill) while contributing zero opens. Every reputation hit suppresses inbox placement for your good subscribers. Our email deliverability guide covers the full reputation picture. For the money side, see how list quality feeds email marketing ROI.
Bottom line: Bounce rate is a reputation signal, not just housekeeping. Keep hard bounces under 1% and you protect inbox placement for everyone else on your list.
What are the most common email bounce codes and how do you fix them?
Most bounce volume comes from about ten codes. Below is each one: what it means, whether to suppress, and the fix. Our roundup of the most common email bounce codes and how to fix them has extra diagnostic text samples. Our marketer-focused shortlist, 10 SMTP error codes every email marketer should know, condenses these into a cheat sheet.
550 5.1.1 — User unknown
The mailbox doesn't exist on the receiving server, so this is a hard bounce. It's typically caused by typos ("jhon@"), people who left a company, abandoned accounts deleted by the provider, or fake signups. Suppress on the first occurrence and never retry.
The deeper fix is upstream: find where these addresses entered your list. If 5.1.1s cluster around one lead source or signup form, that source is the problem. Read the full breakdown in 550 5.1.1 user unknown: what it means. For the step-by-step remediation (capture validation, bulk verification, re-permissioning old segments), see how to fix 550 5.1.1 recipient address rejected.
550 5.1.2 — Bad destination host
The domain can't receive mail. Either it doesn't exist, or it has no MX record (and no usable fallback A record). Common causes are domain typos ("gmail.co," "yaho.com"), expired company domains, and placeholder data ("test.com").
This is a hard bounce, and it's the easiest one to prevent: a DNS/MX check catches it before you send. Details are in 550 5.1.2 bad destination host explained.
550 5.4.1 — Recipient address rejected: Access denied
This code is mostly seen from Microsoft 365 / Exchange Online. It typically comes from Directory-Based Edge Blocking, which rejects mail for recipients that don't exist in the organization's directory. Despite the "access denied" wording, it usually behaves like a 5.1.1, so treat it as a hard bounce.
The exception is when the tenant is misconfigured, which matters if you own the receiving domain. See 550 5.4.1 recipient address rejected: access denied.
550 5.7.1 — Message rejected
This is a security/policy block. The receiver refused the message because of your IP or domain reputation, a blocklist listing, failed authentication, or content filters. It is a block bounce, and you should not suppress the recipients.
Diagnose it in this order:
- Read the text for a blocklist name or help URL.
- Check your sending IP and domain against blocklists. Unlimited Verifier offers a free domain blacklist checker.
- Confirm SPF, DKIM and DMARC alignment.
- Look at recent list sources and complaint rates.
Full playbook: 550 5.7.1 message rejected — how to fix it.
554 5.7.1 — Delivery not authorized
This means the same thing as 550 5.7.1, but uses the 554 "transaction failed" basic code. You'll see it for relay denials ("Relay access denied"), spam rejections, and IPs blocked at connection time. Most often it's a block bounce. When the text says "relay access denied," it's usually a server configuration problem on a sending account rather than a marketing issue. See what 554 5.7.1 means and why it happens.
554 — Transaction failed
A bare 554 is the server's generic "no." RFC 5321 also uses it at connection time to mean "No SMTP service here." Because it's so generic, the diagnostic text carries all the meaning: a blocklist reference, "message looks like spam," or a content rule. Classify by text, and treat it as a block unless the text clearly says the user doesn't exist. More in 554 transaction failed: decoding the bounce.
421 4.7.0 — Try again later
This is a deferral, not a final bounce. The server is closing the connection and asking you to come back later. Gmail uses 421 4.7.0 for temporary reputation-based throttling and some authentication or TLS issues.
Your MTA will retry. The real signal is volume: if 421s spike at one provider, you're being rate-limited for reputation reasons. Slow your send rate to that domain, mail engaged segments first, and check authentication. See 421 4.7.0 "try again later" meaning.
450 — Requested mail action not taken
RFC 5321 describes 450 as "mailbox unavailable," for example when the mailbox is busy or temporarily blocked for policy reasons. In practice, 450 (often 450 4.2.0 or 450 4.7.1) is a classic greylisting response. The server temporarily rejects mail from unfamiliar senders and accepts it on a properly spaced retry. It's a soft bounce, and legitimate MTAs pass greylisting automatically. Read SMTP 450 "requested mail action not taken" explained.
451 — Local error in processing
A 451 means the receiving server hit a temporary problem: a backend timeout, a spam-scanner hiccup, or greylisting (451 4.7.1). It's soft, so let your MTA retry. Persistent 451s from one domain suggest either their infrastructure problem or a soft reputation throttle. See what SMTP error 451 means.
452 4.2.2 — Mailbox full
The mailbox exists but is over its storage quota. Gmail's wording is "The email account that you tried to reach is over quota." It's soft in the short term.
Our practitioner's rule: a mailbox that stays full across several sends over three to four weeks is almost always abandoned. Treat it as dead even though the code is a 4xx. See 452 4.2.2 mailbox full bounces.
Bottom line: 5.1.x codes mean remove the address. 4.x.x codes mean let retries work but count them. 5.7.x codes mean the problem is your reputation, not your list.
What do Office 365 and Gmail bounce codes mean?
Microsoft and Google return enhanced codes with provider-specific meanings and diagnostic text. Knowing their dialects saves hours.
Microsoft 365 / Exchange Online NDR codes
Microsoft's non-delivery reports (NDRs) include an enhanced code plus a fix-it summary. The ones list owners hit most:
| Microsoft code | What it means | Treat as |
|---|---|---|
| 5.1.10 | Recipient not found by SMTP address lookup | Hard: suppress |
| 5.4.1 | Recipient address rejected: Access denied | Hard: suppress |
| 5.2.2 | Mailbox full | Soft, then suppress if persistent |
| 5.7.1 | Delivery not authorized (often sender restrictions) | Block: check permissions and policy |
| 5.7.606–5.7.649 | Access denied, banned sending IP | Block: request delisting from Microsoft |
| 5.7.708 | Traffic not accepted from this IP | Block: IP reputation issue |
| 4.4.7 | Message expired (retries exhausted) | Soft that became final: investigate the path |
The 5.7.6xx and 5.7.708 codes are the important ones for bulk senders. They mean Microsoft has blocked your IP, so suppressing recipients does nothing. Our full Office 365 NDR bounce codes list covers the rest, with delisting steps.
Gmail bounce codes worth memorizing
- 550 5.1.1 — "The email account that you tried to reach does not exist." Hard.
- 452 4.2.2 — Over quota. Soft.
- 421 4.7.0 — Temporary deferral, often reputation or authentication related.
- 421 4.7.28 / 550 5.7.28 — An unusual rate of unsolicited mail from your IP or domain. Reputation.
- 550 5.7.26 — The message is unauthenticated or fails DMARC. Fix SPF, DKIM and DMARC alignment per Google's sender guidelines.
To see your Gmail-specific domain reputation and spam rate, Google Postmaster Tools is the authoritative free dashboard.
Bottom line: Microsoft's 5.7.6xx/5.7.708 and Gmail's 5.7.26/5.7.28 are sender-side problems. Fix your IP, domain or authentication rather than touching the list.
What do hard bounce messages look like, and why do emails hard bounce?
Hard bounce messages vary wildly in wording even when the code is identical, which is why parsers that match on text break. Real-world variants of the same 5.1.1 failure include:
550 5.1.1 The email account that you tried to reach does not exist.550 5.1.1 <user@domain>: Recipient address rejected: User unknown in local recipient table550 5.1.10 RESOLVER.ADR.RecipientNotFound; Recipient not found by SMTP address lookup550 No such user here, a legacy server with no enhanced code at all
We've collected annotated samples in examples of hard bounce messages.
The root causes concentrate in a handful of patterns. In rough order of how often they explain a hard-bounce spike:
- Typos at signup, at both the local part and the domain.
- Job changes. B2B addresses decay as people leave employers.
- Abandoned accounts that the provider eventually deletes.
- Fake or throwaway signups used to grab a discount or a gated download.
- Old, purchased or imported lists that were never verified.
The pattern behind all five is time plus uncontrolled acquisition. Our breakdown of the top 5 reasons emails hard bounce maps each cause to a specific prevention step.
Bottom line: Don't match bounce text; match the enhanced code. Almost every hard bounce traces back to list age or an unvalidated signup source.
What causes soft bounces, and how many before you remove a subscriber?
Soft bounces come from full mailboxes, oversized messages, receiving-server outages, greylisting, rate limiting, and temporary reputation throttles. Most clear up on retry. The ones that don't are telling you something. Our common soft bounce reasons list pairs each reason with its typical code.
How many soft bounces before removal? ESPs set different defaults, and there is no standard. Here is our recommendation, with the reasoning behind each part:
- Suppress after 3–5 consecutive soft bounces spanning at least two weeks. Spreading the count across time filters out one-day outages. Requiring consecutive failures means a single delivery resets the count.
- Shorten the fuse for "mailbox full." Three consecutive 4.2.2/5.2.2 bounces over about 30 days is a strong abandonment signal.
- Never count block bounces (4.7.x/5.7.x) against an individual address. They reflect your reputation at that provider, not the subscriber's mailbox.
- Cross-check engagement. A soft-bouncing address that hasn't opened or clicked in 6+ months should go sooner. Use that as your own rule of thumb, adjusted to your send frequency.
The full decision tree is in how many soft bounces before removing a subscriber.
Bottom line: Count consecutive soft bounces over time, exclude policy blocks from the count, and suppress persistent "mailbox full" addresses early.
Why do I keep getting mailer-daemon bounce messages?
A "Mailer-Daemon" or "Mail Delivery Subsystem" email is an automated DSN telling you a message failed. Receiving them repeatedly has one of three causes:
- You're sending to bad addresses. This is the usual case for marketers and sales teams. The fix is to clean the list.
- Your account or domain is being spoofed. You receive backscatter: bounces for messages you never sent, because a spammer forged your address. The fix is a DMARC policy (moving toward
p=quarantineorp=reject) so receivers reject spoofed mail instead of bouncing it to you. - Your account is compromised and is actually sending spam. Check your sent folder and change credentials immediately.
Read the enhanced code in each DSN. 5.1.1s point to cause 1. Bounces for messages absent from your sent folder point to cause 2. See why you keep getting mailer-daemon bounce messages.
Bottom line: Repeated mailer-daemon emails come from bad addresses, spoofing or compromise. Your sent folder and the enhanced code tell you which.
How should you triage bounces? A 5-step framework
This is the framework we recommend for any team sending at volume. It works whether you read bounces in an ESP dashboard or parse raw logs.
- Parse every bounce into structured fields. You need the recipient, recipient domain, basic code, enhanced code, diagnostic text, timestamp and campaign. Why: you can't spot patterns in a pile of DSN emails.
- Classify into four buckets by enhanced code subject. The buckets are Address (X.1.x, X.2.1, Microsoft 5.4.1/5.1.10), Transient (4.2.x, 4.3.x, 4.4.x, greylisting), Policy/Reputation (X.7.x) and Content (X.3.4, X.6.x). Why: each bucket has a different owner and fix.
- Check concentration by recipient domain. If one provider accounts for a large share of a bucket, especially Policy, you have a provider-specific reputation or blocklist problem, not a list problem. Why: evenly spread 5.1.1s mean list decay, while 5.7.1s clustered at one domain mean a block.
- Act per bucket.
- Address: suppress immediately and record the lead source.
- Transient: let retries run and apply your soft-bounce threshold.
- Policy: pause or throttle that provider, check blocklists and authentication, and request delisting.
- Content: fix the template and resend.
- Prevent the next round. Verify the list before your next send, add validation to signup forms, and re-verify aging segments on a schedule. Why: steps 1–4 are cleanup. Step 5 is the only one that lowers future bounce rates.
Bottom line: Parse, classify, check concentration, act per bucket, prevent. Most bounce problems are solved at step 3 or step 5.
How do you stop address bounces before you send? (Hands-on tutorial)
You prevent address bounces by verifying the list before the campaign. Here's why that works. Verification tools generally check DNS and MX records, then open an SMTP conversation with the recipient's server and ask whether the mailbox would be accepted, without sending a message. The server answers with the same codes covered above: a 250 for a deliverable mailbox, or a 5.1.1-style rejection for one that doesn't exist. Verification is reading the bounce code in advance.
If you're new to the concept, start with what is email verification. Here's how to do it with Unlimited Verifier, step by step:
- Export your list from your ESP or CRM as CSV. Unlimited Verifier has no native ESP/CRM/Zapier integrations, so the workflow is export, verify, re-import (or the API, covered below). Include any columns you'll want back, such as IDs and tags.
- Create an account. You can sign up free. The Free plan covers 25 lists a month of up to 150 emails each, plus 750 deep verifications a month, which is enough to test the workflow. Free results are kept for 24 hours.
- Upload the file. CSV or Excel up to 10MB is accepted, and the email column is detected automatically. On the Pro plan ($29/month, or $25/month billed annually), each list can hold up to 25,000 emails, with no cap on the number of lists.
- Run verification. Each address is checked for syntax, domain, MX records and the SMTP mailbox. Catch-all domains are detected, and disposable and role-based addresses are flagged. Standard verification is unlimited on every plan, with no per-email fees.
- Review the three result buckets.
- Valid: send normally.
- Invalid: remove. These are the 5.1.1 and 5.1.2 bounces you just avoided.
- Risky: catch-all, disposable or role-based. Decide by policy (see below).
- Export and re-import. Download as CSV, Excel or JSON. Re-import Valid contacts to your ESP, add Invalid to your suppression list, and tag Risky for a separate send or a re-permission campaign.
- Spot-check edge cases. Before a big send, run a few addresses from new lead sources through the free single-email checker. Check your sending domain with the free domain blacklist checker so you also catch the 5.7.x risk.
You can upload and verify a list in a few minutes. On the Pro plan, results stay available for 30 days.
Bottom line: Export, verify, sort into Valid/Risky/Invalid, re-import. That pre-empts the entire Address bucket of bounces.
Worked example 1: Diagnosing a real bounce report
A SaaS company sends a product update to 40,000 contacts. The ESP reports a scary 4.2% bounce rate. Here's the breakdown after parsing (illustrative numbers):
| Code | Count | Bucket |
|---|---|---|
| 550 5.1.1 user unknown | 412 | Address |
| 550 5.1.10 recipient not found (Microsoft) | 96 | Address |
| 550 5.1.2 bad destination host | 74 | Address |
| 550 5.4.1 access denied (Microsoft) | 58 | Address |
| 452 4.2.2 over quota | 38 | Transient |
| 421 4.7.0 deferrals that expired after retries | 70 | Transient |
| 550 5.7.1, all from one regional ISP, text cites a blocklist | 930 | Policy |
| Total final bounces | 1,678 |
(There were also 610 Gmail 421 4.7.0 deferrals in total, but 540 of them delivered on retry, so only the 70 expired ones count as failures.)
The arithmetic:
- Total: 1,678 ÷ 40,000 = 4.2%
- Address bounces: 412 + 96 + 74 + 58 = 640 → 640 ÷ 40,000 = 1.6%
- Policy block: 930 ÷ 40,000 = 2.3%, concentrated at a single provider
- Transient: 108 → 0.27%
What this tells you:
- Over half the bounces (930 of 1,678) are a block, not bad data. Suppressing them would delete 930 real customers at that ISP. The correct move is to check the blocklist cited in the text, request delisting, fix whatever triggered it, and resend to that domain once delisted.
- The 1.6% address-bounce rate is the list-hygiene problem. It sits above the 1% target. All 640 get suppressed now, and the list gets verified before the next send.
- The 540 recovered deferrals at Gmail are an early warning about reputation. Check Postmaster Tools and authentication now, before the deferrals turn into 5.7.x blocks.
Bottom line: A headline bounce rate hides two different problems. Split by bucket and recipient domain before you suppress anything.
Worked example 2: Cleaning a 60,000-contact list before a relaunch
An ecommerce brand hasn't mailed its 60,000-contact list in 14 months and plans a win-back campaign. These are illustrative figures. Old lists decay, but your mix will differ.
Step 1: Fit the list to the plan's limits. The Pro plan caps each list at 25,000 emails, so split the file into three uploads:
- 25,000 + 25,000 + 10,000 = 60,000 (3 lists)
Standard verification is unlimited, so the split costs nothing extra.
Alternative: use the API. Pro includes API access for 100,000 emails a month in batches of up to 10,000 per request, so 60,000 ÷ 10,000 = 6 requests.
Step 2: Read the results.
| Result | Count | Share |
|---|---|---|
| Valid | 49,800 | 83% |
| Risky (3,900 catch-all · 1,300 role-based · 800 disposable) | 6,000 | 10% |
| Invalid | 4,200 | 7% |
Pro's 25,000 monthly deep verifications comfortably cover a second pass on the entire 6,000-address Risky segment. Unlimited Verifier states 99.5% accuracy for deep verification.
Step 3: Compare outcomes.
- Send to all 60,000 unverified: about 4,200 hard bounces → 4,200 ÷ 60,000 = 7%. That's above the 5% level at which Amazon SES says it may review accounts, and a strong negative signal to every mailbox provider.
- Send to the 49,800 Valid only: at an illustrative residual 0.5% bounce rate, ≈ 249 bounces, comfortably under 1%.
- Handle Risky separately: drop the 800 disposables, keep role-based addresses only if they opted in, and send catch-all addresses in small batches to monitor bounces.
Step 4: Cost sanity check. Pro costs $29/month, or $300/year billed annually ($25 × 12). For comparison, if a credit-based tool charged a hypothetical $4 per 1,000 checks, one pass on 60,000 would be $240, and quarterly re-verification would reach $960 a year. Actual credit prices vary by vendor and volume. See our breakdown of email verification pricing.
Bottom line: Verifying a stale list turned a likely 7% bounce rate into roughly 0.5%, within the Pro plan's per-list and API limits.
Why can't some addresses be verified? Catch-all domains explained
A catch-all (accept-all) domain is configured to return 250 OK for any address, real or not. The SMTP check can't distinguish ceo@company.com from zzz123@company.com. These domains are common in B2B, because companies set them up so mail to misspelled employee addresses isn't lost.
Because the server accepts everything at SMTP time, a bad catch-all address often bounces asynchronously later, or simply disappears. Any honest verifier labels these Risky rather than Valid. Unlimited Verifier detects catch-all domains and places them in the Risky bucket. Learn how it handles them on the catch-all verification page.
How to send to catch-all addresses safely:
- Send to them separately from your Valid segment, starting with your most engaged contacts.
- Watch for asynchronous DSNs over the following 24–48 hours.
- Suppress any that bounce, and don't re-mail catch-all addresses that never engage.
Bottom line: Catch-all addresses can't be confirmed by SMTP alone. Segment them, send cautiously, and let real engagement decide.
How do you automate bounce handling and verification?
Automate at two points: at capture, by verifying each new signup in real time, and on a schedule, by re-verifying aging segments in batches. Pair both with your ESP's automatic hard-bounce suppression.
With Unlimited Verifier's REST API, you authenticate with API keys and either verify single emails (ideal for signup forms) or submit bulk batches of up to 10,000 emails per request. API access is included on Pro, covering 100,000 emails a month. You can generate credentials on the API keys page.
Typical patterns:
- Signup form: call single-email verification on submit. Block Invalid, warn on likely typos, and accept Risky with a flag.
- Nightly or weekly job: pull contacts not verified in 90 days, batch them in groups of up to 10,000, and write the status back to your CRM.
- Pre-campaign gate: verify the segment, and only push Valid contacts to the ESP.
The verification engine is open source on GitHub, so technical teams can inspect how checks work. For architecture patterns, retry handling and webhook-style workflows, read our guide to email verification API and automation. There's also a deeper engineering walkthrough on automating verification via API.
Bottom line: Verify at the point of capture and on a schedule. The API turns bounce prevention from a quarterly chore into a pipeline step.
What are the best tools to analyze and prevent bounce codes?
No single tool covers the whole lifecycle. You need something to diagnose bounces after sending, something to monitor reputation, and something to prevent address bounces before sending.
| Tool / approach | Stage | Two concrete differentiators | Specific limitation |
|---|---|---|---|
| Your ESP's bounce reports | After send | Per-campaign codes; automatic hard-bounce suppression | Damage is already done; classification rules vary by ESP and can lump block bounces with hard bounces |
| Google Postmaster Tools | Monitor | Gmail domain/IP reputation dashboards; spam-rate and authentication data | Gmail only; needs meaningful volume before data appears; no per-recipient bounce detail |
| Microsoft SNDS | Monitor | IP-level data for Microsoft consumer mail, including complaint rates and trap hits | IP-based, so of limited use on a shared ESP IP pool you don't control |
| MXToolbox | Diagnose | Blocklist lookups across many lists; DNS, SPF and DMARC checks plus a header analyzer | Diagnoses infrastructure, but doesn't clean lists |
| Unlimited Verifier | Prevent | Unlimited standard verification on every plan, with Valid/Risky/Invalid sorting; catch-all, disposable and role detection plus an open-source engine | Can't fix 5.7.x policy blocks; catch-all addresses can't be confirmed; no native ESP integrations (CSV round trip or API) |
| Credit-based verifiers (e.g. ZeroBounce, NeverBounce) | Prevent | ZeroBounce markets an AI-based scoring feature; NeverBounce (owned by ZoomInfo) emphasizes ESP integrations | Per-email credit costs scale with list size and re-verification frequency |
How we compared (and limitations): This table is based on public documentation and product pages, not hands-on benchmarking. Vendor features and accuracy figures are the vendors' own claims. Features and pricing change, so confirm current details on each vendor's site before buying.
For a broader roundup, see our guide to the best email verification tools and the dedicated comparison of tools to analyze email bounce codes. For a head-to-head of verifiers specifically, read our email verifier comparison. For cost models, our verification pricing breakdown compares credit-based and unlimited plans.
Bottom line: Use your ESP and postmaster tools to diagnose, and a verifier to prevent. For teams re-verifying large lists often, an unlimited model avoids per-email costs that compound.
How should ecommerce and SaaS teams handle bounces?
Ecommerce and SaaS have a specific problem: transactional mail shares reputation with marketing mail. A bounce-heavy promo blast can push order confirmations, password resets and invoices into deferrals and spam folders. That turns a marketing problem into a support and revenue problem.
Priorities that differ from general marketing:
- Verify at signup and checkout. A typo in a checkout email means the customer never gets their receipt, and you inherit a future 5.1.1. Real-time verification at capture fixes both.
- Watch disposable addresses. Free trials and first-order discounts attract throwaway inboxes. Flag them at signup rather than discovering them as bounces later.
- Separate streams where possible. Many teams send transactional and marketing mail from different subdomains or IPs, so a marketing reputation dip doesn't block password resets.
- Treat bounces as a data-quality signal. In SaaS, a 5.1.1 on an active user's account email means that user can't recover their account. Prompt them in-app to update it.
Our guide to email verification for ecommerce and SaaS covers checkout flows and trial-abuse patterns in depth, and there's a companion piece on verification workflows for online stores and software companies.
Bottom line: For ecommerce and SaaS, bounces threaten transactional mail. Verify at capture and keep marketing reputation from bleeding into receipts and resets.
How do bounce codes fit into compliance and list hygiene?
Bounce handling is part of running a lawful, defensible email program, not just a deliverability tactic. Regulations like CAN-SPAM, GDPR and CASL govern consent and unsubscribes rather than bounce rates. But hygiene supports compliance in practical ways:
- Data accuracy. GDPR's accuracy principle expects organizations to keep personal data accurate and up to date. Continuing to process addresses you know are invalid is hard to justify.
- Evidence of good practice. Mailbox providers' requirements (authentication, low complaint rates, easy unsubscribe under Google and Yahoo rules) assume you're actively maintaining your list.
- Suppression lists are records. Keep hard-bounced and unsubscribed addresses on a permanent suppression list so re-imports don't resurrect them. That's a common way old CRM exports reintroduce thousands of dead addresses.
A sensible hygiene cadence: verify every new import before first send, re-verify active segments every quarter or so, and run a re-permission campaign for contacts unengaged for a year or more. More on building a defensible program in email verification compliance and hygiene. For a policy template, see our list hygiene and compliance guide.
If you're building the case internally, our explainer on how verification works and why it matters is a good primer for stakeholders.
Bottom line: Hygiene keeps your data accurate, your suppression list intact, and your program aligned with provider and privacy expectations.
What are the most common bounce-handling mistakes?
- Suppressing every 5xx bounce. 5.7.x codes are policy blocks. Purging those recipients after a blocklist incident permanently deletes good customers. Classify by the enhanced code instead.
- Retrying hard bounces. Re-mailing 5.1.1 addresses "just in case" is exactly the behavior providers penalize. Suppress on the first address-bucket bounce.
- Counting block bounces toward the soft-bounce threshold. That removes healthy subscribers whenever your reputation dips at one provider.
- Ignoring persistent "mailbox full." A 4xx code doesn't mean the address is healthy. Months of 4.2.2 means it's abandoned.
- Parsing bounce text instead of codes. Diagnostic text varies by server and changes without notice. Enhanced codes are standardized.
- Reading only the headline bounce rate. As Worked Example 1 showed, a 4.2% total can hide a 1.6% list problem and a 2.3% block problem that need opposite fixes.
- Re-importing old exports without checking suppressions. This is the most common way dead addresses come back.
- Treating catch-all as Valid. Accept-all servers say yes to everything. Segment and monitor them.
- Verifying once and never again. Lists decay continuously, especially B2B. A list that was clean last year isn't clean now.
- Fixing the list but not the source. If one form or lead vendor produces most of your 5.1.1s, cleaning won't stop the next wave. Add validation at capture.
Bottom line: Most bounce damage comes from misclassification. Use the enhanced code, three buckets, and verification before every major send.
Bounce code triage framework
| Code pattern | Meaning | Action |
|---|---|---|
| 4.x.x | Temporary failure | Retry at least 30 min apart for 4–5 days |
| 5.1.x (e.g. 5.1.1, 5.1.10) | Bad address | Suppress immediately |
| 5.2.1 | Mailbox disabled | Suppress |
| 5.2.2 / 4.2.2 | Mailbox full | Retry, then suppress if it persists |
| 5.7.x (e.g. 5.7.1) | Policy, authentication or reputation block | Fix SPF/DKIM/DMARC and blocklist issues; do NOT purge the list |
| Hard-bounce rate | Below 1% is the target; 2% means investigate | Verify the list before the next send |
Frequently asked questions
What is the difference between a hard bounce and a soft bounce?
A hard bounce is a permanent failure, usually signaled by a 5xx code such as 550 5.1.1, meaning the address doesn't exist or can never receive your mail. A soft bounce is a temporary 4xx failure, such as a full mailbox or a busy server. You can retry soft bounces, but you should suppress hard bounces caused by addressing errors. Policy-based 5xx codes need a fix on your side rather than list removal.
What does bounce code 550 5.1.1 mean?
550 5.1.1 means the recipient mailbox does not exist. It usually comes from a typo, a deleted account, or an invented address. This is a permanent addressing failure, so you should suppress the address immediately and stop mailing it. If you keep sending to 5.1.1 addresses, you raise your hard-bounce rate and signal poor list hygiene to mailbox providers.
What does 550 5.7.1 mean in an email bounce?
550 5.7.1 means the receiving server rejected your message for security or policy reasons. Common causes are blocklisting, failed SPF, DKIM or DMARC checks, or content filtering. The mailbox usually exists. Don't suppress the recipient. Instead, check your authentication records, your blocklist status and your sending reputation, then retry once you have fixed the underlying issue.
How long should I retry a 4xx soft bounce?
RFC 5321 recommends spacing retries at least 30 minutes apart and continuing to try for at least 4 to 5 days before giving up. Most ESPs handle these retries automatically. If the same address soft-bounces across several consecutive campaigns, treat it as effectively dead and suppress it so it doesn't keep dragging down your sender reputation.
What is a good email bounce rate?
Aim for a hard-bounce rate under 1% per send, and start investigating if it reaches 2%. Amazon SES states in its FAQ that it may place accounts under review at a 5% bounce rate. Consistently low bounce rates come from verifying lists before sending, removing invalid addresses quickly, and avoiding purchased or stale lists.
What is the difference between a synchronous and asynchronous bounce?
A synchronous bounce happens during the live SMTP session, when the receiving server rejects the message immediately and your ESP logs the code. An asynchronous bounce happens after the server first accepts the message, then later sends back a delivery status notification (DSN), often called an 'Undeliverable' email. Asynchronous bounces are harder to parse because the diagnostic details sit inside the returned message.
Why do Microsoft and Gmail bounce messages look different?
Every provider writes its own diagnostic text and may add proprietary codes on top of the standard RFC codes. Microsoft uses codes like 5.1.10 (recipient not found) and 5.4.1 (relay access denied). Gmail adds help links and policy references. Always classify by the enhanced status code first, then use the provider's text for detail.
What does the enhanced status code format X.Y.Z mean?
Enhanced status codes, defined in RFC 3463, use a Class.Subject.Detail format. The class (2, 4 or 5) shows success, temporary failure or permanent failure. The subject shows the category: 1 is addressing, 2 is mailbox, 3 is mail system, 4 is network or routing, 5 is protocol, 6 is content, and 7 is security or policy. The detail digit narrows down the exact reason.
Can I prevent email bounces before sending?
Yes, for address-related bounces. Codes like 5.1.1, 5.1.2, and Microsoft's 5.1.10 come from invalid addresses that verification can catch in advance. A verifier checks syntax, domain and MX records, and SMTP mailbox existence, and it flags catch-all domains. Policy bounces need proper SPF, DKIM and DMARC records plus good sending practices.
What does 452 4.2.2 mailbox full mean?
452 4.2.2 means the recipient's mailbox is over its storage quota. It is a temporary soft bounce, so retrying later may succeed once the user frees up space. If the same address stays full across multiple sends over weeks, the mailbox is likely abandoned. Suppress it at that point to protect your reputation.
Cut Bounces and Protect Your Sender Reputation With Unlimited Email Verification
Every invalid address you send to hurts your sender reputation and your inbox placement. Verifying your list before each send means fewer bounces, healthier deliverability, and a predictable cost. With Unlimited Verifier, standard verification is unlimited on every plan, with no per-email fees.
Unlimited Verifier checks syntax, domain, MX records and the SMTP mailbox. It also detects catch-all domains and flags disposable and role-based addresses. Export a CSV from your email platform or CRM, upload and verify the list, then re-import the clean results. You can also automate checks with the email verification API.
| Free | Pro | |
|---|---|---|
| Price | $0 | $29/month ($25/month billed annually) |
| Lists | 25 a month, up to 150 emails each | Unlimited, up to 25,000 emails each |
| Deep verifications | 750 a month | 25,000 a month |
| API access | No | Yes (100,000 emails a month) |
| Result retention | 24 hours | 30 days |
Why teams choose Unlimited Verifier
- Unlimited standard verification on all plans, including Free, with no per-email fees.
- Catch-all detection so you know which domains accept every address.
- Clear Valid / Risky / Invalid results, exportable as CSV, Excel or JSON.
- An open-source verification engine you can inspect on GitHub.
Unlimited Verifier states 99.5% accuracy for deep verification.
Create a free account and verify your next list before you hit send.
Want to test a single address first? Try the free email checker.