Transform your risky emails into valid leads with ScrubbyLearn how
Email Validation

Email Verification Statuses Explained: What to Do With Each Result

Valid, invalid, catch-all, unknown, risky, role, disposable: a verification report is only useful if every status has a next step. What each result actually means, the myths that lead to bad decisions, and a routing table you can apply to any list.

November 16, 2026
9 min read
Three shallow trays on a dark green floor sorting spheres by result, glowing mint in one, coral in another and amber in the third, with more spheres falling in, beside the headline "Every status needs a next step."

Every verification status needs a next step, and “valid” and “invalid” are the only two that are simple. Send to valid, remove invalid, and put everything in between, catch-all, unknown and risky, through a second check before it goes anywhere near a campaign. Role and disposable addresses are policy decisions, not deliverability verdicts.

Most teams look at a verification report the same way. They keep the valid rows, delete the invalid ones, and then stare at the middle of the file wondering what to do with the rest. Some delete it all. Some send to it all. Both are expensive.

This guide goes through the statuses you’ll see, what each one actually tells you, the myths that cause bad calls, and a routing table you can apply to any list from any verifier.

Why Verifiers Disagree on Names

Before the statuses themselves, a warning: there’s no standard vocabulary. One tool says “accept-all”, another says “catch-all”, a third folds the same addresses into “risky”. “Unknown” in one report can mean the server timed out; in another it covers anything the tool couldn’t settle.

So read your verifier’s documentation for what each label means in practice. If you’ve run a list through two tools and got different answers, our guide to reconciling conflicting verification results covers how to settle them. The categories below cover the meanings behind the labels.

The Statuses, One by One

Valid (Deliverable)

The receiving server confirmed the mailbox exists and accepts mail, and the server isn’t one that accepts everything. This is the result you want.

What it doesn’t mean: that the address is safe forever, that the person reads it, or that your email will land in the inbox. It describes the mailbox on the day of the check. Placement depends on your domain, content and sending patterns.

Next step: send. If the list waits weeks before a campaign, re-check it first. See how often to re-verify.

Invalid (Undeliverable)

The server said the mailbox doesn’t exist, the domain has no mail server, or the address isn’t formatted as a real address could be. These are the addresses that would hard bounce.

Next step: remove, and add them to your suppression list so the next import doesn’t bring them back. Our suppression list guide shows how to set one up.

Catch-All (Accept-All)

The domain’s server accepts mail for any address, real or made up. A standard check asks “does this mailbox exist?” and the server says yes to everything, so the check can’t tell a real person from a typo. What a catch-all email account is explains why companies configure servers this way.

Next step: don’t send yet, and don’t delete either. Put these addresses through a check that goes beyond the server handshake.

Unknown

The verifier couldn’t get an answer. Common reasons: the server didn’t respond in time, it was temporarily unavailable, it used greylisting to delay unfamiliar connections, or it blocked the verification attempt.

Next step: retry later. Many unknowns resolve on a second attempt. Whatever stays unknown goes to the same deeper check as catch-all. Our guide to validating unknown emails goes further.

Risky

A catch-all bucket under another name in some tools, a mixed bag of signals in others: a catch-all domain, a mailbox that looks full, an address with a pattern often linked to low quality. Read the reason code if your verifier gives one.

Next step: treat it as uncertain until a second check settles it. See how to check risky emails.

Role-Based

Addresses like info@, sales@ or support@ that belong to a function rather than a person. They can be perfectly deliverable. The question is whether you should be emailing them.

Next step: a policy call. For cold outreach to individuals, usually leave them out. For partnerships or vendor contact, a role address may be exactly right. Validate or remove role-based addresses walks through the decision.

Disposable

Addresses from temporary inbox services that expire after minutes or days. They show up mostly in signup forms, from people who want the download without the follow-up.

Next step: remove from marketing and outreach lists, and block them at the form. See how to detect and block disposable addresses at signup.

Spam Trap or Abuse Flags

Some verifiers flag addresses that match known trap patterns or belong to people who habitually complain. No tool can see every trap, by design, so a missing flag isn’t a clean bill of health.

Next step: remove anything flagged, and look at where the list came from. Traps in a list usually point to old or scraped data. Our spam trap guide has the details.

Four Myths That Lead to Bad Calls

Myth 1: “Catch-All Means Invalid”

It means unconfirmed, not bad. Plenty of established companies run catch-all servers, so on a B2B list, deleting every catch-all row often means deleting a large share of the accounts you wanted. Delete them and you lose good contacts; send to them blind and the bad ones bounce on your domains. Neither is a plan.

Myth 2: “Unknown Is a Polite Word for Bad”

Unknown is the verifier saying it didn’t get an answer, not that the answer was no. A busy server, a timeout or greylisting can all produce it for a real mailbox. Retrying is cheap. Deleting a real decision-maker is not.

Myth 3: “Valid Means It Will Land in the Inbox”

Verification answers one question: can this address receive mail? Inbox placement depends on your sender reputation, authentication, volume and content. A list of verified addresses sent from a burned domain still lands in spam.

Myth 4: “If the Report Says Valid, It Stays Valid”

People change jobs, companies retire domains, and mailboxes get closed. A result from three months ago tells you about three months ago. Verify close to the send.

A Routing Table for Any Verification Report

Here’s how we’d route each status on a cold outreach or marketing list:

StatusWhat it meansWhere it goes
ValidMailbox confirmed on a standard serverCampaign
InvalidMailbox or domain doesn’t existRemove and suppress
Catch-all / accept-allServer accepts every address, mailbox unconfirmedSecond check before sending
UnknownNo answer from the serverRetry, then second check
RiskyMixed or uncertain signalsSecond check before sending
Role-basedFunction address, may be deliverablePolicy decision, usually exclude from 1:1 outreach
DisposableTemporary inboxRemove, block at signup
Spam trap / abuse flagMatches a trap or complainer patternRemove, review the list source

Keep the status as a column in your CRM or sheet, not just the cleaned output. When bounces rise later, you’ll want to know which bucket the bouncing rows came from.

How to Resolve the Uncertain Middle

The catch-all, unknown and risky rows are where most of the value and most of the risk sit. Here’s the workflow we recommend.

1. Run the Fast Check on Everything

Quick Verification costs 1 credit per email and finishes in minutes, using a server handshake plus a catch-all probe. It sorts the list into valid, invalid and uncertain. If you’ve already run the list through another verifier, you can skip straight to step 2 with its catch-all, unknown and risky rows.

2. Retry the Unknowns

Give timeouts and temporary failures another chance a little later. Some will come back with a clear answer.

3. Send What’s Still Uncertain to Deep Verification

Deep Verification costs 3 credits per email. Scrubby sends a real blank message from its own warmed infrastructure, never your domains, and watches how the receiving server behaves for 72 hours, including bounces that arrive days later. Most addresses resolve in the first 24 hours. How long catch-all verification takes explains the timing.

4. Act on the Final Answer

Valid goes to the campaign. Invalid gets removed and suppressed. Anything that still can’t be resolved stays out of your main campaign. If you want to reach those people anyway, follow the containment rules in is it bad to cold email catch-all addresses: separate campaign, secondary domains, low volume, a close eye on bounces.

Mistakes to Avoid

  • Deleting the whole middle of the report. It feels safe, but on B2B lists it can throw away a big share of the contacts you paid to find.
  • Sending to the whole middle of the report. The bad addresses in it bounce on your domains, and bounces are one of the clearest signals inbox providers use against a sender.
  • Merging statuses into one “OK” column. Keep the original status. It’s your audit trail.
  • Treating role and disposable addresses as deliverability problems. They’re often deliverable. Whether to email them is a policy choice, so make it once and apply it consistently.
  • Verifying once at import and never again. Results age. Re-check before each new campaign on lists that have been sitting.

Where This Fits in Your Stack

Verification belongs between wherever your list comes from and wherever it’s sent. If you build lists in an enrichment tool and send through a sequencer, export, verify, route by status, and import only what goes to the campaign. Our guide to validating lists before Instantly or Smartlead campaigns covers that handoff, and the CRM workflow guide covers keeping statuses current inside your CRM.

FAQ

What’s the difference between invalid and unknown? Invalid means the server said the mailbox doesn’t exist. Unknown means the verifier didn’t get an answer. Remove invalid addresses; retry unknown ones and check them further.

Should I send to catch-all email addresses? Not unchecked. A catch-all result means the mailbox wasn’t confirmed. Run those addresses through a deeper check and send only to the ones that come back valid.

Is a role-based address invalid? No. Role addresses like info@ are often deliverable. Whether to email them depends on what you’re sending and who you want to reach.

Why does my verifier mark so many addresses as risky? On B2B lists, it’s often because many target companies run catch-all servers, which standard checks can’t see past. Check what your tool’s risky label includes, then send that segment for a second check.

Does a valid result mean my email will reach the inbox? No. Valid means the address can receive mail. Whether your email lands in the inbox or spam depends on your sender reputation, authentication, volume and content.

Got a report full of catch-all and unknown rows? New Scrubby accounts start with 200 free credits, and no card is required. See pricing.

email verificationverification resultscatch-all emailsunknown emailslist hygienebounce rate
Amit S.

Amit S.

Marketing Lead

Ready to Validate Your Emails?

Start with 200 free credits. No credit card required.