Find the addresses that will bounce before you hit send. Paste one, or up to 50, and we sort them into the ones that will hard bounce, the ones that won't bounce but shouldn't be mailed, and the ones that need a mailbox check.
A hard bounce is permanent. The address or the domain doesn't exist, and sending again gives the same answer. A soft bounce is temporary: a full mailbox, a server that's down, a receiver slowing you down. Your ESP retries soft bounces for a while and then gives up.
Hard bounces are the ones you can prevent, because the address was bad before you sent anything. Some are visible from DNS alone: a domain with no mail servers can't accept mail for anyone, and this page catches those. The rest are mailboxes that existed once. Someone changed jobs, an account was closed, a free inbox expired after months unused. The domain still works, so nothing looks wrong until the mail server refuses the message. Catching those takes a mailbox check before you send.
The longer version, with how ESPs convert repeated soft bounces into hard ones, is in hard bounce vs soft bounce.
The usual line is a hard-bounce rate under about 2% of messages sent. That figure is a rule of thumb shared across ESPs, not a number any mailbox provider publishes, and some ESPs start asking questions sooner. Past it, expect throttling, a review of your account, or more of your mail landing in spam, because a sender who keeps hitting dead addresses looks like one who bought or scraped the list.
Lists decay as people move on, so a list that was clean last year isn't clean now. The fixes, in the order that pays off fastest, are in how to reduce your email bounce rate.
A bounce message carries a three-digit SMTP reply and, usually, an enhanced status code like 5.1.1. The first digit is what matters most: 5 means permanent, 4 means try again later. These are the ones you'll see most often.
| Code | Type | What it means | What to do |
|---|---|---|---|
| 550 5.1.1 | Hard | The mailbox doesn't exist. The most common hard bounce: a typo, or someone who left the company. | Suppress the address. |
| 550 5.1.2 / 5.1.10 | Hard | The domain is wrong or has no mail route (5.1.10 is Microsoft's "recipient not found by lookup"). | Suppress, or correct the domain if it's a typo. |
| 550 5.4.1 | Hard | Recipient address rejected, often from Microsoft 365 when the mailbox isn't in that tenant. | Suppress. |
| 552 5.2.2 / 452 4.2.2 | Soft | The mailbox is full. The account exists but is over quota, which on an old address often means it's been abandoned. | Retry later. Suppress after repeated failures. |
| 421 / 451 4.7.x | Soft | Deferred: greylisting, rate limiting, or the receiver is wary of your sending IP or domain. | Let your ESP retry. If it's widespread, look at your reputation and authentication. |
| 550 5.7.1 / 554 5.7.x | Block | Rejected by policy: a blocklist, failed SPF/DKIM/DMARC, or content. This is about you, not the address. | Don't suppress the address. Fix the cause, then resend. |
| 4.4.7 | Soft | Delivery expired: the receiver kept deferring until your server gave up. | Treat as soft. Check whether that domain is throttling you. |
A 5.7.x block is the odd one out: it's permanent for that message, but it's a verdict on your sending, not on the address. Suppressing those addresses hides the problem. If they appear in numbers, check your SPF, DKIM and DMARC first.
Upload a CSV of up to 100,000 addresses. Each row comes back with a status, a sub-status saying why, and a confidence score, so you can drop the invalids, hold back the risky ones and send the rest. Addresses we can't settle are refunded.
Paste it in above. An address with bad syntax or a domain with no mail servers will hard bounce, and this tool catches both from DNS without sending anything. The remaining question is whether the mailbox itself still exists, which needs a check against the mail server. That runs free on an account with 100 credits.
A hard bounce is permanent: the address or domain doesn't exist, and sending again will fail again. A soft bounce is temporary: a full mailbox, a server that is down, or a receiver deferring you. Your ESP retries soft bounces and suppresses hard ones.
Keep hard bounces under about 2% of messages sent. That is a common rule of thumb across email service providers rather than a published standard, and several ESPs review or pause accounts well before it. A list that has been verified recently usually sits far lower.
Because some bad addresses never bounce. A spam trap accepts your mail and records that you sent it. A misspelled domain that someone has registered, like a typo of gmail.com, accepts the message and delivers it to whoever owns that domain. A disposable inbox accepts mail until it vanishes. A bounce checker that only looks for bounces misses all three.
Up to 50 per check, pasted one per line or separated by commas. For a full list, upload a CSV of up to 100,000 addresses on a free account; every row comes back with a status, a sub-status and a confidence score.
No. The list is held in memory for the length of the request and is not written to disk, to a database or to a log. No email is sent to any address.
Related terms
Upload a CSV and get back the addresses that are safe to send. 100 free credits to start, no card, and no charge for the ones we can't verify.