Article
Do Email Verifiers Charge for Unknown Results? How Billing Really Works
By Unlimited Verifier Team ·

Summary
Most per-check email verifiers charge for unknown results, because the check still ran even without a Valid or Invalid verdict. Billing rules vary, so the vendor's written policy on unknowns matters more than the headline unit price.Yes, often. If a verifier bills per check, an unknown result still costs one credit, because the check ran without reaching a Valid or Invalid verdict. Some models exclude unknowns or allow free retries, so read the written billing policy before you buy.
Quick answer
- Per-check vendors typically bill unknowns. Some waive the charge or allow free retries, but that policy is rarely on the pricing page, so ask for it in writing.
- Unknowns usually come from the receiving server. Greylisting, probe blocking and catch-all domains are common causes, so unknowns tend to cluster by domain.
- Price the definitive result, not the check. Divide the unit price by the share of checks that return Valid or Invalid to get your real cost.
- Unlimited Verifier's standard verification has no per-email fee on any plan. Deep verifications are capped at 750 a month on Free and 25,000 a month on Pro, so spend them on unresolved rows.
- Don't mail unknowns to find out. Re-check once after 24 to 48 hours, then hold back whatever stays unresolved.
Do email verifiers charge for unknown results?
Whether an unknown costs you depends on the vendor's billing rule, not on the verdict. Verifiers that charge per check bill every row they process, including rows that come back inconclusive. Other models exclude unknowns, refund a retry, or draw from a monthly allowance. Full email verification pricing has two parts: the unit price, and the rule for which results consume a unit.
Most comparisons focus on the unit price and skip the second part. That is the expensive omission, because your list's unknown rate determines what you actually spend. For a wider breakdown, start with our email verification cost guide.
Bottom line: The unit price tells you what a check costs. The unknown policy tells you what you pay for a usable answer.
What counts as an unknown result?
An unknown is a check where the verifier could not get a definitive answer from the receiving mail server. It is not the same as "Risky" or "catch-all," although vendors often blur the labels.
The main causes are:
- Greylisting. The receiving server replies with a temporary 4xx code, which RFC 5321 classes as a transient negative completion reply, and asks the sender to try again later. A verifier that doesn't retry records no verdict.
- Probe blocking. Some servers accept the connection but won't confirm whether a specific recipient exists, returning a generic response instead.
- Timeouts and refused connections. Slow or firewalled servers never complete the handshake.
- Rate limiting. A receiving server may throttle a verifier that sends many probes to one domain in a short window.
- Catch-all domains. The server accepts mail for any address, so the mailbox can't be confirmed. Many tools file these as Risky rather than unknown. Our catch-all email verification page explains how that category is handled.
Because most causes sit on the receiving server, unknowns cluster by domain. One organisation that rate-limits probes can account for a large block of unknowns in a single file. Sorting unknowns by domain shows whether the problem is a few large providers or scattered data quality.
Labels are not standardised. One tool's "unknown" can be another's "unverifiable" or "accept-all," so compare definitions, not names.
Bottom line: Unknowns usually come from the receiving server rather than bad data, which is why they cluster by domain.
How do vendors bill unknown results?
Verifiers use four common billing models. Vendor pricing pages often don't say which one applies, so you will need to ask.
| Billing model | What an unknown costs | Main risk for you |
|---|---|---|
| Charge every check | Full price, and again on every retry | Your bill rises with your unknown rate |
| Charge only definitive results | Nothing | The vendor's definition of "definitive" may not match what you're willing to mail |
| Free retry within a window | Full price on the first pass, free if re-checked soon | The window and retry limits are easy to miss in the fine print |
| Monthly allowance with unlimited standard checks | Nothing per email; deep checks draw from a capped allowance | The deep allowance can run out, so you need to budget it |
The last model describes Unlimited Verifier. Standard verification is unlimited on every plan, including Free, with no per-email fees. Deep verifications are metered at 750 a month on Free and 25,000 a month on Pro. Whether a particular row draws from the deep allowance is the detail to confirm before a large run.
If you buy credit packs elsewhere, check what happens to unused email verification credits before you commit. For current unit prices, see how much email verification costs in 2026. Retry and resubmission fees that don't appear on the headline price are covered in hidden costs of email verification services.
Bottom line: Four billing models exist, and only the written policy tells you which one a vendor uses.
Why does the price per definitive result matter more than the unit price?
When unknowns are billed, your real cost per usable answer is the unit price divided by the share of checks that return a definitive result. The headline price understates your cost whenever the unknown rate is high.
Here is a comparison using illustrative numbers:
- Vendor A: $0.004 per check, charges every row. Returns Valid or Invalid for 80% of rows.
- Vendor B: $0.005 per check, charges only definitive results.
Vendor A's effective price per definitive result is $0.004 ÷ 0.80 = $0.005. Vendor B's is $0.005 ÷ 1.00 = $0.005, because every charged check is definitive. Vendor A looks 20% cheaper at the unit level and works out equal once unknowns are counted. If Vendor A's definitive share fell to 70%, its effective price would rise to about $0.0057.
Unknown rates vary by data source. Sign-up forms, purchased lists and CRM exports all produce different mixes of corporate domains, strict servers and catch-alls. Ecommerce and SaaS teams should measure their own unknown rate on a sample rather than trust a vendor's example set. For guidance on that workflow, see email verification for ecommerce and SaaS.
Bottom line: Divide the unit price by your definitive rate. That result is the number to compare across vendors.
How do you test a verifier's unknown-result billing before you buy?
Run a small test file and compare your usage before and after. The change reveals the billing policy, provided the vendor shows usage at all.
- Build a 150-row test file. Use 50 addresses you know are active, 50 that hard-bounced in past campaigns, and 50 at domains you suspect are catch-all or strict.
- Record your balance or allowance before uploading. Screenshot it so you have a clean before-and-after.
- Upload using the standard flow, not an API call, so you measure the path you'll actually use.
- Count each bucket using the vendor's labels. Write down what each label means according to its documentation.
- Check the balance again. If a per-check vendor's balance dropped by 150, it bills every check. If it dropped only by the number of Valid plus Invalid rows, unknowns are free. If the vendor shows no balance at all, ask for a written example of how an unknown row is billed.
- Re-upload only the unknown rows after 24 hours. If the balance drops again, retries are billed.
- Get the answer in writing. Ask the vendor to confirm the policy by email before you commit.
Unlimited Verifier's Free plan fits this test neatly: a 150-row file is exactly one Free list, which allows up to 150 emails. Because standard verification carries no per-email fee, the metered item to watch is the deep allowance. Create a free account to run the test on your own rows.
Bottom line: A 150-row test and two usage readings answer the billing question more reliably than any pricing page.
How much do unknown results cost at scale?
Unknowns add real cost to a large list even at low unit prices. Here is an illustrative 50,000-row pass at $0.004 per check, with a 12% unknown rate (6,000 rows).
Scenario A: unknowns are billed
- First pass: 50,000 × $0.004 = $200, covering 44,000 definitive results and 6,000 unknowns.
- Retry the 6,000 unknowns once at full price: 6,000 × $0.004 = $24. Assume half resolve to a definitive result, adding 3,000.
- Total: $224 for 47,000 definitive results, or about $0.0048 each.
Scenario B: unknowns are free
- First pass: 44,000 × $0.004 = $176, with unknowns not charged.
- Retry the 6,000 unknowns free, adding 3,000 definitive results.
- Total: $176 for 47,000 definitive results, or about $0.0037 each.
The gap is $48 on one pass, which makes Scenario A about 27% more per definitive result. At 500,000 rows, the same assumptions produce a gap of roughly $480. For a full model, see how much it costs to verify 500,000 emails. To turn totals into cost per lead, use how to calculate email verification cost per lead. Agencies that run this across many client lists should also read email verification pricing for agencies with many clients.
Bottom line: At scale, the unknown policy can outweigh the unit-price difference you were comparing.
How does Unlimited Verifier handle unknown and Risky results?
Unlimited Verifier checks syntax, domain, MX records and the SMTP mailbox, detects catch-all domains, and flags disposable and role-based addresses. It sorts every address into Valid, Risky or Invalid, and exports results as CSV, Excel or JSON. When you review an export, treat any row that is neither Valid nor Invalid as unresolved, and hold it back until you've decided what to do with it.
The practical rules are:
- Standard verification has no per-email fee. You can re-run a list without budgeting for each check. For what "unlimited" does and doesn't cover, read what "unlimited" really means in email verification.
- Deep verification is the metered step. Free includes 750 a month and Pro includes 25,000. Use deep checks on unresolved rows, not the whole list. The company states 99.5% accuracy for deep verification. That is Unlimited Verifier's own figure, not an independent benchmark.
- Results expire. Free keeps results for 24 hours and Pro for 30 days, so export before the window closes.
- Lists have caps. Free allows 25 lists a month of up to 150 emails each, a ceiling of 3,750 emails a month through standard uploads. Pro allows unlimited lists, each up to 25,000 emails.
Worked example on Free. Suppose you have the 50,000-row list from the previous section. At 150 rows per list, you need at least 334 lists (50,000 ÷ 150 = 333.3, rounded up). Free allows 25 lists a month, so the job takes 14 months (334 ÷ 25 = 13.4, rounded up). Free suits testing, not a 50,000-row cleanup.
Worked example on Pro. Split the same 50,000 rows into two uploads of 25,000 each, within the per-list cap. Suppose the results are 40,000 Valid, 4,000 Invalid and 6,000 unresolved (illustrative). Standard verification adds no per-email fee, so the month costs the Pro price of $29, or $25 a month billed annually. If deep-checking the 6,000 unresolved rows draws one unit each, the allowance drops from 25,000 to 19,000. A per-check vendor at the illustrative $0.004 rate would bill $200 for the first pass alone, before retries.
The email verification API accepts single-email checks and batches of up to 10,000 emails per request. Pro includes 100,000 API emails a month, and Free has no API access. How API and bulk billing differ is covered in API email verification pricing versus bulk upload pricing. Unlimited Verifier has no native ESP, CRM or Zapier integrations, so the workflow is to export a CSV, verify it, and re-import, or to call the email verification API and automation from your own scripts. If you're weighing budget options under $30 a month, see the best value email verifier under $30 a month.
Bottom line: Unlimited standard checks remove the per-email cost of unknowns. The deep allowance is the budget to plan.
How do you re-check unknown results with Unlimited Verifier?
- Sign up and confirm your limits. Create a free account and check the list cap and result-retention window for your plan.
- Export the unresolved rows from your last run as CSV or Excel. Keep the full original file so you can match rows back later.
- Upload the file on the Upload and verify a list page. CSV and Excel files up to 10MB are accepted, and the email column is detected automatically. Split files so each list stays within 150 rows on Free or 25,000 rows on Pro.
- Wait before re-checking. Greylisting windows differ by server, and no universal standard fixes them. Sources don't agree on a single figure, so we recommend 24 to 48 hours as a practical starting point, and avoid re-checking within the same hour.
- Run deep verification on rows still unresolved. Spend allowance on high-value contacts first. For a single address, such as one key account, use the free email checker.
- Sort the output. Valid goes to your sending segment, Invalid gets suppressed, and anything still unresolved or Risky stays on hold.
- Export immediately as CSV, Excel or JSON. Free results last 24 hours and Pro results last 30 days.
- Log the run. Record the date, row count and count per bucket. A reviewer may ask for this record, and it is the core of email verification compliance and hygiene.
Bottom line: The re-check is a short, repeatable process, and the log turns it into evidence.
When is a re-check worth the deep allowance?
Use this table to decide. The thresholds are judgement calls, not industry standards.
| Situation | Suggested action | Why |
|---|---|---|
| Small share of unknowns on a low-value list (for example, an old newsletter list) | Hold back, no re-check | The recovered reach may not justify the allowance |
| Unknowns concentrated on one domain | One targeted re-check, then reach contacts another way | A single server's policy causes the whole cluster |
| High-value contacts (paying customers, enterprise leads) | Deep re-check after 24 to 48 hours | The contact's value justifies the metered check |
| Per-check billing with charged retries | Retry once only | Each further retry costs full price for a smaller yield |
| Catch-all domain | Hold back, or send only to a small engaged test segment | A catch-all accepts every address, so even a favourable result can't confirm the mailbox |
Bottom line: Re-check unknowns when the contact is valuable or the cluster is concentrated, and hold back the rest.
What's a framework for handling unknowns before a send?
- Split every result into three queues: Valid, Invalid, and Unresolved (everything Risky or without a definitive verdict).
- Suppress Invalid immediately. Mailing a nonexistent mailbox produces a hard bounce. RFC 3463 classes a bad destination mailbox as enhanced status code 5.1.1, and repeated hard bounces damage sender reputation.
- Group Unresolved by domain and work the largest clusters first.
- Re-check once after 24 to 48 hours, and deep-check the high-value rows.
- Mail only Valid contacts plus recently engaged ones. Keep Unresolved addresses out until a re-check or a small, monitored test. Google's sender guidelines set spam-complaint thresholds that bulk senders should stay well under, and mailing unverified addresses makes that harder to hold.
- Build the habit into signup and list maintenance. Real-time email validation at signup stops new unknowns entering the list, and email list maintenance best practices covers the recurring schedule.
Bottom line: Three queues, one re-check, and a disciplined send list keep unknowns from becoming your bounce problem.
What are the common mistakes with unknown results?
- Comparing unit prices only. The effective price per definitive result is the comparison that matters.
- Treating an unknown as valid because it hasn't bounced. No bounce means no test, not a pass.
- Mailing unknowns to find out. A live campaign is an expensive and public way to run a verification.
- Retrying immediately. Greylisted servers often need time before they accept a retry, so a same-minute re-check usually repeats the result.
- Assuming labels match across vendors. "Risky" in one tool can mean "catch-all" in another, and some tools use a separate unknown label.
- Spending deep allowance on the whole list. Spend it on unresolved rows, where it changes the outcome.
- Letting results expire. Free results last 24 hours, so export on the same day you run a list.
- Skipping the written billing policy. A pricing page that doesn't mention unknowns isn't an answer.
Bottom line: Most unknown-related losses come from skipping the policy check, or sending before the list is resolved.
How we compared (and limitations)
This article is based on public documentation: RFC 5321 for SMTP reply classes, RFC 3463 for enhanced status codes, Google's sender guidelines, and the FTC's CAN-SPAM guidance. Unlimited Verifier's plan details come from the company's published plans. The 99.5% deep-verification accuracy is the company's own stated figure. The company also publishes its open-source verification engine on GitHub, which you can read to see how checks are structured.
We haven't submitted test files to competing vendors, so this article doesn't state which competitors waive unknown charges. The $0.004 and $0.005 unit prices, unknown rates and resolution shares are illustrative. Vendor billing policies change, so confirm them in writing before you commit. If you're shortlisting providers, our guide to the best email verification tools covers other differences that matter, and how to choose an email verifier sets out a buyer's checklist.
Bottom line: The policy on unknowns is the variable to verify, not assume.
Effective cost per usable answer
Assume a verifier charges 0.005 per check, and 20 percent of a 10,000-row list returns unknown with unknowns billed.
| Item | Value |
|---|---|
| Checks billed | 10,000 |
| Total cost | 50.00 |
| Definitive results | 8,000 |
| Cost per usable answer | 0.00625 |
The listed price is 0.005, but the effective price is 0.00625, 25 percent higher. Re-checking unknowns after 24 to 48 hours can lower this if the retries are free.
Frequently asked questions
Do all email verification services charge for unknown results?
No. Most per-check vendors bill every processed row, including unknowns, but some exclude inconclusive results, allow free retries, or draw from a monthly allowance. The vendor's written billing policy is the only reliable answer.
Why do email verifiers return unknown results?
Unknowns usually come from the receiving mail server. Common causes include greylisting with temporary 4xx replies, probe blocking, timeouts, rate limiting, and catch-all configurations that prevent confirming a specific mailbox.
Can I get a refund for unknown results?
Some vendors credit or refund unknowns, but this is rarely on the pricing page. Ask the provider in writing before purchasing, and confirm whether retries of the same address are free.
Is a catch-all result the same as unknown?
Not usually. Many tools label catch-all domains as Risky rather than unknown, because the server responds positively to any address. Labels differ between vendors, so check how each one classifies catch-all results.
How do I calculate the real cost of verification?
Divide the unit price by the share of checks that return a definitive Valid or Invalid result. If 80 percent of checks resolve, your effective cost per usable answer is 25 percent higher than the listed price.
Should I re-check unknown emails?
Yes, a single re-check after 24 to 48 hours often resolves greylisting or temporary blocks. Check whether retries are billed, and hold back any addresses that remain unknown rather than mailing them.
Does a higher unknown rate mean lower data quality?
Not necessarily. Unknowns often cluster by domain due to receiving-server behaviour rather than list quality. Sorting unknowns by domain helps separate infrastructure issues from genuinely poor addresses.
What should I ask a verifier about unknown billing?
Ask whether unknowns consume credits, whether retries are free, whether catch-all results are billed differently, and whether refunds apply to inconclusive checks. Request the answer in writing and check it against your expected unknown rate.
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.