Email Verification Statuses Explained: What Every Result Means

You run a list through an email verifier and every address comes back with a label: valid, risky, catch-all, unknown, disposable. But what do these statuses actually mean, and more importantly, what should you do with each one? Getting this wrong is expensive. One marketer ran 12,000 addresses through three different verifiers in the same week and the tools disagreed loudly: one marked 847 addresses risky, another called 312 of those same addresses valid, and a third returned unknown for 600 that the others had clear opinions on.

That disagreement is the reality of email verification in 2026. Tools promising 98 to 99% accuracy cannot always agree on a sample you could count on your fingers. The reason is that most people never learn what these status codes mean at the protocol level, or which ones are hard technical facts versus soft judgment calls.

This guide explains every email verification status you will encounter. It covers the four standard industry categories that nearly every tool uses (valid, invalid, risky, unknown), then breaks down each specific status in detail, including the granular results MailTester.Ninja returns: Accepted, Limited, Rejected, Disposable, No MX, Catch-All, MX Error, Timeout, SPAM Block, and Greylisted. By the end, you will know exactly how to act on each result.

How Email Verification Produces a Status

Every email verification status comes from the same underlying technical process. Understanding the sequence helps you interpret what each label is really telling you. Most verifiers follow four steps, and the status you get reflects how far through this sequence an address gets.

At the SMTP stage, the verifier connects to the recipient's mail server and issues a RCPT TO command asking whether the mailbox exists, without ever sending an actual email. The server's response determines the core result: a 250 response means the address is valid, while a 550 response means the mailbox does not exist. Some servers return ambiguous responses, which is what produces unknown results. As infrastructure providers like Twilio SendGrid note, SMTP acceptance does not always equal final deliverability. For the full picture of how this fits into your email program, see our complete email deliverability guide.

SMTP Response Codes Behind Each Status

Every email verification status ultimately traces back to a numeric SMTP response code returned by the recipient mail server. These codes are the raw signal that tools interpret into friendly labels. Knowing them helps you understand exactly why an address received its status, and they are the same codes you will see in bounce messages.

The first digit tells you the category at a glance. A code starting with 2 means success, the action worked. A code starting with 4 is a temporary failure, meaning you should retry later, which is what produces unknown and greylisted statuses. A code starting with 5 is a permanent failure, which produces invalid and rejected statuses and means you should remove the address.

The 4 Standard Email Verification Status Categories

Despite different naming across tools, nearly every email verifier sorts addresses into four top-level categories. Learning these four makes every tool's output readable, even when the specific labels differ.

Valid / Deliverable / Accepted

This is the status you want. It means the verifier confirmed, with high confidence, that the mailbox exists and is associated with a valid, active account that can receive email. These are the best contacts for your campaigns and are safe to send to without restriction.

Across the industry you will see this same outcome labeled Deliverable (Verifalia, Emailable), Valid (Hunter, Snov.io), or simply OK. They all mean the same underlying thing: the SMTP server returned a positive 250 response confirming the mailbox.

Invalid / Undeliverable / Rejected

This status is the clear opposite. The address failed verification because the mailbox does not exist, the domain cannot receive mail, or the format is broken. Sending to these addresses produces hard bounces, which directly damage your sender reputation, so they should be removed from your list immediately.

Other tools call this Undeliverable (Verifalia, Emailable), Invalid (Hunter, Snov.io), or break it into sub-reasons like Invalid Domain and Invalid Syntax. The common thread is certainty: the verifier knows the address cannot receive mail.

Risky and Its Subtypes

Here is where verification gets nuanced. Risky is not a single protocol response. It is a tool-level judgment that an address is technically deliverable but carries elevated risk, whether because of how the domain is configured or what kind of address it is. The risky bucket usually contains several distinct subtypes, each needing different handling.

A fourth common risky subtype is the role-based address, like info@, sales@, or support@. These exist but are usually shared among several people and tend to generate high spam complaint rates, so many tools (notably Snov.io) flag them as risky by default. They are a business judgment call, not a protocol fact.

Unknown and Its Subtypes

Unknown does not mean an address is bad. It means the verification could not be completed, usually because the recipient server prevented a definitive answer. These addresses often need a retry rather than removal. Several specific conditions produce an unknown result.

Across tools, this category appears as Unknown (Hunter, Emailable), Blocked (Hunter), or specific failure reasons. The shared meaning is always the same: the verifier needs another attempt, not a deletion.

Every MailTester.Ninja Status Explained

MailTester.Ninja returns more granular statuses than the basic four-bucket model, which gives you clearer guidance on exactly why an address landed where it did. Here is the complete reference, mapped to the standard categories.

Email Verification Statuses Across Different Tools

One of the most confusing parts of email verification is that every tool uses its own vocabulary for the same underlying results. An address labeled Accepted in one tool is Deliverable in another and Valid in a third. This table maps the equivalent statuses across the major verification tools so you can translate any result.

Notice that MailTester.Ninja breaks each category into more granular statuses than most competitors. Where a tool might simply return Unknown, MailTester.Ninja tells you specifically whether the issue was a Timeout, Greylisting, a SPAM Block, or an MX Error, so you know exactly why an address could not be verified and whether a retry is worthwhile.

This is why comparing tools on labels alone is misleading. What matters is the accuracy of the underlying verification, the granularity of the statuses, and the pricing model. A tool that returns a vague Unknown and charges you for it is far less useful than one that tells you precisely why an address failed and prices fairly. For a deeper comparison, see our guide to the best email verification tools.

Why Verifiers Disagree on the Same Email

If you have ever run the same address through two tools and gotten different answers, you are not imagining it. The disagreement is real and it has specific causes. Understanding them helps you trust the right result.

How to Act on Each Status

Knowing what a status means is only half the value. The other half is having a clear policy for each one. Here is a simple, proven framework you can apply to any verification result.

The single most effective habit is to build this policy into your workflow so it runs automatically: valid addresses get sent, invalid ones get blocked, catch-all gets segmented, and unknown gets held for a recheck. Verifying at the point of capture, then again before each major send, keeps your list clean without manual effort. This protects your sender reputation and keeps your bounce rate low on every campaign.

Frequently Asked Questions

About the author

Danila Kozlov

COO at MailTester.Ninja

Danila has spent the last few years deep in email deliverability, helping SaaS companies and growth teams fix the infrastructure problems that silently kill their outbound results. As COO of MailTester.Ninja, he oversees product and operations with a single obsession: making email verification fast, accurate, and genuinely useful for the people who need it most.