Article

Valid vs Risky vs Invalid Email Results Explained

By Unlimited Verifier Team ·

Diagram showing an email verifier sorting addresses into Valid, Risky and Invalid email result buckets with a sending action for each.

Summary

Valid, Risky and Invalid are the three result categories a bulk email verifier assigns to each address. Valid addresses passed every check, Invalid addresses will almost certainly bounce, and Risky addresses might deliver but cannot be confirmed. Each bucket should trigger a different sending decision.

Valid, Risky and Invalid are the three result categories a bulk email verifier assigns to each address. Valid addresses passed every check, Invalid addresses will almost certainly bounce, and Risky addresses might deliver but cannot be confirmed.

Each bucket should trigger a different sending decision, so reading the buckets correctly matters as much as the verification run itself. This guide explains what each result means, what causes it, how to act on it, and how to judge the numbers without overtrusting them. It sits within our bulk email list verification workflow.

Quick answer

What do Valid, Risky and Invalid results actually mean?

Each bucket is a prediction about delivery, not a judgement about the person behind the address. Valid means deliverable as far as the checks can tell, Risky means unknown, and Invalid means mail is expected to bounce.

Bucket What the verifier found Typical causes Bounce risk if you send Default action
Valid Passed syntax, domain, MX and SMTP mailbox checks Active mailbox at a normal provider Low, though engagement still matters Send, most engaged contacts first
Risky Delivery could not be confirmed either way Catch-all domain, disposable or role address, temporary server response Uncertain: could deliver or could bounce Hold back, test in small batches, decide by sub-reason
Invalid Failed a check that indicates non-delivery Syntax error, domain with no mail server, mailbox permanently rejected High, close to certain Suppress permanently

Bottom line: Valid means "deliverable as far as we can tell," Risky means "unknown," and Invalid means "don't send."

Why do verifiers use three buckets instead of yes or no?

A verifier can't always get a clear answer. It asks the receiving mail server whether a mailbox exists rather than reading the inbox, and some servers accept every recipient or give an inconclusive reply. A yes-or-no result forces those cases into a false choice. Label them "safe" and you mail catch-all addresses blind. Label them "bad" and you delete real customers. The middle bucket keeps the uncertainty visible.

The SMTP reply codes behind this are defined in RFC 5321. Negative replies split into transient 4xx codes, which ask the sender to try again later, and permanent 5xx codes, which mean the message should not be retried. A 4xx reply does not mean the address is dead. Treating every rejection as final is one of the most common list-cleaning errors.

Here is the practitioner insight: the size of your Risky bucket measures how much you don't know. Two lists with the same Valid percentage can carry very different risk. The one with more Risky addresses has more of its deliverability resting on untested assumptions.

Bottom line: The middle bucket exists because server answers are sometimes ambiguous, and a yes-or-no label would hide that.

What makes an address Valid?

A Valid result means the address cleared all four checks Unlimited Verifier runs: syntax, domain, MX records and the SMTP mailbox. Each check rules out a different failure:

Valid has limits you should write into your process. It does not show that a contact opted in. The checks above also don't detect spam traps, which are addresses run by providers to catch senders who mail stale lists. A mailbox can close after it was verified, too. EU and UK rules generally require consent before marketing email goes to individuals, and a working mailbox does not prove that consent. US rules, set out in the FTC's CAN-SPAM compliance guide, focus instead on honest headers, accurate subject lines and a working unsubscribe. Your lawful basis depends on where your recipients are. For how verification fits into this picture, see email verification compliance and hygiene.

Bottom line: Valid means deliverable, not consented. Keep those two questions separate in your process.

What counts as Invalid, and is it always permanent?

Invalid means the verifier found a failure that predicts non-delivery: broken syntax, a domain that does not exist or accepts no mail, or a mailbox the server rejects with a permanent error. Suppress these as a matter of routine.

Permanent rejections often carry enhanced status codes. RFC 3463 defines 5.1.1 as "bad destination mailbox," the classic signal of a nonexistent address. Typos are a frequent source. A misspelled domain can point to a name with no mail server, which fails the domain or MX check. That is one reason imported lists, which often contain keyed-in data, can show a higher Invalid share than lists collected through a signup form.

Invalid is the highest-confidence bucket, but two cases need judgement:

If a large share of your list comes back Invalid, the cause is usually the data source rather than the cleaning. What to do if 30 percent of your list is invalid walks through that diagnosis. To stop new Invalid addresses at the point of entry, add real-time email validation to your signup forms.

Bottom line: Invalid is the bucket you can act on with the most confidence, but suppress it in every system, not just the one you cleaned.

What should I do with Risky addresses?

Treat each Risky address according to its sub-reason, because the sub-reason tells you why the verifier couldn't decide. The label alone isn't enough.

Risky reason Why it's uncertain Practical handling
Catch-all domain The server accepts any recipient, so a "yes" proves little Test a small sample across the domain, then decide for the whole domain
Disposable address Throwaway providers are short-lived and often reflect fake signups Exclude from marketing; review before any transactional use
Role address (info@, sales@) Shared inbox, often unmonitored, with unclear consent Keep out of person-level segments; confirm the basis for B2B outreach
Temporary server response (4xx) The server asked for a retry; the mailbox may be full or the server busy Re-verify after a delay; treat as unknown emails until resolved
Inconclusive probe The server gave no clear answer Re-verify later and treat as Risky in the meantime

Unlimited Verifier flags catch-all, disposable and role-based addresses. In your own segmentation, treat any flagged address as Risky until you have made a deliberate decision about it. The catch-all email verification page explains how catch-all results are handled.

The most useful practitioner insight is that catch-all status belongs to the domain, not the mailbox. Every address at a catch-all company shares the same uncertainty, so 300 contacts at one employer are a single decision, not 300. A common pattern is to delete a whole company's contacts, or to send 300 emails into a domain that bounces them. A better approach is to send a sample of about 20 addresses across different people at that domain, then let the sample decide for the whole domain.

Bottom line: Risky is not "half-valid." Decide by sub-reason, and make catch-all decisions per domain.

How should I act on each bucket?

Send Valid addresses, test Risky addresses in controlled batches, and suppress Invalid addresses. Then adjust the rule for each use case.

  1. Suppress Invalid everywhere first. Apply it in the source file, your ESP and your CRM, so the addresses cannot come back on the next import.
  2. Build the Valid segment and rank it. Sort by last open, click or purchase. The guide on segmenting a list by verification status shows how to set this up.
  3. Send to Valid, most engaged first. Check the bounce count after each batch, not only at the end.
  4. Split Risky by sub-reason. Test catch-all domains with samples, exclude disposable addresses from marketing, and re-verify temporary responses later.
  5. Log the counts per bucket and the bounce result per send. The next run is only as useful as the record of this one.
Use case Valid Risky Invalid
Transactional (receipts, password resets) Send Send to known customers and monitor bounces Don't send; contact the person another way
Opted-in newsletter Send, most engaged first Small test, then decide by sub-reason Suppress
Cold B2B outreach Send only where your legal basis and local rules allow Exclude, or test narrowly Suppress

Transactional mail usually needs the most care of the three. A missed receipt or password reset costs more than a slow newsletter, so the Risky tests should be even more conservative there.

Bottom line: The buckets tell you what to send, but the use case decides how far into Risky you go.

How accurate are the buckets, and how do I test them?

Accuracy claims are only useful if you can test them against your own sends. Unlimited Verifier states 99.5% accuracy for its deep verification. That is the company's own figure, not an independent benchmark. Vendors typically measure accuracy against test sets they choose, so when you compare email verification tools, run the same sample through each one and compare the bounce results rather than the brochure claims.

You can calibrate any verifier with a simple test:

On thresholds, sources disagree. Amazon SES's documentation describes review at a 5% bounce rate and pausing at 10%. Google's sender guidelines set 0.3% as the spam-complaint level to stay under. Other platforms use their own triggers and publish no single standard. We recommend planning around a 2% total bounce ceiling, with under 0.5% on your first Valid-only send. That leaves room before any platform's automated response.

Bottom line: Trust the buckets only after your own Valid-only sends confirm them, and plan to a stricter ceiling than any platform's trigger.

How do I read a verification results file?

Follow these steps to turn a results file into a sending decision.

  1. Clean the file first. Remove blank rows, stray characters and duplicate addresses. The guide on cleaning a messy CSV before upload covers the common problems.
  2. Check the format. CSV and Excel are both accepted. If you're unsure, see which file formats email verifiers accept.
  3. Upload the file. Go to upload and verify a list. Files can be up to 10MB, and the email column is detected automatically. On Pro, each list can hold up to 25,000 emails. If your file is larger, split it first. Deduplicate before splitting, or the same address can land in two lists and skew your counts. The upload guide walks through the screens.
  4. Wait for the run to finish, then open the results.
  5. Count each bucket. Check that Valid, Risky and Invalid add up to your input total. If they don't, stop and find out why before going further.
  6. Review the flags. Look at catch-all, disposable and role results to build your sub-segments.
  7. Export the results as CSV, Excel or JSON. The guide on reading a results file explains each column.
  8. Export the same day. Free results are kept for 24 hours and Pro results for 30 days.
  9. Re-import the buckets. Load Valid as a new segment, and add Invalid to your suppression list. Unlimited Verifier has no native ESP, CRM or Zapier integrations, so this step is a file re-import or an API call. To keep your extra columns intact, follow the guide on keeping custom fields when verifying a list.
  10. Spot-check odd cases. For a single address that needs a closer look, the free email checker handles one lookup at a time.

If you want to automate these decisions, the email verification API and automation approach lets your own scripts send single checks or batches. The email verification API accepts single-email checks and batches of up to 10,000 emails per request.

Bottom line: Count the buckets, export the same day, and re-import only what you have decided to send to.

Which plan fits my list size?

Plan limits shape how you split and time the work, and they matter as much as the bucket logic. You can compare email verification pricing with the limits below.

Feature Free ($0) Pro ($29/month, or $25/month billed annually)
Standard verification Unlimited, no per-email fees Unlimited, no per-email fees
Lists per month 25 Unlimited
Emails per list Up to 150 Up to 25,000
Deep verifications per month 750 25,000
API access No Yes, 100,000 emails per month
Results kept 24 hours 30 days

Two practical consequences follow. Free suits a small list or a single segment, but its 150-email cap per list rules it out for large files. The 24-hour retention on Free means you must export the same day, or the buckets are gone. You can create a free account and test your process on a sample before moving to Pro.

Bottom line: Match the plan to your file size and to how long you need to act on the results.

What does a real 40,000-row run look like?

The scenario (illustrative): A B2B software company exports 40,000 rows from its CRM, including signup dates and last-activity fields. The team runs them on Pro at $29 for the month. Each Pro list holds up to 25,000 emails, so the team splits the file into two lists of 25,000 and 15,000. It deduplicates the full file first, so no address appears in both.

Hypothetical results:

Check: 27,200 + 8,400 + 4,400 = 40,000.

Risky breakdown (hypothetical): 5,500 catch-all, 1,500 role-based, 400 disposable, 1,000 temporary or inconclusive. Check: 5,500 + 1,500 + 400 + 1,000 = 8,400.

Deep verification: Running deep verification on the 8,400 Risky addresses uses 8,400 of the 25,000 monthly deep verifications, which leaves 16,600 for re-checks.

Sending plan:

Calibration result (hypothetical): The first batch bounces 36 of 9,000 addresses, which is 0.4% and under the 0.5% target. That is evidence the Valid bucket works. Had the rate come in at 2% or more, the team would investigate by domain before sending again.

Cost: One Pro month at $29 covers 40,000 rows, about $0.73 per 1,000 rows. The Free plan can't handle this file in a month. At 150 emails per list and 25 lists a month, its maximum is 3,750 rows (25 × 150). Covering 40,000 rows would need 267 lists (40,000 ÷ 150, rounded up), far beyond the 25-list limit. Teams running this volume regularly can also use the API, which includes 100,000 emails a month on Pro.

Bottom line: The arithmetic gives you the split, the quota, the cost and the calibration plan before you send anything.

What mistakes should I avoid with Valid, Risky and Invalid results?

Bottom line: Most errors come from mixing buckets together or from letting a result go stale before anyone acts on it.

How we compared (and limitations)

This article is based on public documentation: the SMTP reply-code and status-code specifications in RFC 5321 and RFC 3463, Google's sender guidelines, Amazon SES's published thresholds, the FTC's CAN-SPAM guidance, and Unlimited Verifier's own plan facts. We have not run controlled tests against any vendor or mailbox provider, and we have not benchmarked the accuracy of any verifier.

The 99.5% figure is Unlimited Verifier's stated accuracy for deep verification, not an independent measurement. The worked-example numbers and bucket breakdowns are illustrative and hypothetical. Thresholds and platform behaviour change over time, so check current documentation before setting a policy. When you review email list maintenance best practices or decide how to choose an email verifier, run your own sample and measure the bounces.

Bottom line: The buckets are a decision tool. Validate them against your own sends before you rely on them.

Action by verification bucket

Bucket Action Notes
Valid Send, engaged contacts first Still confirm consent and engagement
Risky Hold back, test in small batches Decide by sub-reason such as catch-all or role address
Invalid Suppress permanently Keep suppressed in every system

Frequently asked questions

What does a Valid email result mean?

A Valid result means the address passed syntax, domain, MX and SMTP mailbox checks, so it is deliverable as far as the checks can tell. It is safe for regular sending. However, passing verification does not prove the person consented to receive your email, so engagement and permission still matter.

What does a Risky email result mean?

A Risky result means the verifier could not confirm delivery either way. Common causes include catch-all domains, disposable or role addresses, and temporary server responses. Hold Risky addresses back, test them in small batches, and decide based on the specific sub-reason.

Should I delete Invalid email addresses?

Yes, suppress Invalid addresses permanently and keep them suppressed in every system that sends mail. They failed a check that predicts non-delivery, so mailing them is expected to bounce. Repeated bounces can hurt your sender reputation with mailbox providers.

Why are there three buckets instead of valid or invalid?

Verifiers cannot always get a clear answer from receiving servers. Some accept every recipient or return inconclusive replies. A two-bucket system would force those cases into either safe or bad, which leads to mailing bad addresses or deleting real customers. The Risky bucket keeps that uncertainty visible.

Is a 4xx SMTP response the same as an invalid address?

No. Under RFC 5321, 4xx codes are transient and ask the sender to retry later, while 5xx codes are permanent. A 4xx reply does not mean the address is dead. Treating every rejection as final is a common list-cleaning mistake.

What is a catch-all domain?

A catch-all domain is a mail server configured to accept mail for any address at that domain, whether or not the mailbox exists. Verifiers cannot confirm individual mailboxes on these domains, so those addresses usually land in the Risky bucket.

How do I tell if my Risky bucket is too large?

Compare the Risky share across list sources and over time. Two lists with the same Valid percentage can carry very different risk if one has far more Risky addresses. A large Risky bucket means much of your deliverability depends on untested addresses, so test them in small batches before full sends.

How long should I keep verification results?

Unlimited Verifier keeps results for 24 hours on the Free plan and 30 days on the Pro plan, according to its published plan terms. Export your Valid, Risky and Invalid buckets on the day you run them so you are not relying on stored results expiring.

Cut Bounces and Protect Your Sender Reputation With Unlimited Email Verification

Every invalid address you send to hurts your sender reputation and your inbox placement. Verifying your list before each send means fewer bounces, healthier deliverability, and a predictable cost. With Unlimited Verifier, standard verification is unlimited on every plan, with no per-email fees.

Unlimited Verifier checks syntax, domain, MX records and the SMTP mailbox. It also detects catch-all domains and flags disposable and role-based addresses. Export a CSV from your email platform or CRM, upload and verify the list, then re-import the clean results. You can also automate checks with the email verification API.

Free Pro
Price $0 $29/month ($25/month billed annually)
Lists 25 a month, up to 150 emails each Unlimited, up to 25,000 emails each
Deep verifications 750 a month 25,000 a month
API access No Yes (100,000 emails a month)
Result retention 24 hours 30 days

Why teams choose Unlimited Verifier

Unlimited Verifier states 99.5% accuracy for deep verification.

Create a free account and verify your next list before you hit send.

Want to test a single address first? Try the free email checker.