Article
What Is a Good Unknown Rate for an Email Verifier? Thresholds by Source
By Unlimited Verifier Team ·

Summary
A good unknown rate for an email verifier is under 5% of the full list on a fresh, opt-in database, with under 2% for the segment you mail first. Unknown means the mail server gave no clear yes or no, so it is not proof an address is bad. Measure unknowns by source and mailbox domain, since a blended average can hide a problem segment.A good unknown rate for an email verifier is under 5% of your total list on a fresh, opt-in database, and most teams should treat anything above 10% as a signal to investigate before sending. An unknown result means the verifier could not get a clear yes or no from the recipient's mail server, so it is an "I can't tell" answer, not proof that the address is bad. We are not aware of a standards-body threshold for this number, so the bands below are a practitioner rule of thumb. The more useful figure is the unknown rate broken down by source and mailbox domain.
Quick answer
- Target: Under 5% unknown across the whole list, and under 2% for the segment you mail first after cleaning.
- Thresholds: 5–10% means investigate by source. Above 10% means find and fix the responsible source. Above 20% means stop mailing that source until its consent is rebuilt.
- Unknown is not invalid. Many unknowns are temporary server responses or strict mail gateways. Deleting all of them drops real customers.
- Measure by segment. A blended 5% can hide a legacy source at 36%. A 150-row sample cannot reliably tell 5% from 8%.
- In Unlimited Verifier, results are sorted into Valid, Risky and Invalid. Use the Risky share as a proxy for unknowns, but remember Risky also includes catch-all, disposable and role-based addresses, so it overstates true unknowns.
This page is part of our complete guide to email verifier accuracy.
What does "unknown" mean in an email verification result?
A verifier checks an address by connecting to the recipient domain's mail server and asking whether it will accept mail for that mailbox. This is the SMTP mailbox check, and the server's reply decides the result. An acceptance on a normal domain points to valid, and a permanent rejection points to invalid.
RFC 5321 defines the reply classes: 4xx replies are temporary failures the sender should retry, and 5xx replies are permanent failures. RFC 3463 adds enhanced status codes, such as 5.1.1 for an unknown destination mailbox.
Unknown covers everything in between: a probe that timed out, a temporary 4xx reply, a server that declined to answer the check, or a reply too ambiguous to classify.
Catch-all domains create a second kind of ambiguity. A server that accepts every recipient returns a positive reply even for made-up mailboxes, so the check never confirms that a specific person exists. Unlimited Verifier detects catch-all domains, and our catch-all email verification page explains how they are handled. For the wider accuracy picture, see how accurate email verification really is.
Bottom line: Unknown means the server gave no usable answer. It is neither proof of a bad address nor proof of a good one.
What is a good unknown rate for an email verifier?
Use these bands as your working standard. Vendors and ESPs describe uncertain results in different ways, and there is no shared definition of "unknown," so a number from one tool is not directly comparable to a number from another. We recommend 5% as the ceiling for the full list.
| Blended unknown rate | What it usually means | What to do |
|---|---|---|
| Under 5% | Normal friction on an engaged, opt-in list | Send to Valid rows, hold the rest, keep monitoring |
| 5–10% | Mixed sources, or a few strict domains raising the average | Break the list down by source and domain before sending |
| 10–20% | One source or domain group is driving the number | Fix or suppress that segment, then re-verify |
| Over 20% | Purchased, scraped or very old data, or a configuration problem | Stop mailing that source and rebuild consent first |
Why 5%? Any large list will have some greylisted or strict servers, so a small unknown share is expected. Above 10%, unknowns stop looking like random friction and start pointing at a specific source. That source is where the fix belongs.
Bottom line: Aim for under 5% blended and under 2% for your first sends. Above 10%, don't average the problem away. Find the segment causing it.
Why does the unknown rate vary so much between lists?
List source matters more than list size. A 5,000-row sign-up list and a 5,000-row event scan can have very different unknown rates, even though both look clean to their owners. The causes are predictable:
| Cause | How it shows up | Why it is unknown, not invalid | Practical response |
|---|---|---|---|
| Greylisting or deferral | Temporary 4xx reply | The server asked the sender to retry later | Re-run the unknown rows after a delay |
| Strict or gateway-protected servers | Often seen on enterprise domains | Some gateways accept mail and filter later, or decline verification probes | Hold for engagement rather than deleting |
| Slow or unreachable mail servers | Timeouts | No reply arrived in time | Retry, and check whether the domain still receives mail |
| Catch-all domains | Positive reply to every address | Acceptance does not confirm the mailbox | Treat as uncertain, not valid |
| Provider-specific probe limits | Results differ by mailbox provider | Some large providers limit how far SMTP checks can go | Compare results by provider; see Gmail vs Outlook accuracy |
Two patterns matter in practice. First, unknown is often a timing result. The same domain can return unknown on one run and a definitive answer on the next, so a single run is only a snapshot. Second, sign-up addresses usually come from people who recently interacted with you, so they tend to be fresher than purchased or legacy data. That is why teams working on email verification for ecommerce and SaaS lists often see their lowest unknown rates on new sign-ups.
Bottom line: The source of the list explains most of the variation. Retry before you judge, because unknowns can resolve on a later run.
How many rows do you need to measure an unknown rate reliably?
A sample only describes the population it came from, and small samples carry wide margins. The table uses the standard 95% margin of error for a proportion, 1.96 × √(p(1−p)/n), assuming a true unknown rate of 5% and a random sample.
| Random sample size | Margin of error at 5% | Plausible range for the true rate |
|---|---|---|
| 150 | ±3.5 points | 1.5% to 8.5% |
| 500 | ±1.9 points | 3.1% to 6.9% |
| 1,000 | ±1.4 points | 3.6% to 6.4% |
| 1,825 | ±1.0 point | 4.0% to 6.0% |
A 150-row sample is enough to spot a serious problem, such as a 30% unknown share. It cannot tell a 5% list from an 8% list. The Free plan's 150-row lists suit spot checks, but they are not a basis for deciding whether a 60,000-row list is safe to mail.
For sending decisions, verify every row in the segment rather than sampling. Sampling answers "roughly how big is the problem?" Full verification answers "which rows should I send to?" For test design, see how many emails to use when testing a verifier.
Bottom line: To estimate a 5% rate within ±1 point, you need about 1,800 random rows. For sending decisions, verify the whole segment.
How do you calculate an unknown rate correctly?
Follow this sequence so the number can be compared next time:
- Deduplicate first. Duplicate addresses inflate the total and repeat the same result, which skews the rate.
- Verify the full list if the result will drive a sending decision.
- Count the unresolved rows. In Unlimited Verifier, use the Risky count as a proxy. If your tool reports an explicit unknown status, use that count instead.
- Divide by all unique rows: unknown rate = unresolved rows ÷ total unique rows × 100.
- Repeat by source and by top domain. This requires a source column added before upload.
- Log the date, tool and settings so the next run is comparable.
Keep Invalid rows in the denominator. They are part of the list you are judging, and removing them makes the rate look better than it is.
Bottom line: Deduplicate, verify, divide by all unique rows, and report by segment with the date attached.
How do you measure your unknown rate in Unlimited Verifier?
- Export your list as CSV from your ESP or CRM. If you can, add a
sourcecolumn (for example: signup, event, purchase, legacy) before exporting. - Create an account. You can sign up for free. The Free plan covers 25 lists a month of up to 150 emails each. The Pro plan is $29/month, or $25/month billed annually, and handles lists of up to 25,000 emails each. For how costs add up at volume, see email verification pricing.
- Split files over 25,000 rows. A 60,000-row list becomes three Pro lists: 25,000, 25,000 and 10,000.
- Deduplicate in your spreadsheet. In Excel, use Data > Remove Duplicates. In Google Sheets, use Data > Data cleanup > Remove duplicates.
- Add a domain column. If emails are in column A, enter
=MID(A2,FIND("@",A2)+1,100)in the next free column of row 2 and fill down. - Upload and verify a list. CSV and Excel files up to 10MB are accepted, and the email column is detected automatically.
- Record the three counts: Valid, Risky and Invalid. Calculate the proxy unknown rate as Risky ÷ total rows.
- Export the results as CSV, Excel or JSON, then pivot by source and domain. Free-plan results are kept for 24 hours, so export before you leave the page. Pro results are kept for 30 days.
- Spot-check important contacts with the free email checker when a single key account comes back Risky.
- Automate new sign-ups with the email verification API. It supports single-email checks and bulk batches of up to 10,000 emails per request. API access is part of Pro (100,000 emails a month), not the Free plan. For workflow patterns, see email verification API and automation and real-time validation.
Unlimited Verifier does not offer native ESP, CRM or Zapier integrations, so each run is an export, a verification and a re-import, or an API call from your own scripts.
Bottom line: Export with a source column, dedupe, split if needed, verify, and log three counts. That gives you a measured unknown rate in one afternoon.
What does a real unknown-rate breakdown look like?
This scenario is hypothetical. It illustrates the arithmetic and the decisions, not real results. The list has 12,000 unique rows, which fits in one Pro list under the 25,000-row cap.
Blended result:
- Valid: 9,840 (82.0%)
- Risky: 1,560 (13.0%), above the 10% line
- Invalid: 600 (5.0%)
Check: 9,840 + 1,560 + 600 = 12,000.
Breakdown by source:
| Source | Rows | Risky | Risky rate |
|---|---|---|---|
| Sign-up form | 7,000 | 300 | 4.3% |
| Event scan | 3,000 | 540 | 18.0% |
| Legacy CRM | 2,000 | 720 | 36.0% |
| Total | 12,000 | 1,560 | 13.0% |
Check: 300 + 540 + 720 = 1,560.
The blended 13% looks like a list-wide problem. The source table shows it is concentrated in two sources, and the sign-up source sits inside the under-5% band.
Step 1: Suppress the legacy source. Remove 2,000 rows from all campaigns. This leaves 10,000 rows, with 840 Risky (8.4%).
Step 2: Hold the event scan. Its 3,000 rows run at 18% Risky, so they go into a re-permission message rather than the first campaign. That leaves the sign-up segment: 7,000 rows, 300 Risky (4.3%).
Step 3: Deep-verify the sign-up Risky rows. The 300 rows use 1.2% of the Pro plan's 25,000 monthly deep verifications (300 ÷ 25,000). Illustratively, if the deep pass resolves 180 of them, 120 remain unresolved. That is 1.7% of 7,000 (120 ÷ 7,000), under the 2% target for a first send.
Step 4: Send the first campaign only to Valid rows in the sign-up segment. Hold the 120 unresolved rows for a later re-check.
Cost: One Pro month at $29, or $25 if billed annually. Standard verification of the full list carries no per-email fee on any plan.
Bottom line: The 13% figure became one bad source to suppress, one to re-permission, and a clean segment to mail. A list-wide decision would have thrown away the 7,000 good rows.
What should you do with unknown addresses?
Unknown rows should not go into your first campaign by default. Decide per segment:
| Unknown row type | In the first campaign? | Next step |
|---|---|---|
| Recently engaged contact, unknown on first run | Hold, or include in a small test | Re-verify after a short delay |
| Unknown at a catch-all domain, engaged | Only at the end of your ramp | Watch bounces on every send |
| Unknown from a purchased or legacy list | No | Suppress, or re-permission first |
| Temporary 4xx that persists across runs | No | Suppress after repeated unresolved runs (we suggest three, as a rule of thumb) |
| Unknown at an enterprise gateway, B2B contact | Small test at the end of the ramp | Move to Valid once sends succeed |
The reason to hold unknowns is reputation. Bounces on the first send after an import tend to do the most damage to sender reputation. Google's sender guidelines ask bulk senders to avoid reported spam rates of 0.3% or higher and to aim to stay below 0.1%. Bad addresses often produce complaints as well as bounces.
Two cautions. A Valid result is not a delivery guarantee, as explained in does a valid result mean the email will be delivered. And verification is list hygiene, not consent. It cannot show that someone opted in, which is why email verification compliance and hygiene must sit alongside documented permission. For ongoing routines, see email list maintenance best practices.
Bottom line: Hold unknowns, ramp them in last, and suppress persistent unknowns from legacy or purchased sources.
How do unknown rates compare between verification tools?
Definitions vary, so comparing unknown rates across tools is only meaningful on the same list, on the same day, with the same definition. Some tools return an explicit unknown status. Others fold uncertain results into risky or catch-all categories. Before comparing, agree on what counts as an error; what is a false positive in email verification covers one common source of disagreement. Why different email verifiers give different results explains the mechanics.
| Question to ask | Why it matters | What a good answer looks like |
|---|---|---|
| What produces an unknown or uncertain result? | Shows whether timeouts and greylisting are counted | Documented causes |
| Is catch-all reported separately? | A catch-all domain does not confirm a mailbox | A distinct flag, not a silent "valid" |
| Can you export a per-row status? | Needed for source and domain analysis | CSV, Excel or JSON export with per-row results |
| Can you inspect the verification logic? | Lets you judge the method, not just the marketing | An open or documented engine |
Unlimited Verifier sorts results into Valid, Risky and Invalid, flags catch-all, disposable and role-based addresses, and exports CSV, Excel or JSON. It publishes an open-source verification engine on GitHub, so you can read how it structures SMTP checks. Confirm that the hosted service uses the same logic before you rely on it. The company states 99.5% accuracy for deep verification. That is Unlimited Verifier's own figure, so test it on your own list, as discussed in are vendor accuracy claims for email verifiers trustworthy.
For a broader shortlist, see best email verification tools and how to choose an email verifier.
Bottom line: Compare tools on the same list, on the same day, with the same definition of unknown. Insist on per-row exports.
What are the common mistakes when reading unknown rates?
- Deleting every unknown. You will drop real customers behind greylisting and strict gateways. Retry and hold instead.
- Treating unknown as valid. Mailing unconfirmed addresses in bulk can turn a 6% problem into a deliverability problem.
- Judging a large list from a 150-row sample. That works for a spot check, not a 60,000-row decision.
- Reading only the blended number. A 5% total can hide a 36% legacy source.
- Using the wrong denominator. Dropping Invalid rows or leaving duplicates in distorts the rate.
- Comparing tools on different lists or dates. Results shift with timing and definitions.
- Assuming catch-all means fine. A domain that accepts everything tells you nothing about one specific mailbox.
Bottom line: Most mistakes come from reading a single number without its segment, denominator or date.
How we compared (and limitations)
- Sources: This guide is based on public documentation: RFC 5321 and RFC 3463 for SMTP reply codes, Google's sender guidelines for bulk-sender expectations, and Unlimited Verifier's published plan details and product description.
- No testing: We have not run controlled tests against any verifier or ESP, and we have not benchmarked unknown rates across tools. The bands are a practitioner rule of thumb, not a published standard.
- Statistics: The sample-size table uses standard margin-of-error arithmetic for random samples. Real lists are rarely random, so treat the margins as approximate.
- Vendor figures: Unlimited Verifier's 99.5% deep-verification accuracy is the company's own figure. For third-party context, see independent email verifier accuracy benchmark 2026 and do email verifiers really have 99% accuracy.
- Worked example: All figures are hypothetical and illustrate the arithmetic, not real results.
- Change over time: Server behaviour and provider policies change. Re-check the bands against your own data before relying on them.
Unknown rate thresholds and actions
| Blended unknown rate | What it usually means | What to do |
|---|---|---|
| Under 5% | Normal friction on engaged, opt-in list | Send to Valid rows, hold the rest |
| 5% to 10% | Investigate by source | Break down unknowns by source and domain |
| 10% to 20% | Responsible source identified | Fix or re-consent that source |
| Above 20% | Source quality is poor | Stop mailing that source until consent is rebuilt |
Frequently asked questions
Is an unknown email address invalid?
No. An unknown result means the verifier could not get a clear answer from the recipient's mail server, often due to a timeout, a temporary 4xx reply, or a strict gateway. Many unknown addresses are real, active mailboxes, so deleting them all removes genuine customers. Treat unknowns as a reason to investigate, not as confirmed bad addresses.
Why does my email verifier return so many unknowns?
Common causes include mail servers that rate-limit or block verification probes, temporary server errors, greylisting, and strict security gateways. Older lists and catch-all domains also produce more ambiguous replies. Checking unknowns by source and mailbox domain usually shows whether one segment is driving the number.
Should I send emails to unknown addresses?
Send cautiously, if at all, and only to addresses with a clear opt-in and recent engagement. Unknowns carry more bounce and complaint risk than valid addresses. Start with a small test segment, watch your bounce rate, and stop mailing any source whose unknowns keep rising.
What is the difference between risky and unknown email results?
Risky is a broader category that can include catch-all domains, disposable addresses, role-based addresses such as info@, and unknown results. Because of this, the risky share overstates the true unknown rate. Check the individual reason codes where your verifier provides them to separate true unknowns from other risky addresses.
What is a catch-all domain and how does it affect unknowns?
A catch-all domain is a mail server configured to accept mail for any address at that domain, even nonexistent ones. The server's positive reply therefore cannot confirm that a specific person exists. Verifiers often label these addresses risky or unknown rather than valid, which can inflate your unknown count if the domain is common in your list.
How often should I re-verify my list?
Re-verify before major campaigns and whenever a list has aged significantly, since addresses decay and domains change their mail configuration. Lists that have not been mailed in many months generally need fresh verification before use. Tracking the unknown rate over time shows whether your list quality is improving or drifting.
Does a high unknown rate hurt deliverability?
It can. Sending to a large share of unverified or unknown addresses raises the chance of hard bounces, which damage sender reputation over time. Keeping unknowns out of your main sends and monitoring bounce rate protects inbox placement. Mailbox providers pay close attention to bounce and complaint patterns.
Is there an industry standard for an acceptable unknown rate?
No standards body publishes an official unknown-rate threshold. The bands in this article are a practitioner rule of thumb. Because vendors define unknown differently, compare your results over time using the same verifier rather than across tools.
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.