Article
How to Segment a List by Verification Status: Valid, Risky and Invalid Rules
By Unlimited Verifier Team ·

Summary
To segment a list by verification status, group every address as Valid, Risky or Invalid and give each group its own sending rule: mail Valid addresses first, test Risky ones in small batches, and suppress Invalid ones. Layer engagement and source data on top so each segment has a decision you can defend.To segment a list by verification status, split every address into three groups, Valid, Risky and Invalid, and give each group its own sending rule: mail Valid addresses first, test Risky addresses in small batches, and suppress Invalid addresses before anything else goes out. This guide shows how to build those segments, set the rules and keep them accurate.
Quick answer
- Valid addresses passed the syntax, domain, MX and mailbox checks. Send to them first, starting with the most engaged.
- Risky addresses can't be confirmed as deliverable. Catch-all, disposable and role-based addresses usually land here. Test them in small batches, last.
- Invalid addresses failed in a way that won't fix itself. Suppress them and keep a record of the suppression.
- Layer engagement recency and source onto status, so every segment has a sending decision you can defend.
- Save your results file before it expires, then re-verify on a schedule so the segments stay accurate.
What does it mean to segment a list by verification status?
Segmenting by verification status means grouping contacts by the result a verifier returns for each address, so each group gets its own sending decision. Unlimited Verifier sorts every address into Valid, Risky or Invalid, and you filter the results file on that status column. Segmentation is one step in the wider bulk email list verification workflow, which also covers intake, cleaning and re-checks.
| Status | What the check found | Common causes | Sending rule |
|---|---|---|---|
| Valid | Syntax, domain, MX and SMTP mailbox checks passed | Active personal and corporate mailboxes | Send, most engaged first |
| Risky | The address can't be confirmed as safe or deliverable | Catch-all domains, disposable domains, role addresses (info@, sales@), temporary server errors | Test in small batches, last |
| Invalid | A check failed permanently | Bad syntax, domains with no MX records, mailboxes that don't exist (the SMTP 5.1.1 "bad destination mailbox" code in RFC 3463) | Suppress permanently |
Risky is a confidence label, not a quality label. A catch-all domain may hold a perfectly good mailbox, but its server accepts every address, so the verifier can't tell which ones are real. Treating Risky as a synonym for Invalid throws away reachable contacts. Treating it as Valid puts unknown risk into your main sends.
Bottom line: The three statuses describe how confident you can be that an address works, and each one should map to a different sending rule.
Why does each verification status need its own sending rule?
Each status carries a different bounce and complaint risk, and blending them into one batch hides the bad addresses. An Invalid address will bounce, and every bounce counts against your sending reputation. A Valid address is likely to be delivered, but it may never open. A Risky address might bounce, or it might be a trap you only learn about by sending to it.
The arithmetic makes this concrete. Imagine a 20,000-contact send that includes 1,200 Invalid addresses. That's a 6% bounce rate for the whole send (1,200 ÷ 20,000), even though 94% of the list is clean. Amazon SES's documentation sets 5% as the bounce rate at which an account is placed under review, and many ESPs apply their own, often stricter, limits. Suppressing the Invalid segment before sending brings that same send to 0%, and the 18,800 Valid and Risky contacts are the only ones left to judge.
This matters most for email verification for ecommerce and SaaS teams, where sign-up forms and trial accounts add new addresses every day. Without status segments, one bad import can push a routine send over a provider's limit.
Segmentation also supports compliance. Verification tells you an address is real, but not that the person agreed to hear from you. The FTC's CAN-SPAM compliance guide sets out the consent and opt-out duties that still apply to every valid address. For the wider practice, see email verification compliance and hygiene.
Bottom line: Splitting the list protects your bounce rate and lets you send to contacts who can receive your mail and are likely to want it.
How do you plan verification segments from a master list?
Follow these seven steps in order. Each one creates a record you'll need later.
- Verify the whole master list, not just the new contacts. Older addresses decay as people change jobs and mailboxes close. A segment built on partial verification will look cleaner than it really is.
- Add three columns to your master file:
status,verified_onandsegment. The verification date tells you when a result is going stale. - Split by status first. Create three files or saved views: Valid, Risky and Invalid.
- Layer engagement onto Valid. Add a recency field such as last click, last purchase or last reply. Opens are less reliable than clicks or purchases, because Apple Mail Privacy Protection, introduced in 2021, loads tracking pixels whether or not the person opens the message.
- Break Risky into subtypes. Use the catch-all, disposable and role-based flags to sort Risky addresses into separate groups. Each subtype needs a different decision, covered below.
- Write down each segment's rules. Record its size, its send order and its bounce ceiling before you send anything. A reviewer or stakeholder should be able to read the plan and predict what happens next.
- Re-verify on a schedule and rebuild the segments. A segment is a snapshot. Re-run verification on your maintenance cadence and regenerate the groups.
Invalid addresses need their own follow-through. Suppress them, then review why they accumulated. If a large share fails, the what to do with invalid emails after list cleaning guide covers the next steps, and what to do if 30 percent of your list is invalid covers the case where the problem is systemic.
Bottom line: Status gives you the first split. Engagement and risk subtype turn that split into a sending plan.
Which segmentation method should you use?
Most teams need more than status alone, but each extra layer costs time and depends on cleaner data. The table compares the common options.
| Method | What it answers | Strength | Weakness | Best for |
|---|---|---|---|---|
| Status only | Can this address receive mail? | Fast, objective, straight from verification | Says nothing about interest | First-pass cleaning of an inherited list |
| Status + engagement recency | Can it receive mail, and does this person want it? | Sends first to the people most likely to respond | Depends on clean click and purchase data | Regular campaigns to an established list |
| Status + risk subtype | Why is this address Risky, and what should I do with it? | Gives each Risky address a specific action | Needs the flags in your results file to be read correctly | B2B lists with many corporate catch-all domains |
| Status + source tag | Which acquisition channel produced this address? | Exposes weak sources such as trade-show or purchased lists | Requires source tagging at import | Databases built from several sources |
For lists over about 10,000 contacts, a practical default is status plus engagement plus source. Status tells you what's deliverable, engagement tells you what's welcome, and source tells you where the problems started. If you're still comparing options, the best email verification tools roundup explains how different products label their results, and how to choose an email verifier covers what to test before you commit.
Bottom line: Use status for deliverability, add engagement for intent, and add source when the list came from more than one place.
How do you segment a list in Unlimited Verifier, step by step?
This tutorial uses Unlimited Verifier. The same logic applies to any verifier that returns a status column. The step-by-step guide to cleaning a bulk email list covers the wider cleaning process.
- Export your contacts as a CSV. Include the email field, a unique contact ID, and engagement fields such as last click or last purchase date. The contact ID is what you'll use to merge results back later.
- Trim and lowercase the email column, then remove duplicates. Mailbox providers treat
Jane@Example.comandjane@example.comas the same mailbox in practice, but a spreadsheet's duplicate check will treat them as different rows. - Sign up and choose a plan. Compare email verification pricing before you commit. The Free plan covers 25 lists a month of up to 150 emails each, which is 3,750 emails at most, and it includes 750 deep verifications a month with no API access. The Pro plan is $29 a month, or $25 a month billed annually. It allows unlimited lists of up to 25,000 emails each, 25,000 deep verifications a month, and API access for 100,000 emails a month. Standard verification is unlimited on every plan, with no per-email fees.
- Split files that exceed your list cap. On Pro, a 48,000-contact list needs two uploads. The split a large CSV guide explains how to keep the contact ID on every row. For a sense of run times at scale, see how long it takes to verify 100k emails.
- Upload and verify a list. CSV and Excel files up to 10MB are accepted, and the email column is detected automatically. If you're unsure about formats, check what file formats email verifiers accept and how to upload a CSV to an email verifier.
- Download the results immediately. Results export as CSV, Excel or JSON. Free-plan results are kept for 24 hours and Pro-plan results for 30 days, so save your files before the window closes. The results file guide explains each column.
- Build the segments. Filter the status column into three files. Add the
segmentandverified_onvalues to your master file, matching on the contact ID rather than the email address. - Re-import each segment as a named list. Unlimited Verifier has no native ESP, CRM or Zapier integrations, so you move segments by re-importing the CSV. Import Valid segments into your ESP as named lists, and add Invalid addresses to its suppression list. The re-import guide covers the details.
To spot-check a single high-value contact that came back Risky, use the free email checker before you decide whether it belongs in a segment.
Bottom line: Export, clean, verify, save the results, split by status, then re-import each segment under its own name.
Worked example: segmenting a 48,000-contact list
The percentages below are illustrative, but the plan limits and arithmetic are real.
The list: A B2B software company has 48,000 contacts. 30,000 came from its own sign-up form, and 18,000 came from a trade-show list imported two years ago.
Upload: Pro lists are capped at 25,000 emails, so the company uploads two files of 25,000 and 23,000 rows. Standard verification is included, with no per-email charge.
Results (illustrative):
| Status | Count | Share |
|---|---|---|
| Valid | 39,120 | 81.5% |
| Risky | 5,280 | 11.0% |
| Invalid | 3,600 | 7.5% |
| Total | 48,000 | 100% |
Segment map:
| Segment | Size | Share of list | Decision |
|---|---|---|---|
| Valid, clicked or purchased in last 90 days | 26,400 | 55.0% | Wave 1 |
| Valid, no engagement in 90 days | 12,720 | 26.5% | Wave 2, after Wave 1 bounces check out |
| Risky, catch-all | 3,100 | 6.5% | 300-address test sample |
| Risky, role-based | 1,200 | 2.5% | Exclude from marketing sends |
| Risky, disposable | 380 | 0.8% | Suppress |
| Risky, other or timed out | 600 | 1.3% | Re-verify after a few days |
| Invalid | 3,600 | 7.5% | Suppress |
The segments add up to 48,000 (26,400 + 12,720 + 3,100 + 1,200 + 380 + 600 + 3,600), and the Risky subtypes add up to 5,280.
Deep verification budget: The company runs deep verification on the 5,280 Risky addresses, since that's where an extra check is most likely to change a decision. Unlimited Verifier states 99.5% accuracy for its deep verification, which is the company's own figure. Those checks use 5,280 of Pro's 25,000 monthly deep verifications, leaving 19,720 for the next list. The Free plan's 750 deep verifications would not cover this group.
Send plan for Valid-engaged contacts (26,400):
- Day 1: 6,000 most recent clicks or purchases
- Day 3: 10,000 next most engaged
- Day 7: 10,400 remaining engaged contacts (6,000 + 10,000 + 10,400 = 26,400)
Send plan for the rest:
- Day 14: 12,720 Valid unengaged contacts, split into two sends of 6,360. Check bounces between them.
- Day 21: A 300-address catch-all test. If it produces 2 or fewer bounces (under 1%), release the remaining 2,800 catch-all addresses in batches. If it produces more, hold them and re-verify.
Ceilings: The company sets a bounce ceiling of 1% per wave. If any wave passes 2%, it pauses and re-verifies that wave's list before continuing.
Cost and limits: The run needs one Pro month at $29. The Free plan could not do it. 48,000 contacts at 150 per list would need 320 lists, and Free allows 25 a month.
Bottom line: Splitting by status, then ranking Valid contacts by engagement, gives the company a send order it can explain line by line to an ESP reviewer.
How should you handle catch-all, role-based and disposable addresses?
Each Risky subtype fails for a different reason, so each needs its own action.
| Subtype | Why it's Risky | Segment decision | Action |
|---|---|---|---|
| Catch-all | The domain's server accepts any address, so the individual mailbox can't be confirmed | Separate segment, tested with a small sample | Promote to Valid only if the sample's bounces stay low. Catch-all email verification explains how these results are flagged. |
| Role-based | Shared inboxes like info@ or sales@ get low engagement and often draw complaints from several people | Exclude from personalised campaigns | Keep only for transactional mail that your contract or terms allow |
| Disposable | Throwaway domains are often used by people who never meant to engage | Suppress from marketing | Consider blocking these domains at sign-up |
| Temporary or timed out | A busy or greylisting server may have returned a temporary error. Reply codes in the 4xx range indicate transient failure under RFC 5321 | Hold | Re-verify after a few days. Some will resolve to Valid. |
The catch-all decision needs the most judgement. Catch-all domains are common in corporate B2B lists, so a large share of your Risky segment may sit there. Don't move them into Valid to hit a volume target. Test them, and let the bounce data decide.
Bottom line: Don't treat Risky as one bucket. Each subtype has a different reason for uncertainty and a different fix.
How do you keep segments accurate over time?
Segments decay. People change jobs, domains expire and mailboxes close, so a Valid segment from three months ago can contain Invalid addresses today. Three habits keep segments current.
- Re-verify on a schedule. Monthly checks suit high-churn B2B lists, and quarterly checks suit more stable consumer lists. The email list maintenance best practices guide covers cadence in more detail.
- Stamp every row. The
verified_oncolumn shows which segments need a fresh check. - Verify at the point of entry. Real-time checks at sign-up stop many new Invalid addresses before they reach the list. The real-time email validation guide covers form-level setups. For automation, the email verification API accepts single-email checks and bulk batches of up to 10,000 emails per request, and Pro includes 100,000 API emails a month. API access is not included on the Free plan. For workflow patterns, see email verification API and automation.
When you merge results back into a CRM, match on the contact ID rather than the email address. Case and whitespace differences would otherwise create duplicate rows and lost results. The merge verification results into a CRM guide walks through the steps.
Bottom line: Stamp each row with its verification date, re-verify on a schedule, and check new addresses at sign-up.
What bounce, complaint and engagement thresholds should guide each segment?
Sources disagree on several of these numbers, so the table shows what each one says and the figure we recommend.
| Threshold | What sources say | Recommendation |
|---|---|---|
| Bounce rate | Amazon SES documentation sets 5% as the review point. Other ESPs apply their own limits, which may be lower | Set an internal ceiling of 2% per send, and 1% for the first waves after a list is re-activated |
| Spam complaints | Google's sender guidelines ask bulk senders to keep spam rates below 0.3% | Treat 0.3% as the hard ceiling, and monitor complaints per segment |
| Engagement window | Teams commonly use 30, 60, 90 or 180 days. No single window is standard | Use 90 days as your default Valid-engaged window, and 30 days for the first wave after re-activation |
| Catch-all handling | Verifiers differ on whether catch-all results count as deliverable or Risky | Never blend catch-all into Valid. Keep it as a separate, tested segment |
Where sources conflict, use the stricter number, since it protects your bounce rate. A 90-day engagement window captures most active contacts while keeping the first send to recent responders. Catch-all addresses are where a blended Valid count does the most damage.
These are our recommendations, not an industry standard. Compare them with your ESP's published guidance and with your own bounce data after each wave.
Bottom line: When two sources disagree, use the stricter number and measure each segment against it.
Common mistakes
- Merging Risky into Valid to hit a volume target. This is a common way to turn a clean list into a bounce problem.
- Ranking Valid contacts by open rate alone. Privacy features inflate opens, so use clicks, purchases or replies.
- Letting results expire. Free-plan results are kept for 24 hours and Pro-plan results for 30 days. Export before the window closes.
- Deleting Risky addresses permanently on day one. Temporary errors can look Risky, and many of those addresses resolve on re-verification.
- Matching on email instead of a contact ID. Case and whitespace differences create duplicate rows and lost results.
- Dropping suppression history. When you move segments between tools, carry over your unsubscribe, complaint and bounce lists.
- Verifying only new imports. Older addresses decay, so the existing list needs the same check.
- Treating Valid as consent. A deliverable address isn't an opted-in one. Confirm each segment's consent basis before you send.
Bottom line: Many segmentation failures come from mixing segments that should stay apart, or from acting on stale data.
How we compared (and limitations)
This guide is based on public documentation: Amazon SES's published bounce guidance, Google's sender guidelines, RFC 3463 and RFC 5321 for SMTP status codes, the FTC's CAN-SPAM guide, and Unlimited Verifier's published plan details. We haven't run controlled tests against any ESP's review process, and provider thresholds change without notice.
Unlimited Verifier's plan limits and features come from the company's published details. The 99.5% deep verification accuracy is the company's stated figure, not an independent benchmark. The 48,000-contact example uses illustrative percentages, not real campaign results. Your segment sizes will depend on your list's age, source mix and industry.
Bottom line: Treat these thresholds as starting points, and confirm them against your own bounce, complaint and engagement data for each segment.
Worked example: bounce rate impact of one segment
Scenario: a 20,000-contact send includes 1,200 Invalid addresses.
| Step | Calculation | Result |
|---|---|---|
| Invalid share | 1,200 / 20,000 | 6% |
| After suppressing Invalid | 0 / 18,800 | 0% from known-bad addresses |
| Valid remaining | 18,800 contacts | Send first, most engaged first |
Suppressing the 1,200 Invalid addresses before sending removes the entire 6% known-bounce load from the send.
Frequently asked questions
What is a Risky email address?
A Risky address is one a verifier cannot confirm as safe or deliverable. Catch-all domains, disposable domains, role addresses like info@ or sales@, and temporary server errors commonly produce this status. Risky is a confidence label, so test these addresses in small batches rather than discarding or fully trusting them.
Should I send to Risky email addresses?
Send to Risky addresses only after your Valid segment, and only in small batches while watching bounces and complaints. If the batch performs poorly, suppress the rest of that group. This limits reputation damage while still recovering some reachable contacts.
Should I delete Invalid email addresses?
Suppress Invalid addresses rather than simply deleting them, and keep a record of the suppression. Suppression stops future sends to addresses that will bounce, and the record prevents them from being re-imported later through another sign-up form or list upload.
How often should I re-verify my segments?
Re-verify before major campaigns and on a regular schedule, since addresses go stale as people change jobs and mailboxes close. Many teams re-check active lists more often than dormant ones. Your schedule should match how fast your list changes and how often you send.
Why do I need to save my verification results file?
Verification results files can expire or be removed after a set period, so download and save the results before that happens. Without the file you lose the status of each address and must re-verify the whole list to rebuild your segments.
Can I combine verification status with engagement data?
Yes, and you should. Layering engagement recency and signup source onto verification status lets you rank Valid contacts by likelihood to open, and decide whether a Risky address from a high-intent source deserves a test batch.
What is a catch-all domain?
A catch-all domain is a mail server configured to accept mail for any address on that domain, whether or not the mailbox exists. Because the server accepts everything, a verifier cannot confirm individual mailboxes, so these addresses typically land in the Risky segment.
What does an SMTP 5.1.1 error mean?
SMTP 5.1.1 is the code for a bad destination mailbox, defined in RFC 3463 as an enhanced status code. It indicates the mailbox does not exist and the failure is permanent, which is why addresses returning it belong in the Invalid segment and should be suppressed.
Why does a single bad segment hurt the whole send?
Bounces are measured across the entire send, so a small group of Invalid addresses can raise the overall bounce rate. Sending providers watch this rate closely, and a high rate can lead to account review or throttling, which is why suppressing Invalid addresses first protects every other contact.
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 standard verification on all plans, including Free, with no per-email fees.
- Catch-all detection so you know which domains accept every address.
- Clear Valid / Risky / Invalid results, exportable as CSV, Excel or JSON.
- An open-source verification engine you can inspect on GitHub.
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.