How to read a bounce with this tool
Copy the failure line
Open the delivery failure email (it often comes from
mailer-daemonorpostmaster) and copy the paragraph with the numbers in it. Copying the whole message is fine: the tool finds the codes on its own.Paste it into the box
The result appears as you paste. If you only have the code, type it, for example
421 4.7.0or simply5.1.1.Check the verdict colour first
Amber means a temporary failure that your sending server should retry. Red means a permanent refusal: sending the same message again will fail again and can harm your reputation.
Read the provider note
When the text carries a fingerprint from Gmail, Microsoft, Yahoo, Spamhaus or a greylisting server, a note explains that provider's meaning and links to a full guide where we have one.
Act on the address or on your setup
Address problems (unknown user, disabled mailbox) mean the contact comes off the list. Policy problems (authentication, reputation, rate) mean the fix is on your side, and the whole campaign may need to slow down.
Two codes in one line, and why both matter
A typical rejection reads 550 5.1.1 Recipient address rejected. The first number, 550, is the basic reply code defined in RFC 5321. Its first digit gives the class: 2 is success, 3 means the server wants more input, 4 is a temporary failure and 5 is a permanent one. The second and third digits narrow the topic, but only loosely; 550 alone can mean anything from a missing mailbox to a spam block.
The second number, 5.1.1, is an enhanced status code from RFC 3463. It is written as class, subject and detail. The class repeats the soft or hard verdict. The subject says which part of the system had the problem: 1 for addresses, 2 for the mailbox, 3 for the receiving mail system, 4 for network and routing, 5 for the SMTP conversation itself, 6 for message content and 7 for security and policy. The detail pins it down, so 5.1.1 is an unknown mailbox while 5.7.1 is a refusal by policy.
Because the enhanced code is far more specific, the tool reads it first and uses the basic code to fill in the picture. Where a server sends a detail number that is not in the registry, the tool falls back to the general meaning of that subject and says so, rather than guessing.
Worked example: a prospect list after its first send
Suppose you sent a short introduction to 120 joinery firms gathered from a map search, and four messages came back. Pasting each bounce gives four quite different answers.
The first two are address problems: one mailbox no longer exists and one is full. The third is greylisting, which needs no action because your server retries by itself. The fourth is the one to worry about: Gmail is saying the message was not authenticated, which will affect every Gmail and Google Workspace recipient on the list, not just this one.
550 5.1.1 <office@harbourjoinery.example>: Recipient address rejected: User unknown 552 5.2.2 <dan@oakandpine.example>: Mailbox full 451 4.7.1 <info@quaysidejoinery.example>: Greylisted, please try again in 300 seconds 550-5.7.26 This mail has been blocked because the sender is unauthenticated.
5.1.1 Permanent Unknown mailbox: remove and suppress 5.2.2 Permanent Mailbox full: retry once later, then drop 4.7.1 Temporary Greylisting: leave it, the retry will pass 5.7.26 Permanent Gmail authentication failure: fix SPF, DKIM and DMARC before sending more
The codes cold emailers meet most often
Most bounces in B2B outreach fall into a handful of patterns. The full list of reply and enhanced codes is in the tool under Browse every code.
| Code | What it usually means | Whose problem |
|---|---|---|
| 5.1.1 | The mailbox does not exist; common when staff leave or a list is old | The list: remove the address |
| 5.1.10 / 556 | The domain publishes a null MX and never accepts mail | The list: remove every address at that domain |
| 4.2.2 / 5.2.2 | Mailbox full; often a sign the inbox is no longer read | The recipient, but treat it as a warning |
| 4.7.0 / 421 | Rate limiting or a reputation throttle | Your sending pattern: slow down |
| 5.7.1 | Refused by policy: reputation, block list or content | Your reputation or your list quality |
| 5.7.23 / 5.7.24 | SPF failed, or the record could not be evaluated | Your DNS |
| 5.7.26 | Several authentication checks failed together | Your DNS: SPF, DKIM and DMARC |
| 5.4.5 | Your account's daily sending allowance is used up | Your volume per mailbox |
Soft bounces are not always harmless
A 4xx reply asks your server to try again, and mail servers do so automatically for a period, often several days, before giving up with a final report such as 4.4.7 (delivery time expired). The temporary class therefore describes the server's view of the moment, not your prospects of getting through.
For outreach, a run of 421 or 4.7.0 replies from one provider is an early warning that you are sending faster, or to more unengaged people, than that provider will accept from your domain. Pressing on usually turns temporary deferrals into permanent 5.7.x refusals. The sensible response is to lower the hourly rate, spread sends across the day and look at whether the list itself is the problem.
Hard bounces deserve the opposite treatment. Retrying an unknown mailbox achieves nothing, and receiving servers keep count of how often a sender tries addresses that do not exist. A high hard bounce rate is one of the clearest signals of a scraped or bought list, which is why it is worth cleaning and verifying before the first send rather than after it.
Words you will see in bounce messages
- NDR
- Non-delivery report: the email your own server sends you when it gives up on a message.
- MAILER-DAEMON
- The automated sender name many servers use for bounce messages.
- Greylisting
- A filter that turns away first attempts from unknown senders with a 4xx code, on the basis that genuine servers retry and spam software often does not.
- Null MX
- A DNS record (RFC 7505) by which a domain declares that it accepts no email at all.
- Suppression list
- Addresses you must not email again: hard bounces, unsubscribes and complaints.
Questions people ask
What is the difference between 550 and 5.5.0?
550 is the basic SMTP reply code, a three-digit number defined in RFC 5321. 5.5.0 is an enhanced status code from RFC 3463, written with dots, where the middle number is the subject. Servers usually send both on the same line, such as 550 5.1.1. The enhanced code is the more precise of the two, so read it first when it is present.
Should I retry a 4xx bounce myself?
Normally no. Your sending server or provider retries temporary failures automatically over hours or days. Resending by hand creates duplicates and can make rate limiting worse. If the same provider keeps deferring you, lower your sending rate and review the list rather than retrying harder.
Why does Gmail say my mail is unauthenticated when I have an SPF record?
Gmail's 5.7.26 refusal appears when authentication fails overall, not only when a record is missing. Common causes are an SPF record that does not include the service you actually send through, a broken DKIM signature, or a DMARC record whose domain does not align with the From address. Check SPF with the SPF checker, then DKIM and DMARC.
Is a mailbox full bounce temporary or permanent?
It can be either, depending on the server: you may see 452 4.2.2 or 552 5.2.2. Even when it is temporary, a mailbox that stays full for weeks is usually abandoned. Try once more after a few days and then treat the address as unusable.
Does anything I paste get sent to a server?
No. The full code list and the provider notes are part of this page, and the reading happens in JavaScript in your browser. You can disconnect from the internet after the page has loaded and the tool still works.
Can a code tell me the address was valid?
Only weakly. A 250 reply to the recipient means the server accepted it at that moment, but many servers accept every address and bounce later, and catch-all domains accept mail for any name. Proper verification combines syntax, mail server records and, where possible, a mailbox check.
Where your data goes
Everything runs in your browser. The code database and the provider notes are built into this page, so the bounce text you paste, including any email addresses in it, is never uploaded, stored or logged.
Checked against the tool on