Article

Why Did My Verified List Come Back Mostly Risky? Causes and Fixes

By Unlimited Verifier Team ·

Diagram showing how a verifier's SMTP reply routes addresses to Valid, Risky, or Invalid, with Risky covering temporary and catch-all responses.

Summary

A list comes back mostly Risky when the verifier cannot get a clear yes or no from the receiving mail server, usually because the domain is catch-all, the server replies temporarily, or the address is role-based or disposable. Risky means unconfirmed, not dead, so diagnose by domain and reason before deleting or re-sending anything.

Why does a verified list come back mostly Risky?

A list comes back mostly Risky when the verifier cannot get a clear yes or no from the receiving mail server, most often because the domain is catch-all (it accepts any address), the server answers temporarily, or the address is role-based or disposable.

Quick answer

Risky sits between Valid (the mailbox was confirmed) and Invalid (the address was rejected). Because the fix depends on which cause dominates your file, diagnose before you delete or re-send anything. If you are new to the process, start with the bulk email list verification workflow. This page focuses on the Risky bucket.

Bottom line: A mostly-Risky result is a diagnosis problem first. Read the pattern before you act on the total.

What does Risky actually mean in a verification result?

Risky is the bucket for addresses where the mail server gave an unclear, incomplete or non-final answer. Most mailbox checks work by opening an SMTP conversation with the recipient's server and asking whether it will accept the address, using the RCPT TO step described in RFC 5321. A well-behaved check stops there and sends no message content. The server's reply determines the outcome:

Server response Typical example Typical outcome Why
2xx acceptance 250 Valid, unless the domain is catch-all The mailbox appears to exist
5xx permanent rejection 550 with enhanced code 5.1.1 Invalid A permanent failure; enhanced codes are defined in RFC 3463
4xx temporary response 450 or 421 Risky The server asks the sender to try again later
No usable reply Timeout or dropped connection Risky There is nothing to decide on
Accept-all (catch-all) 250 for any local part Risky The server accepts every address, so the mailbox cannot be confirmed

Verifiers differ in the exact labels they apply, so treat this as the typical pattern rather than a fixed rule. The practical point is that Risky is not a judgement on the person. It means the server did not give a clean answer, so the first question is why.

Bottom line: Risky is what you get when the server's reply is ambiguous or temporary. Find out which, and the right action becomes clear.

What are the seven causes of a mostly-Risky result?

Each cause leaves a different fingerprint in your results. Check them in roughly this order, because catch-all domains are the most common cause in B2B files.

1. Catch-all domains

A catch-all (accept-all) domain accepts mail for any local part. The server replies "yes" to jane.doe@company.com and to zq8817@company.com alike, so the SMTP check cannot separate real mailboxes from invented ones. Those addresses land in Risky.

This is why B2B lists skew Risky. Trade-show leads, scraped company pages and bought firmographic data often include dozens of contacts at each of a few companies, and many corporate domains are configured this way.

The practical insight is that catch-all behaviour is usually set per domain, not per mailbox. One Risky address at a company predicts most of the others there, so you can make one decision per domain instead of thousands of decisions per row. The catch-all email verification page explains how Unlimited Verifier flags these domains.

Signature: Risky rows concentrate in a limited number of corporate domains.

2. Temporary responses, greylisting and throttling

Some servers use greylisting: they refuse first contact with a 4xx code and expect a retry. Others rate-limit, so a burst of checks against one provider can produce delayed or missing replies.

Both produce Risky rather than Invalid, because the server never said no permanently. This is the cause most often mistaken for a bad list. A genuinely dead address usually returns the same 5xx rejection on every attempt, so an address that resolves on a second run was probably never dead.

Signature: Risky spread across large consumer providers as well as corporate domains, with counts that change between runs.

3. Role-based addresses

Addresses such as info@, sales@, support@, admin@ and hello@ usually exist, but they are shared, often unattended and prone to complaints. Verifiers flag them so you can decide whether they belong in a marketing send. Scraped and purchased lists tend to carry the most of them.

Signature: A cluster of local parts from that short list.

4. Disposable and low-quality domains

Throwaway providers that issue short-lived addresses are flagged. Sign-up forms without a confirmation step let them into a list at scale.

Signature: Many addresses from small, unfamiliar domains, several per domain, with sign-up dates clustered together.

5. Full mailboxes and enterprise filtering

A full mailbox can return an over-quota response, which may be temporary. Some enterprise security gateways answer probes in ways that look ambiguous, even when the mailbox is real.

Signature: Risky results concentrated at one large organisation, while other addresses there resolve normally.

6. The age and origin of the list

Old and merged lists produce mixed results. Companies rebrand or decommission domains, and those addresses move to Invalid. People who changed jobs but still sit at a company that accepts everything move to Risky. For SaaS and ecommerce teams whose lists grow from sign-ups, trials and events, email verification for ecommerce and SaaS covers how source quality shapes results.

Signature: Risky and Invalid rise together, with most Risky rows carrying older source tags.

7. Setup mistakes on your side

Sometimes the list is fine and the upload is the problem:

Signature: The result looks wrong across the board, including addresses you know are good.

Bottom line: Catch-all domains explain most B2B cases, and temporary responses explain most unexpected swings. Rule out the setup mistakes first, because they are the cheapest to fix.

How do you diagnose a mostly-Risky result?

Look for the pattern across Risky rows, not the single worst address. Match what you see to the signatures below.

Signature in your Risky rows Most likely cause What to do
Concentrated in a few corporate domains Catch-all domains Decide per domain; test a small engaged group
Spread across major consumer providers, changing between runs Temporary responses or throttling Re-run after a day or two; treat unstable rows as unresolved
Dominated by info@, sales@, admin@ Role-based addresses Exclude from marketing sends unless the mailbox serves a real purpose
Many addresses from small, unfamiliar domains Disposable or low-quality sources Suppress unless you have documented consent and a real reason to keep them
Risky and Invalid rise together, mostly from old sources Stale list Split by source date and verify each source separately
Known-good addresses come back Risky Upload, column or run-mixing error Re-check the email column and re-run a sample of 50 known addresses

How much Risky is normal? No authoritative public benchmark exists for the Risky share of a verified list, so treat any single vendor figure as that vendor's claim. Composition matters more than the total. A corporate-heavy B2B file can be legitimately high-Risky, while a consumer file dominated by major providers should not be. As a practitioner rule of thumb (not an industry standard), investigate whenever Risky exceeds about 15–20% on a file with few corporate domains.

Bottom line: The domain and reason breakdown tells you more than the headline percentage.

Which Risky addresses should you send to?

Only send to a Risky address once it has an engagement signal, and send those addresses last. Verification shows that a mailbox is probably there. It does not show that the person wants your email.

That distinction is a compliance question as well as a deliverability one. A valid address is not an opted-in address, and email verification compliance and hygiene requires both. US senders should check the FTC's CAN-SPAM compliance guide for the baseline rules. On deliverability, Google's sender guidelines ask bulk senders to keep spam rates below 0.3%, and sending untested Risky addresses in a first campaign is a common way to breach that without warning.

Risky subgroup First campaign? Why
Catch-all, opened or clicked in the last 90 days Small test, last in your ramp Likely reachable, but still unconfirmed
Catch-all, no engagement on record Exclude Undetermined and no evidence of interest
Inconclusive, but Valid on re-run Treat as Valid The re-run resolved the ambiguity
Role-based Exclude from marketing Shared inbox, low engagement, complaint-prone
Disposable Suppress Rarely reaches a person who wants the mail
Still Risky after re-run, no engagement Suppress Undetermined and unproven

Bottom line: Engagement decides who receives Risky addresses, and they go at the end of your ramp.

How do you re-verify a Risky list step by step?

Export your results, split the Risky bucket by reason, re-run only the unstable rows, and decide the structural rows per domain. Follow these nine steps.

  1. Sign up and upload your file. CSV and Excel files up to 10MB are accepted, and the email column is detected automatically. Confirm the detected column is the address you intended. The accepted file formats page lists what works.

  2. Split the file to fit your plan. Free allows 25 lists a month, each up to 150 emails. Pro allows unlimited lists, each up to 25,000 emails. For a 40,000-row file on Pro, two lists are enough. The splitting guide covers larger files, and the 100k verification timing guide helps you plan run times.

  3. Download results immediately. Export as CSV, Excel or JSON. Free results are kept for 24 hours and Pro results for 30 days, so save a copy before the next step. The results file guide explains each column.

  4. Count Risky rows by domain. Filter to Risky, sort by domain and count. A domain with dozens or hundreds of Risky rows is usually catch-all.

  5. Group Risky rows by reason. Use the catch-all, role-based and disposable flags to sort rows into groups. Anything without a flag goes into an "inconclusive" group.

  6. Run a consistency test. Take about 200 Risky addresses across a mix of domains and run them with standard verification. Repeat the run a day later. Rows that flip between runs belong to the temporary-response group. Rows that stay Risky both times are structural. For one-off spot-checks, the free email checker is quick.

  7. Re-run only the inconclusive group. Standard re-runs are unlimited. If you repeat this often, an email verification API lets you script it. API access is included on Pro, which covers 100,000 emails a month, and each request takes up to 10,000 emails. Deep verifications come from your monthly quota (750 on Free, 25,000 on Pro), so spend them on rows that remain ambiguous, not on the whole file.

  8. Recombine and decide. Valid goes to your first send. Invalid is suppressed, following the steps in what to do with invalid emails. Risky is handled according to the subgroup table above.

  9. Merge and re-import. Upload only the Valid segment to your platform, along with a suppression list for Invalid addresses. The re-import guide covers the ESP side, and the CRM merge guide covers contact records. Unlimited Verifier has no native ESP, CRM or Zapier integrations, so this step is a manual export and import, or a script built on the API.

Bottom line: Export first, split Risky by reason, re-run the unstable rows, and decide the structural rows per domain.

What does a worked example of a 62% Risky result look like?

The numbers below are hypothetical. They illustrate the arithmetic and are not benchmarks.

Starting point: A B2B software company has a 40,000-row list built from event leads and a purchased contact file. It is uploaded on Pro and split into 25,000 and 15,000, both within the per-list cap.

First results:

Check: 9,200 + 6,000 + 24,800 = 40,000.

Risky breakdown:

Check: 17,300 + 4,100 + 1,900 + 900 + 600 = 24,800.

Diagnosis: The catch-all rows are the story. Of the 17,300, 14,000 (about 81%) sit at just 35 companies. The remaining 3,300 are spread across domains with only a few contacts each, so they are handled individually. The domain pattern points to catch-all configuration rather than a bad list overall.

Re-run of the inconclusive group: Standard re-verification of the 4,100 rows resolves 2,600: 1,900 become Valid and 700 become Invalid. The other 1,500 stay Risky.

Check: 2,600 + 1,500 = 4,100.

Updated totals:

Check: 11,100 + 6,700 + 22,200 = 40,000.

The re-run moved Risky from 62% to 55.5%. Most of the remaining Risky share is structural, so re-running alone could not fix it.

Deciding the Risky rows: Of the 14,000 contacts at the 35 domains, the company's engagement data shows 2,100 opened an email in the last 90 days. Those become a small, tracked test at the end of the ramp. The other 15,200 catch-all contacts (11,900 at those domains plus 3,300 elsewhere) stay out of the first campaign. The 1,500 inconclusive rows get a deep verification, which uses 1,500 of the 25,000 monthly deep quota.

Group Count Decision
Valid (9,200 + 1,900 from re-run) 11,100 First campaign
Catch-all, engaged in last 90 days 2,100 Small test, last in the ramp
Catch-all, no engagement 15,200 Exclude from first campaign
Role-based 1,900 Exclude from marketing
Disposable 900 Suppress
Inconclusive, still Risky after re-run 1,500 Deep-verify; suppress if still undetermined and unengaged
Other 600 Sample by hand, then decide
Invalid (6,000 + 700) 6,700 Suppress

Check: 11,100 + 2,100 + 15,200 + 1,900 + 900 + 1,500 + 600 + 6,700 = 40,000.

Cost: One Pro month at $29, or $25 per month billed annually. Standard re-runs add no per-email fees.

What the example teaches: A 62% Risky result did not mean the list was 62% dead. One structural issue, catch-all domains at a few companies, dominated the bucket. Re-running resolved 2,600 rows, and the rest needed a per-domain decision.

Bottom line: Do the arithmetic on each subgroup before deciding anything, because the Risky total hides very different problems.

How can you reduce Risky results before you verify?

Most Risky spikes can be prevented upstream, before the file reaches a verifier, by checking data at capture, cleaning it and tagging where each row came from.

Bottom line: Each source you verify at capture is one that cannot produce a Risky spike later.

What are the common mistakes?

Bottom line: Most avoidable mistakes come from acting on the total before reading the breakdown.

Is the verifier to blame, and how do you evaluate one?

Sometimes, but only after the diagnosis. If the pattern persists once you have ruled out list and setup causes, check whether the tool lets you act on each Risky group separately. Different tools draw the lines between catch-all, unknown and invalid differently, so a Risky result in one tool is not automatically Risky in another. When you review the best email verification tools, look for:

For a structured comparison, the how to choose an email verifier guide walks through the criteria, and our tool roundup compares the field.

Bottom line: Judge a verifier by whether its labels let you act on each Risky subgroup. Accuracy claims are a secondary check.

How we compared (and limitations)

This article is based on public documentation: the SMTP specifications in RFC 5321 and RFC 3463, Google's sender guidelines and the FTC's CAN-SPAM guidance. We have not run controlled tests of any verifier's classifications against a reference list.

Unlimited Verifier's stated accuracy for deep verification is 99.5%. That is the company's own figure, not an independent benchmark. Accuracy describes decided addresses. Catch-all addresses are a special case, because the server gives the same answer for real and invented mailboxes, so no SMTP check can resolve them, whatever the accuracy claim.

The worked example is illustrative, and the 15–20% investigation threshold is a practitioner heuristic, not an industry standard. Mail server behaviour changes without notice, so run your own consistency test rather than relying on any single breakdown.

Bottom line: Read every percentage here as a planning tool. Your own domain and reason breakdown is the evidence that matters.

Diagnose a mostly-Risky file in four steps

  1. Sort Risky rows by domain. If a few domains hold most rows, suspect catch-all.
  2. Check the reason or response column. Separate temporary responses and timeouts from catch-all flags.
  3. Re-run only the unstable rows after a short wait. Keep those that settle.
  4. Decide per segment: keep and send cautiously to catch-all contacts with recent engagement, re-check temporary rows, and remove rows that become Invalid.
Pattern in the Risky bucket Likely cause Action
Many rows at few companies Catch-all domains Segment and send cautiously
Count changes between runs Temporary or timeout responses Re-run unstable rows
Role or disposable addresses Non-personal or short-lived inboxes Review and often remove

Frequently asked questions

What does Risky mean in email verification?

Risky means the verifier could not get a clear, final answer from the receiving mail server. It is an unconfirmed label, not a verdict that the address is dead. Common reasons include catch-all domains, temporary 4xx responses, and timeouts.

Are Risky emails safe to send to?

Not automatically. Risky addresses carry more uncertainty than Valid ones, so send to them cautiously and only after you understand the cause. Sending to a catch-all domain without checking engagement history can raise bounce and complaint rates.

Why are so many of my B2B emails catch-all?

Many corporate domains are configured to accept mail for any local part, often to avoid losing messages sent to misspelled or new addresses. The server then replies yes to every address, so the verifier cannot confirm individual mailboxes.

Should I delete all Risky addresses?

Usually no. Break the Risky rows down by domain and reason first. Deleting everything can remove valid contacts at catch-all companies, so decide per segment rather than per file.

Why does the Risky count change when I run the same list again?

Temporary server responses and timeouts are the usual cause. A mail server may be busy or rate-limiting one run and responsive the next. Re-run the unstable rows to see which results settle.

What is the difference between Risky and Invalid?

Invalid means the server permanently rejected the address, typically with a 5xx code such as 550 5.1.1. Risky means the server gave an unclear or temporary answer, so the mailbox status is unknown.

Can a role-based or disposable address cause a Risky result?

Yes. Role addresses such as info@ or sales@ and disposable domains may be flagged Risky by many verifiers because they are often not tied to a single person or are short-lived. Check the reason column to confirm.

How do I reduce Risky results in future list checks?

Clean your source data, remove obvious typos, prioritise direct contacts over generic inboxes, and re-verify unstable rows after a short delay. Export results promptly, since retention windows vary by plan.

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.