International Email Validator
Check Unicode addresses and convert them to punycode.
Tell a hard bounce from a soft one, and from a block.
Or pick a common one
The Email Bounce Code Checker reads a bounce message or a bare SMTP code and says whether it is a hard bounce, a soft bounce or a block aimed at you — three cases that need three different responses.
Paste a bounce — the whole message, or just the code out of it — and get three things: what kind of failure it was, what caused it, and whether the address should come off your list.
The third category is the one that gets missed. A hard bounce means the mailbox does not exist and the address should go. A soft bounce means it was temporarily unavailable and your sender will retry. But a block is neither: the address is perfectly good and the receiver refused *you*, on reputation or authentication grounds. Deleting the address is exactly the wrong response, and it is a common one.
Both the enhanced status codes from RFC 3463 and the basic SMTP reply codes are recognised, and when there is no code at all the phrasing every mail server writes is matched instead — "user unknown", "mailbox full", "greylisted", "blocked using".
A block means the address is fine and you were refused.
Enhanced status codes and basic SMTP reply codes.
Falls back to the phrasing mail servers actually write.
The address that bounced is pulled out of the message.
Remove, retry or fix authentication — stated explicitly.
The whole message, or just the status code from it.
Hard bounce, soft bounce, or a block aimed at you.
What the code means in the words the RFC uses.
Remove, retry, or fix your sending setup — they are different.
A hard bounce is permanent — the mailbox or domain does not exist, and the address should be removed at once. A soft bounce is temporary, usually a full mailbox or a busy server, and your platform will retry it for you.
That the recipient address does not exist on the receiving server. It is the most common hard bounce, and the address should be removed from your list immediately — repeatedly mailing known-dead addresses is one of the fastest ways to damage a sending reputation.
No. 5.7.1 is a policy rejection: the address is fine and the receiver refused you, usually over authentication or IP reputation. Fix SPF, DKIM and DMARC and check whether your sending IP is listed somewhere — do not delete the recipient.
Under 2% is healthy for a list you built yourself. Above 5% and most sending platforms will warn you; above 10% many will suspend the account, because that level of bouncing is what a purchased list looks like.
What people who use the Email Bounce Code Checker think of it. Reviews come from visitors and are posted as written.
No ratings yet
Yours would be the first.
0 reviews
Newest first
No reviews yet
Be the first to rate the Email Bounce Code Checker. It takes half a minute and no account.
Write the first reviewCheck Unicode addresses and convert them to punycode.
Catch gmial.com, yahooo.com and every near miss.
Check any address for syntax, typos and risk.
Validate a DKIM public key and read its real key size.
Remove duplicates, including the ones Gmail hides.
Trim, lowercase, dedupe and drop the bad addresses.
Test an address against the RFC rules, rule by rule.
One report on a list before you spend money sending to it.