Article
7 Best Tools to Analyze Email Bounce Codes in 2026 (Compared)
By Unlimited Verifier Team ·

Summary
The best way to analyze email bounce codes is to combine your ESP's event log, which records the exact SMTP reply for each message, with a pre-send verifier that removes likely-invalid addresses. Reputation dashboards such as Google Postmaster Tools and Microsoft SNDS then show whether bounces come from your list or your sending.The best way to analyze email bounce codes is to pair your ESP's event log, which records the SMTP reply for every message, with a pre-send verifier such as Unlimited Verifier, and to keep hard bounces under 1% of attempted sends. Unlimited Verifier is our top verifier pick because its unlimited standard verification on every plan, including Free, lets you re-check the addresses behind bounce batches without per-email fees. This guide is for marketers, list owners, agencies and SaaS teams who need to read bounce codes and act on them. It is part of our complete guide to email bounce codes.
Quick answer
- Best overall for acting on bounce codes: Unlimited Verifier. It sorts your list into Valid, Risky and Invalid before the next send.
- Best for the exact reason behind each bounce: your ESP's event or bounce log, which keeps the SMTP reply text for each message.
- Best free reputation views: Google Postmaster Tools for Gmail and Microsoft SNDS for Outlook.com.
- Your working threshold: keep hard bounces under 1% of attempted sends. Sources disagree on where warning levels start, so we recommend the stricter number.
Which tools are best for analyzing email bounce codes?
The right tool depends on the question you're asking. A log tool tells you what happened on past sends. A verifier predicts which addresses will bounce next. A reputation dashboard shows whether a mailbox provider treats your sending differently from your list. Most teams need at least one tool from two of these groups.
Quick picks
- Best overall: Unlimited Verifier, for removing likely-invalid addresses before the next send.
- Best for per-message reasons: your ESP's event log.
- Best for Gmail trends: Google Postmaster Tools.
- Best for Outlook.com IP status: Microsoft SNDS.
- Best for self-hosted teams: Postfix or Exim logs.
- Best for domain and blocklist diagnostics: MXToolbox.
- Best for granular status labels: ZeroBounce.
| Tool | Starting price | Free tier | Catch-all handling | Best for |
|---|---|---|---|---|
| Unlimited Verifier | $0; Pro $29/mo ($25/mo billed annually) | Yes: 25 lists/mo of up to 150 emails each, plus 750 deep verifications | Detects catch-alls and sorts them into Risky | Pre-send cleaning driven by bounce history |
| ESP event/bounce logs (e.g., Amazon SES, SendGrid, Mailgun, Postmark) | Included with sending account | Varies | N/A (reports bounces, doesn't verify) | Per-message reply text and timestamps |
| Google Postmaster Tools | Free | Free | N/A | Gmail spam rate and reputation trends |
| Microsoft SNDS | Free | Free (enrollment required) | N/A | IP-level status for Outlook.com |
| Postfix / Exim logs | Free (open source) | Free | N/A | Self-hosted, custom analysis |
| MXToolbox | Free lookups; paid monitoring | Free lookups | N/A | MX, SMTP and blacklist diagnostics |
| ZeroBounce | Varies (credits/subscriptions) | Varies | Dedicated catch-all status | Maximum status granularity |
Bottom line: logs explain the past, verifiers predict the next send, and reputation dashboards show whether the problem is your list or your sending.
How do email bounce codes work?
Every SMTP reply starts with a three-digit code, defined in RFC 5321. Many providers also return an enhanced status code in X.Y.Z form, defined in RFC 3463. The first digit of both tells you the class: 4 means temporary and 5 means permanent. In the enhanced code, the second digit names the subject: 1 for addressing, 2 for mailbox, 4 for network and routing, 6 for message content, and 7 for security or policy.
Two points matter more than the spec. First, providers use the same code for different situations, so the reply text is part of the diagnosis. Second, the code reports the receiving server's decision, which may reflect your sending reputation rather than the subscriber's inbox. Use this triage table as a starting point:
| Code pattern | Usually means | Recommended action |
|---|---|---|
| 550 5.1.1 | Mailbox does not exist | Suppress immediately |
| 550 5.1.2 | Domain or host not found | Suppress; check the domain across your list |
| 554 5.7.1 | Refused on policy or reputation | Don't suppress on one bounce; investigate the sender |
| 421 4.7.0 | Temporary throttling or block | Retry later and watch volume |
| 450 4.x.x | Mailbox temporarily unavailable | Retry; treat as hard after repeated failures |
For soft bounces, our recommended policy is three retries over 7 to 14 days before suppressing. This is a working policy, not an industry standard, so test it against your own history.
Worked example (illustrative). Suppose 90 of your 236 hard bounces are 5.7.x, and 81 of those come from one provider's domain. That pattern points to the provider's policy or your reputation with them, not to list decay. Suppressing those 81 addresses would clean the list without fixing the cause. Reduce volume to that provider and check your reputation signals there instead.
Bottom line: group bounces by enhanced code and reply text, not by the first digit alone.
How we compared (and limitations)
We judged each option on what it lets you do with bounce data:
- Granularity: does it show the raw reply, a per-address classification, or only an aggregate?
- Scope: can you see which addresses are affected, or only the pattern?
- Actionability: does the output become a suppress, retry or investigate decision?
- Cost to run weekly: what does routine use cost, based on published terms?
- Setup effort: what does it take to get the first useful result?
Limitations. This comparison is based on public documentation and vendor-published information. We did not run head-to-head accuracy tests, and any accuracy figure quoted is the vendor's own claim. Pricing changes, so we write "varies" where we aren't certain. A verifier predicts deliverability but cannot see a subscriber's intent, and no tool can tell you why someone stopped reading.
Bottom line: treat any accuracy figure as a claim to test on your own bounce history.
The 7 best tools for analyzing email bounce codes, reviewed
1. Unlimited Verifier (best overall)
Unlimited Verifier is a bulk verifier, not a log parser. You upload a CSV or Excel file up to 10MB, and it runs syntax, domain, MX and SMTP mailbox checks, detects catch-all domains, flags disposable and role-based addresses, and sorts every address into Valid, Risky or Invalid. Use it when your bounce history shows a problem and you need to find the rest of it before the next send.
Key features
- Unlimited standard verification on Free and Pro, with no per-email fees.
- Syntax, domain, MX and SMTP mailbox checks, plus catch-all email verification.
- Automatic email-column detection, and export as CSV, Excel or JSON.
- REST API with API keys: single checks and bulk batches of up to 10,000 emails per request on Pro.
- An open-source verification engine published on GitHub, so technical teams can review how checks are implemented.
Pros
- Re-checking isn't metered, so you can re-verify a batch while you test your rules.
- The three buckets map directly to actions: send, segment, suppress.
- The open-source engine lets your team audit the checks.
Cons
- It doesn't read your ESP's bounce logs or show the SMTP reply from a past send.
- Free results are kept for 24 hours and the Free plan has no API access, so download exports immediately.
- Per-list caps apply: 150 emails per list on Free, 25,000 on Pro. Split larger files.
Best for: teams that want to clean the addresses behind bounce codes before the next send.
Where it falls short: explaining why a specific past send bounced. Use your ESP log for that.
Pricing: Free is $0 and includes 25 lists a month of up to 150 emails each, plus 750 deep verifications. Pro is $29 a month, or $25 a month billed annually, with unlimited lists of up to 25,000 emails each, 25,000 deep verifications a month and API access (100,000 emails a month).
Tip: verifying only your bounced addresses shows the tool catches known failures, not that it predicts future ones. The tutorial below shows how to test for false positives too.
2. Your ESP's event and bounce logs
Sending platforms record each delivery attempt with its reply text and timestamp. Amazon SES labels bounces as Permanent, Transient or Undetermined, with subtypes. SendGrid exposes per-message events in its Activity Feed, Mailgun publishes event logs, and Postmark groups bounces by type. Check each provider's current documentation for fields and retention, since these change.
Key features
- Per-message reply text and timestamps, as the receiving server returned them.
- Provider classification labels, plus event export (varies by provider).
Pros
- The record closest to what the receiving server actually returned, recipient by recipient.
- Included with your sending account, with no added setup.
Cons
- Labels are the provider's interpretation. A policy rejection can be labeled as a hard bounce, so read the reply text, not just the category.
- Retention windows vary, so export grouped data before records roll off.
- It cannot forecast which addresses on your list will bounce next.
Best for: the source of truth for past sends.
Where it falls short: prediction. Pair it with a verifier.
Pricing: included with your sending account; varies by provider.
Tip: before each campaign, export hard bounces grouped by enhanced code. Compare them with examples of hard bounce messages to see what each reply looks like.
3. Google Postmaster Tools
Google's free dashboard reports aggregated data for senders with enough Gmail volume, including spam rate, domain and IP reputation, authentication and delivery errors. Google's sender guidelines say to keep the spam rate below 0.1% and never let it reach 0.3%. You can access the dashboard at postmaster.google.com.
Key features
- Spam rate trends, domain and IP reputation, authentication status and delivery errors.
Pros
- Official, free, and Google's own view of your sending.
- Helps separate a list problem from a reputation problem when Gmail bounces rise.
Cons
- It is aggregated, so it never shows a specific address or the reply for one message.
- It covers Gmail only, and shows nothing until volume is high enough.
Best for: deciding whether Gmail bounces come from your list or your reputation.
Where it falls short: any per-address question.
Pricing: free.
Tip: if Gmail 5.7.1 rejections rise alongside your spam rate, reduce sends to your oldest, least-engaged segment before deleting anyone. Reputation recovers when you send less to people who don't engage.
4. Microsoft SNDS
Smart Network Data Services is Microsoft's free service for senders using their own IP addresses to deliver to Outlook.com and Hotmail. It shows IP status and complaint-related data for enrolled addresses. Enrollment steps are on Microsoft's sender support pages.
Key features
- IP-level status and complaint data for enrolled IPs, at no cost.
Pros
- Shows IP-level data for Outlook.com that the Gmail-focused dashboard does not cover.
- Useful when a dedicated IP is your Outlook.com identity.
Cons
- It is IP-based. Shared IPs, or sending through several platforms, blur the signal.
- You need enrollment and an IP you control, and data can be thin at low volume.
Best for: dedicated-IP senders with meaningful Outlook.com volume.
Where it falls short: shared-infrastructure senders and any per-recipient detail.
Pricing: free.
Tip: when Outlook 550 or 554 rejections rise while your authentication checks pass, look at the IP view before assuming the list is at fault.
5. Postfix or Exim logs (self-hosted)
If you run your own mail server, the MTA logs record every delivery with its response. Postfix writes a dsn= field on bounced and deferred lines, so you can count enhanced codes with one command. Log paths vary by system; many Linux servers use /var/log/maillog or /var/log/mail.log.
grep -oE "dsn=[45]\.[0-9]+\.[0-9]+" /var/log/maillog | sort | uniq -c | sort -rn
Key features
- A complete delivery record, with enhanced codes on Postfix lines and easy command-line counting.
Pros
- Free, complete and fully customizable.
- Grouping by recipient domain often reveals the real story faster than grouping by address.
Cons
- It needs sysadmin skills, log rotation and parsing.
- The command counts 4xx and 5xx together, so split them in the next step. It also has no classification layer, so you interpret each code yourself.
- Exim writes failure responses in its own layout, so the command above needs adapting.
Best for: self-hosted teams with engineering time.
Where it falls short: anyone on a hosted sending platform.
Pricing: free and open source.
Tip: group by recipient domain. If one provider accounts for most of your 5.7.x bounces, the cause is more likely that provider's policy or your reputation with them.
6. MXToolbox
MXToolbox is a web diagnostic suite covering MX lookups, SMTP tests and blacklist checks. It helps when a 5.1.2 or 5.7.x pattern traces back to your own domain configuration or a blocklist listing, rather than to individual addresses.
Key features
- MX lookups, SMTP tests and blacklist checks in a browser.
Pros
- Quick, with no installation, for checking your own domain and IP setup.
Cons
- It tests one domain or IP at a time and does not classify your list.
- Blacklists differ, so a clean result on one list is not a clean bill of health.
Best for: troubleshooting a domain or IP.
Where it falls short: list-level analysis.
Pricing: free lookups; paid monitoring. Confirm current terms on the site.
Tip: after any DNS change, run an SMTP test before sending to the full list, especially if 5.1.2 bounces have spiked.
7. ZeroBounce
ZeroBounce is a verifier with a notably granular status system: valid, invalid, catch-all, unknown, spamtrap, abuse and do_not_mail, each with sub-statuses. The vendor also describes AI scoring for catch-all addresses as a way to rank likely engagement.
Key features
- Seven top-level statuses with sub-statuses, separate spamtrap and abuse labels, and vendor-described AI scoring for catch-alls.
Pros
- Spamtrap and abuse labels give suppression signals that a three-bucket output does not.
- Useful for teams that want detailed labels to build rules around.
Cons
- Seven top-level statuses mean more rules to write and maintain.
- It is credit-based, so routine re-checks draw on paid volume. Confirm current rates.
Best for: teams that want maximum label detail and can budget per check.
Where it falls short: frequent re-checking on a fixed budget.
Pricing: credits and subscriptions; the vendor advertises a small free allowance. Check current terms.
Tip: suppress spamtrap and abuse outright, and decide do_not_mail case by case, since its sub-statuses include categories you may want to keep.
How do you analyze bounce codes with Unlimited Verifier?
This process turns a bounce log into a cleaner list in one working session. The numbers below are hypothetical, to show the arithmetic.
Example: your last send went to 40,000 addresses and produced 236 hard bounces, a 0.59% rate (236 ÷ 40,000). That is under the 1% target, so the remaining work is about trends and policy bounces, not a crisis.
- Export the bounce log for the last two to four sends, with address, reply text, enhanced code and date. Calculate rates against attempted sends.
- Separate the codes. Route 5.x.x to suppression review, 4.x.x to the retry queue, and 5.7.x to a sender investigation.
- Split the hard bounces into lists. On Free, each list holds up to 150 emails, so 236 addresses become two lists (150 and 86) and use 2 of your 25 monthly lists. On Pro, each list holds up to 25,000.
- Upload and verify each list. Email-column detection is automatic. If you don't have an account, sign up first.
- Measure the result. Suppose 190 of the 236 come back Invalid (illustrative): 190 ÷ 236 = 80.5%. This shows the verifier catches known failures. It does not yet show that it predicts future ones.
- Test for false positives. Verify a random sample of addresses that delivered last time, say 500 (illustrative). If 15 come back Invalid, that's 3%. Inspect those 15 by hand, or hold them out of the next send and compare the outcome, before any bulk suppression.
- Run the full active list. Keep Valid, suppress Invalid, and segment Risky. The Free plan's 750 deep verifications a month can cover a Risky segment of up to 750 addresses.
- Download results right away. Free results are kept for 24 hours and Pro results for 30 days. Export as CSV, Excel or JSON.
- Re-import. Add Invalid addresses to your ESP's suppression list, or they will return on the next import. Handle 5.7.x separately, because cleaning the list does not fix a policy block.
- Automate weekly signups (Pro). Generate API keys and send new signups in batches of up to 10,000 per request, within the 100,000-email monthly allowance. For background, see the email verification API and automation overview. For a single address, the free email checker works too.
Bottom line: verify the bounced addresses, test for false positives, then clean the list and automate new signups.
How should you choose a bounce analysis tool?
Choose by the question you need answered:
- "What exactly happened on the last send?" Use your ESP's event log.
- "What will bounce on the next send?" Use a verifier such as Unlimited Verifier or ZeroBounce.
- "Are Gmail bounces a list problem or a reputation problem?" Use Google Postmaster Tools.
- "Is my dedicated IP healthy at Outlook.com?" Use Microsoft SNDS.
- "Is my domain or IP misconfigured or listed?" Use MXToolbox.
- "I run my own servers and want everything." Use Postfix or Exim logs.
If budget is tight, the no-cost stack is your ESP logs, Postmaster Tools, SNDS and a free verifier allowance for small batches. If you want ESP syncing without file handling, NeverBounce publicly markets Sync integrations, and if you want a tunable score, Kickbox's Sendex rating is built for threshold rules. Compare their pricing against how often you re-check. For signup-time checks, read about real-time email validation. For a structured decision, see how to choose an email verifier and the best email verification tools overview. Also weigh your email verification pricing tolerance.
Bottom line: use logs for the past, verifiers for the future, and dashboards for reputation.
What mistakes do senders make when reading bounce codes?
- Judging by one bounce. A single 5.7.1 can be a temporary policy event. Look for a pattern across several sends.
- Suppressing policy bounces as invalid addresses. A 554 5.7.1 is a sender-side signal; suppressing the address does not fix it.
- Retrying hard bounces. Repeatedly sending to a 5.1.1 address adds bounces and hurts reputation.
- Treating a verifier's Valid as a guarantee. Valid means the address passed checks, not that it will read your mail.
- Re-importing without suppressing. Invalid addresses return on the next import unless they go on your suppression list.
- Assuming verification proves consent. A deliverable mailbox is not permission to email. Review your email verification compliance and hygiene practices and the FTC's CAN-SPAM compliance guide.
- Ignoring the causes. If you're unsure what drives your hard bounces, start with the top five causes of hard bounces.
Bottom line: most bounce-analysis errors come from reading codes in isolation.
Verdict
For most senders, the best setup is a log for what happened, a verifier for what comes next, and a reputation dashboard for the trend. Unlimited Verifier fills the verifier role, with unlimited standard checks on every plan, Valid/Risky/Invalid output and API access on Pro. It doesn't read your bounce logs, so pair it with your ESP's event data. Start on the Free plan, test your last hard bounces for false positives, then run the full list. For ongoing practice, the list maintenance routine covers the rest.
Bottom line: read the codes, verify before you send, and keep hard bounces under 1%.
Bounce code triage framework
| Code pattern | What it means | Action |
|---|---|---|
| 5xx, e.g. 550 5.1.1 | Permanent failure, address unknown | Remove the address and suppress it from future sends |
| 4xx, e.g. 421 4.7.0 | Temporary failure, often throttling | Let the server retry, and slow sending if it repeats |
| 5.7.x policy codes | Blocked for policy or reputation | Check Postmaster Tools or SNDS, then review content and authentication |
| Repeated soft bounces | Mailbox persistently unavailable | Convert to suppression after a set number of retries |
| Bounce rate above 1% | List or sending quality issue | Verify the list before the next send and audit the source |
Frequently asked questions
What is the best free tool to analyze email bounce codes?
Your ESP's event or bounce log is usually the best free starting point, since it records the SMTP reply text for each message. Pair it with Google Postmaster Tools for Gmail trends and Microsoft SNDS for Outlook.com IP status. Free verifier tiers can also re-check addresses that bounced.
What do 5xx and 4xx bounce codes mean?
A 5xx SMTP reply is a permanent failure, so the message should not be retried. A 4xx reply is a temporary failure, and the sending server should retry later. These classes are defined in RFC 5321, and the first digit tells you which category applies.
What is the difference between a hard bounce and a soft bounce?
A hard bounce is a permanent delivery failure, usually from a nonexistent or invalid address, and those addresses should be removed. A soft bounce is temporary, such as a full mailbox or a server that is busy, and it may succeed on retry. Repeated soft bounces often become hard bounces over time.
Where can I find the exact bounce reason for a message?
Look in your ESP's event, activity or bounce log for the message ID or recipient address. The log typically stores the SMTP reply text and timestamp. If you self-host, check the mail server logs such as Postfix or Exim, which record the remote server's response.
What is an enhanced status code in email?
An enhanced status code is a structured code in X.Y.Z form, defined in RFC 3463, that appears alongside the three-digit SMTP reply. The first digit shows success (2), persistent transient failure (4) or permanent failure (5). The middle and last digits give more specific detail, such as a bad mailbox.
Can an email verifier catch every bounce?
No. A verifier predicts likely bounces before you send, but it cannot know everything about a mailbox, and some providers accept mail and bounce it later. Verifiers work best as a filter to reduce hard bounces, combined with monitoring of your actual bounce logs after each campaign.
How do I check if bounces are hurting my sender reputation?
Use Google Postmaster Tools to view Gmail spam rate and domain reputation, and Microsoft SNDS to check IP status for Outlook.com. Compare these trends with your bounce rate by provider. If reputation drops after a list import, the list quality is the likely cause.
What hard bounce rate is too high?
Many senders aim to keep hard bounces under 1 percent of attempted sends, which is the stricter threshold used in this guide. Industry sources do not agree on one exact warning level, so treat 1 percent as a conservative working target and investigate any sustained rise in bounces.
How should I handle catch-all email addresses?
Catch-all domains accept mail for any address, so a verifier cannot confirm that a specific mailbox exists. Many teams place these addresses in a Risky group, send to them more cautiously, and watch engagement and bounce signals over time rather than treating them as confirmed valid.
Do I still need server logs if my ESP provides bounce data?
Often not for routine work, because ESP logs cover most needs. Self-hosted server logs add value when you run your own mail infrastructure, need custom analysis, or want to diagnose delivery problems that the ESP summarizes away.
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.