Article

What to Do with Risky Emails After Verification: A Triage Guide

By Unlimited Verifier Team ·

Diagram showing a verified list splitting Risky email addresses into catch-all, disposable, role-based and unconfirmed groups, with a 72-hour bounce check for c

Summary

Risky emails are addresses a verifier could not confirm either way, so the reason behind each flag should decide the next step. Split the Risky bucket into catch-all, disposable, role-based and unconfirmed groups, suppress disposables, and hold other segments back. Test catch-alls with a capped send of 500 engaged, consented contacts and expand only while bounces stay under 2%.

Treat Risky emails as their own segment: split them by reason, suppress disposable addresses, hold back role-based and unengaged contacts, and send only a capped test of 500 engaged, consented contacts, expanding only if bounces stay under 2%.

Verification rarely gives a clean yes or no, so the Risky bucket is where most of the judgement happens. This guide covers how to triage it, test it safely and record every decision. For the full cleaning sequence, start with our bulk email list verification workflow.

Quick answer

What are Risky emails, and why aren't they simply Valid or Invalid?

A Risky email is an address the verifier could not confirm either way. The format and domain look plausible, but the check cannot prove the mailbox will accept mail. The cause of that uncertainty should decide what you do next.

Unlimited Verifier checks syntax, domain, MX records and the SMTP mailbox, detects catch-all domains, and flags disposable and role-based addresses. Those flags tell you why an address is Risky. Any Risky row without a flag is best labelled "unconfirmed" in your own file. For how the three result buckets differ, see Valid vs Risky vs Invalid results explained.

The SMTP check creates most of the ambiguity. RFC 3463 defines enhanced status codes, and the first digit matters most. A 4.x.x code is a temporary failure, such as a full mailbox or a server that is throttling you, and the address may be perfectly healthy. A 5.x.x code is a permanent failure and usually means the mailbox no longer exists. Timeouts and greylisting also leave an address unresolved. Many Risky results are really temporary conditions that cleared too slowly for the check to confirm.

Bottom line: Risky means "plausible but unproven." The reason behind it decides whether the address is worth keeping.

Why do Risky emails matter for deliverability and compliance?

Risky emails are not harmless. A catch-all address can bounce after you send, a disposable address was never meant to be read, and a role-based inbox may be shared by several people, one of whom may complain.

Public thresholds show why the stakes are real:

These figures measure different things. Google's thresholds concern complaints and SES's concern bounces, so a Risky send can breach one without touching the other. Where sources differ, plan against the stricter number. We recommend a 2% total bounce ceiling and a 0.10% complaint target, which leave room under both.

Bounce timing matters too. Some catch-all servers accept a message at SMTP and bounce it later, so a count taken within hours can understate the problem. We recommend reading a Risky test at 72 hours. This is a conservative planning window, not a published standard.

Verification also does not settle consent. A valid or Risky address tells you nothing about whether the person agreed to receive your mail. The FTC's CAN-SPAM compliance guide sets the baseline for commercial email in the US. Keep consent evidence for each contact as part of your email verification compliance and hygiene process, and treat it separately from the verification result.

Bottom line: Risky addresses carry three separate costs: bounces, complaints and consent gaps. Each needs its own control.

Which Risky emails should you suppress, and which can you keep?

Weigh the value of each contact against the cost of a bounce or complaint. A disposable address has almost no value and a real cost, so suppress it. A catch-all contact who engaged recently and gave consent has real value, so it can earn a place in a tightly capped test.

Risky reason What the check couldn't establish Typical source Default action
Catch-all domain Whether this specific mailbox exists, because the server accepts everything Corporate domains, some ISPs, B2B imports Hold. Test only if engaged and consented
Disposable Whether a real, reachable person owns it Throwaway sign-up services, lead magnets Suppress permanently
Role-based (info@, sales@, support@) Whether a specific person reads it Contact pages, scraped sites, web forms Exclude from marketing unless you hold consent for that inbox
Unconfirmed (4xx response, timeout, greylisting) Whether the mailbox is alive right now Slow or throttling servers, newly created domains Re-check after a wait, then decide

Catch-all addresses

Catch-all domains are the largest and most misunderstood group. Because the server accepts any address, a "yes" from the verifier tells you the domain accepts mail, not that this mailbox exists. Mail to a catch-all can also bounce later. Treat catch-alls as a conditional keep: they need documented consent and recent engagement, and they should go through a capped test before anything larger.

Disposable addresses

Disposable addresses are the easiest call. They come from temporary inboxes people use to get past a form, so the person behind them rarely expects your mail. Suppress them and block them at sign-up with real-time email validation so they don't return. For the difference between suppressing and deleting, see should you delete or suppress invalid emails.

Role-based addresses

A role address such as info@ or sales@ is usually shared, so it doesn't show that one identifiable person agreed to your mail. Keep one only when you have a documented opt-in from someone who reads that inbox.

Unconfirmed addresses

Unconfirmed addresses are the most often discarded by mistake. A temporary response usually means "try again later," not "this mailbox is dead." Hold them for a re-check rather than deleting them or mailing them straight away. The guide on what to do with unknown emails after verification goes deeper on the same logic.

Bottom line: Suppress disposable addresses, exclude role-based ones without consent, re-check unconfirmed ones, and reserve catch-alls for a conditional test.

How do you decide whether to keep a Risky contact?

Run each Risky contact through five questions in order. The first two settle most addresses.

  1. Is it disposable? If yes, suppress it and stop.
  2. Is it role-based with no consent for that inbox? If yes, exclude it from marketing and record the reason.
  3. Is it unconfirmed? If yes, hold it for a re-check at about 30 days.
  4. Is it catch-all? Ask whether the contact gave documented consent and engaged (opened, clicked or purchased) in the last 90 days. If both are true, it goes into the capped test. If not, hold it.
  5. Does it have a transactional need? An order receipt or account notice may still justify a send. Bounces from those sends still count toward your overall sending reputation.

Record a reason for every decision. If a reviewer or an ESP asks why you dropped 6,000 contacts, a recorded reason for each one answers the question in minutes.

Bottom line: Work through the five questions in order and log the reason for every decision.

Should you re-verify Risky emails, and when?

Yes, but timing matters more than frequency. Re-running the same file within the hour usually returns the same result, because the mail server hasn't changed. A wait of about 30 days lets temporary conditions clear, and mailbox status changes as people leave companies.

Unlimited Verifier offers two levels of checking, and their costs differ:

Option Availability Cost Best used for
Standard verification Unlimited on every plan, including Free No per-email fee. Free is limited to 150 emails per list Re-running a held segment on a delayed schedule
Deep verification Free: 750 a month. Pro: 25,000 a month Included in the plan allowance. On Pro, about $1.16 per 1,000 at $29 a month, or about $1.00 per 1,000 at $25 a month billed annually, if you use the full allowance The unconfirmed contacts that matter most

The company states 99.5% accuracy for deep verification. That is Unlimited Verifier's own figure, not an independent benchmark. For wider context on how pricing models compare, see email verification pricing.

Bottom line: Re-check unconfirmed addresses after about 30 days, and spend deep checks on the contacts you most need to keep.

How do you send to Risky emails without hurting your reputation?

Send to Risky contacts only in a capped, staged test, and let the bounce rate decide whether you continue. The thresholds below are our recommendation, not a published standard.

Don't use a Risky test to chase volume. Its purpose is to learn whether the segment is healthy before you send to all of it.

Bottom line: Cap the test at 500, read it at 72 hours, and stop above 10 bounces.

How do you split and export Risky emails in Unlimited Verifier?

This tutorial takes you from a verified file to three segments you can re-import. It works on the Free and Pro plans, with the limits noted in the steps.

  1. Keep your context columns in the source file. Include columns for consent source and last engagement date. After you export, check that they're still present. The guide on keeping custom fields when verifying an email list explains how to preserve them.
  2. Upload the file. Go to upload and verify a list. CSV and Excel files up to 10MB are accepted, and the email column is detected automatically. Files over 25,000 rows need splitting first. The guide on splitting a large CSV for verification shows how.
  3. Check the totals. Compare the Valid, Risky and Invalid counts with your input row count. A large gap usually points to formatting problems, which the guide on cleaning a messy CSV before upload can fix.
  4. Export the Risky rows the same day. Export as CSV, Excel or JSON. Results are kept for 24 hours on Free and 30 days on Pro.
  5. Assign a reason to each row. Add a risk_reason column. Use the catch-all, disposable and role-based flags, and label the remainder "unconfirmed."
  6. Split into three files.
    • Suppress: disposable addresses, plus role-based addresses without consent.
    • Hold: unconfirmed addresses and unengaged catch-alls, each with a re-check date.
    • Test: catch-all contacts with consent and recent engagement, capped at 500 for the first send.
  7. Re-import the segments. Unlimited Verifier has no native ESP, CRM or Zapier integrations, so import each file into your platform manually. If you want to automate, call the email verification API from your own scripts. For patterns, see email verification API and automation. The guide on segmenting a list by verification status covers naming and structure.
  8. Spot-check high-value addresses. For one important contact, the free email checker gives a quick second opinion without a full upload.

Bottom line: Export the same day, assign a reason to every row, and re-import three named segments.

Worked example: what happens to a 48,000-contact Risky segment?

The figures below are illustrative. The arithmetic and plan limits are real. Imagine a B2B SaaS team with a 48,000-contact list, verified as follows:

The Risky 7,400 breaks down as 4,300 catch-all, 1,100 role-based, 600 disposable and 1,400 unconfirmed.

Check the plan limits first. On Free, each list holds up to 150 emails and you get 25 lists a month, which is 3,750 emails. Verifying 48,000 would take 13 months (48,000 ÷ 3,750 = 12.8). Free also includes 750 deep verifications a month, so the 1,400 unconfirmed addresses would take two months (1,400 ÷ 750 = 1.9). On Pro, the list splits into two uploads of 25,000 and 23,000, both within the per-list cap. The 1,400 deep checks fit comfortably inside the 25,000 monthly allowance.

Triage the Risky segment:

  1. Suppress 600 disposable addresses. Risky falls to 6,800.
  2. Deep-verify the 1,400 unconfirmed addresses. Suppose 900 come back Valid, 350 Invalid and 150 stay Risky. Valid rises to 37,000, Invalid to 4,850, and Risky becomes 5,550 (6,800 − 1,400 + 150).
  3. Exclude 1,100 role-based addresses from marketing, as no consent exists for those inboxes. Risky falls to 4,450: 4,300 catch-alls plus 150 unconfirmed.
  4. Identify engaged catch-alls. Suppose 620 of the 4,300 engaged in the last 90 days and have consent evidence. Only those 620 qualify for the test. The other 3,680 are held for a re-engagement check and suppressed if they stay inactive.
  5. Run the test. Send to 500 of the 620. At 72 hours, 4 bounces (0.8%) is under the 1% line, so the team sends to the remaining 120 and holds the rest.

Outcome: The team now has 37,000 Valid contacts for normal sending, 4,850 Invalid contacts to suppress, 600 disposable addresses suppressed, and a documented Risky audit with a count for every step. The Pro plan costs $29 for the month, and every removal has a recorded reason.

Bottom line: Plan within the per-list and monthly limits, triage by reason, and let a capped test decide what the catch-alls are worth.

What are the most common mistakes with Risky emails?

Bottom line: Most Risky-segment problems come from sending too much, too soon, or without a record of why.

How we compared (and limitations)

This guide draws on public documentation: Google's sender guidelines and Postmaster Tools, Amazon SES's published thresholds, RFC 3463 for SMTP enhanced status codes, and the FTC's CAN-SPAM guidance. We have not run controlled tests of any ESP's review process, and platform thresholds change without notice.

The 2% bounce ceiling, the 0.10% complaint target, the 500-contact test size, the 72-hour read window and the 30-day re-check interval are our recommendations, not published standards. Where Google's and Amazon's figures differ, we planned against the stricter number.

Unlimited Verifier's features and limits come from its published plan details. The 99.5% deep-verification accuracy is the company's own stated figure. The worked-example percentages and counts are illustrative. If you're comparing verifiers on how they label uncertain results, see our guide on how to choose an email verifier and the roundup of best email verification tools.

To put this into practice, sign up and run your Risky segment through the process above. If your list has many catch-all domains, the catch-all email verification page explains how those results are handled.

Risky triage and capped test steps

  1. Split Risky rows by flag: catch-all, disposable, role-based, unconfirmed.
  2. Suppress every disposable address.
  3. Hold role-based addresses unless you hold consent for that inbox.
  4. Re-verify unconfirmed addresses after about 30 days.
  5. Build a test of 500 engaged, consented catch-all contacts.
  6. Send once and read bounces at 72 hours.
    • At or below 1%: expand gradually.
    • Between 1% and 2%: hold and review.
    • Above 2%: stop and remove the segment.

Frequently asked questions

What does Risky mean in email verification?

Risky means the verifier could not confirm that a mailbox will accept mail. The address format and domain look plausible, but the SMTP check was inconclusive. The flags attached to the result, such as catch-all or disposable, explain why it is uncertain and guide what to do next.

Should I send to Risky emails?

Not in a full campaign. Send only to Risky addresses that have a clear reason to be kept, such as a catch-all domain with verified engagement, and start with a small capped test. Suppress disposable addresses and hold back unconfirmed contacts until they are re-checked.

What is a catch-all email address?

A catch-all address sits on a domain configured to accept mail for any local part, so the verifier cannot confirm whether a specific mailbox exists. Catch-alls can still bounce later, so treat them as a separate segment and test them with a limited send before scaling up.

Should I remove disposable email addresses?

Yes, in most cases. Disposable addresses are temporary inboxes built to be abandoned, so they rarely engage and are not a good fit for marketing. Suppress them unless the contact has deliberately provided one and you have a clear, lawful reason to email it.

Are role-based emails like info@ or sales@ safe to mail?

They can be deliverable, but they are often shared by several people and may generate complaints from staff who never opted in. Keep them out of marketing sends unless you hold consent for that specific inbox, and treat them as a distinct segment.

How long should I wait before re-checking unconfirmed addresses?

A re-check after about 30 days is a sensible default. Many unconfirmed results come from temporary conditions such as greylisting, timeouts or full mailboxes, which often clear within days or weeks. Re-verify before mailing rather than assuming the address is still valid.

What bounce rate is too high for a catch-all test?

Read bounces about 72 hours after the send. Continue expanding if bounces are at or below 1%, hold between 1% and 2%, and stop above 2%. Keep the test list engaged and consented so that bounces reflect the address quality rather than poor targeting.

Why does a 4.x.x SMTP code matter for Risky results?

Under RFC 3463, a 4.x.x enhanced status code signals a temporary failure, such as a full mailbox or throttling. The address may be healthy, so it should not be treated the same as a permanent 5.x.x failure, which usually means the mailbox no longer exists.

How long should I keep verification results?

Export results the same day you verify them. Unlimited Verifier keeps results for 24 hours on the Free plan and 30 days on Pro, so save a copy of your decisions and segment labels to your own system to maintain an audit trail.

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.