Article
Fair Use Limits on Unlimited Email Verification Plans: What Caps Actually Apply
By Unlimited Verifier Team ·

Summary
Fair use limits on unlimited email verification plans are metered caps on deep checks, list sizes and API volume, even when standard checks are unlimited. On Unlimited Verifier's published facts, Pro includes 25,000 deep verifications a month and lists up to 25,000 emails, while Free includes 750 deep checks and lists up to 150 emails.Fair use limits on unlimited email verification plans are the metered caps a vendor sets on deep checks, list sizes and API volume, even when standard checks are advertised as unlimited. On Unlimited Verifier's published plan facts, the ceilings that matter most are 25,000 deep verifications a month and lists of up to 25,000 emails on Pro, compared with 750 deep verifications and lists of up to 150 emails on Free. This guide maps every ceiling, works through the arithmetic for real list sizes, and shows how to run a cleanup without hitting a cap halfway through.
Quick answer
- "Unlimited" usually refers to standard checks. Unlimited Verifier includes unlimited standard verification on every plan, Free included, with no per-email fees.
- Deep verifications are usually the binding cap. Pro includes 25,000 a month and Free includes 750. A 500,000-row list where every row needed a deep check would take 20 months of Pro allowance.
- Lists and API volume have separate ceilings. Free allows 25 lists a month of up to 150 emails each. Pro allows lists of up to 25,000 emails and 100,000 API emails a month.
- Plan around the caps. Run standard checks on everything, send only uncertain addresses to deep checks, and export results before the retention window closes (24 hours on Free, 30 days on Pro).
What does "fair use" mean on an unlimited verification plan?
Fair use is a vendor's way of saying "unlimited within reasonable use." It shows up in four places:
- Metered allowances, such as a monthly count of deep checks.
- Size limits per upload, per list or per API request.
- Acceptable-use terms, which vary by vendor and often cover topics such as reselling access or automated bulk use.
- Throughput controls, meaning how quickly a service lets you submit checks.
The first two are numbers you can plan around. The last two live in contract language, so read them before a large project. For Unlimited Verifier, the published plan facts define the first two. Check the current terms for the rest.
When you compare best email verification tools, the word "unlimited" tells you less than the metered allowances do. Two vendors can both advertise unlimited checks and still differ widely in how many deep checks their plans include.
Bottom line: Treat "unlimited" as a claim about one check type, and read the metered limits for everything else.
Which limits does Unlimited Verifier publish?
The table below combines the plan facts for Free and Pro.
| Limit | Free ($0) | Pro ($29/month, or $25/month billed annually) |
|---|---|---|
| Standard verification | Unlimited, no per-email fee | Unlimited, no per-email fee |
| Deep verifications | 750 a month | 25,000 a month |
| Lists per month | 25 | Unlimited |
| Emails per list | Up to 150 | Up to 25,000 |
| API access | Not included | 100,000 emails a month |
| Bulk API request | Not included | Up to 10,000 emails per request |
| Result retention | 24 hours | 30 days |
Upload files are CSV or Excel up to 10MB, with the email column detected automatically. Exports come as CSV, Excel or JSON.
Two numbers carry most of the planning: the 25,000 deep verifications and the 25,000-email list size. They gate different things. The deep allowance limits how many checks you run in a month, and the list size limits how many rows one file can hold.
The 10MB cap is a third limit that people overlook. At 25,000 rows, 10MB works out to roughly 400 bytes per row. An email-only file sits far below that, but a CRM export with 40 columns can exceed 10MB well before it reaches 25,000 rows. Check file size as well as row count.
The plan facts don't say which checks run in standard mode and which run in deep mode. Confirm that before you design a workflow around it. If you automate checks, the email verification API and automation pattern you choose determines how quickly you use these allowances.
Bottom line: Plan around three ceilings: deep checks per month, emails per list, and file size.
Why are deep checks capped when standard checks are not?
Standard checks such as syntax and domain or MX lookups are lightweight. A deep check adds a live SMTP mailbox test, in which the verifier talks to the recipient's mail server and asks whether it will accept mail for that address. The protocol is defined in RFC 5321.
The reasoning below is our reading of how SMTP verification works. It is not a statement from Unlimited Verifier about its own costs.
- The live exchange takes real time on both sides. It costs more than a DNS lookup.
- Mail servers limit clients that probe too often. A verifier that pushes too hard can have its sending IPs throttled, which degrades results for everyone using it.
Those two factors explain why a vendor might meter the most expensive check while leaving lightweight checks open.
Catch-all domains are where the mailbox test is least conclusive. A catch-all server accepts mail for any address at its domain, so the test can't confirm whether a specific person's mailbox exists. Unlimited Verifier detects catch-all domains. Decide your policy for those addresses before you spend allowance on them. The catch-all email verification page explains how these results are handled.
Bottom line: The deep allowance caps the most expensive check, and catch-all domains are where that check is least conclusive.
How do you calculate whether a list fits the limits?
Use three formulas:
- Files needed = rows ÷ list size, rounded up.
- Deep checks needed = the number of addresses that need a deep check.
- Months of deep allowance = deep checks ÷ monthly allowance, rounded up.
Always round up. A fraction of a month still counts as a month.
Worked example 1: a 500,000-row list on Pro
- Files: 500,000 ÷ 25,000 = 20 files. Pro has no monthly list cap, so all 20 can run.
- Standard checks on all 500,000 rows are included, with no per-email fee.
- Deep checks on every row: 500,000 ÷ 25,000 = 20 months. That is the wrong plan.
- Assume the standard pass flags 31,500 addresses that need a deep check (an illustrative figure, not a benchmark).
- 31,500 ÷ 25,000 = 1.26, rounded up to 2 months.
- Month 1 uses 25,000 deep checks. Month 2 uses 6,500, leaving 18,500 unused.
- Cost: 2 months at $29 is $58 on monthly billing, or $50 on annual billing ($25 × 2).
Worked example 2: a 5,000-row list on Free
- Files: 5,000 ÷ 150 = 33.3, rounded up to 34 files.
- Free allows 25 lists a month, so one month covers at most 25 × 150 = 3,750 emails.
- The remaining 1,250 rows wait for next month's allowance.
- Deep checks on Free are capped at 750 a month, so a full deep pass on 3,750 emails wouldn't fit in one month either.
- On Pro, the same 5,000 rows fit in one file, with no monthly list cap.
Worked example 3: signup checks and a backfill through the API
- Assume a form adds 8,000 new addresses a month (illustrative). That is 8,000 ÷ 100,000 = 8% of the monthly API allowance, leaving 92,000 of headroom.
- A one-time backfill of 25,000 addresses needs 25,000 ÷ 10,000 = 2.5, rounded up to 3 bulk requests at the 10,000-per-request cap.
- API access is a Pro feature, so Free users can't run this workflow.
Bottom line: Run the formulas before you upload anything. The deep-check count usually sets the timeline.
How should you triage a list so deep checks fit the allowance?
Spend deep checks only where the answer would change what you do. If you would mail an address whatever the result, a deep check wastes allowance.
| Segment | First pass | Deep check? | Why |
|---|---|---|---|
| Engaged in the last 90 days | Standard | Usually no | Low risk, and you would mail it anyway |
| Never engaged, imported 2+ years ago | Standard, then deep | Yes | Higher bounce and spam-trap risk |
| Catch-all domain results | Standard | Only if you must mail them | The mailbox test may stay inconclusive |
| Role addresses (info@, sales@) | Flag | Usually no; hold them back | Often lower engagement and higher complaint risk |
| Disposable domains | Flag | No; remove them | Little value on a sending list |
| Previous hard bounces | Suppress | No | Already failed; don't pay to re-check them |
The last row saves the most allowance. Addresses that already hard-bounced don't need a fresh deep check. Suppress them and spend your monthly allowance on the uncertain middle.
Verification supports email verification compliance and hygiene, but it can't prove consent. Keep your opt-in records alongside your verification results.
Bottom line: Deep checks belong where the result changes your action.
Can you split a list to fit the per-list cap?
Yes, for lists you own. Splitting a 60,000-row list into 25,000 + 25,000 + 10,000 is a routine workflow for large databases.
Splitting becomes a problem when it's used to stretch the monthly allowance. Re-running the same addresses in new files consumes allowance without adding information. Keep one master file with a status column and a verification date, and send only new or changed addresses back through checks.
Split by file, not by account. Spreading one list across several accounts to get around a cap can run against acceptable-use terms, and it is the kind of pattern vendors review when they look at fair use.
Bottom line: Split files for size, never for quota.
What does verification cost per 1,000 addresses under these limits?
Before you compare email verification pricing across vendors, convert each plan into a cost per 1,000 checks at the volume you actually run. For Pro, using only the plan facts:
- Monthly billing, full deep allowance: $29 ÷ 25 = $1.16 per 1,000 deep checks.
- Annual billing, full deep allowance: $25 ÷ 25 = $1.00 per 1,000 deep checks.
- Monthly billing, 7,000 deep checks used: $29 ÷ 7 = $4.14 per 1,000 deep checks.
Standard checks add nothing to that total, because they carry no per-email fee.
Low utilization raises the effective price, so idle allowance is the real cost driver. The plan facts don't say whether unused deep checks roll over, so confirm that before you plan a light month. What happens to unused credits explains how allowances are typically treated and what to ask. The annual versus monthly billing comparison shows when the annual rate pays off. For context, see the 2026 price breakdown and the 500,000-email cost walkthrough. Our full email verification cost guide covers the complete picture.
Bottom line: At full use, Pro works out to $1.00–$1.16 per 1,000 deep checks, and idle allowance pushes that number up.
What happens when you hit a limit mid-project?
The plan facts don't describe overage charges, so don't plan on any. Ask before a large run whether a job can exceed the monthly allowance and what happens if it does.
If you reach a limit partway through, you have four options:
- Keep running standard checks, which aren't metered, and hold deep checks for the next period.
- Wait for the monthly reset. Confirm the reset date in your account before you set a deadline.
- Move from Free to Pro if you keep hitting the 25-list or 150-email ceilings.
- Use the API for new addresses as they arrive, while bulk uploads handle the historical database.
Whether unknown results consume allowance is a separate question. Do email verifiers charge for unknown results covers what to check, but confirm the answer against your own plan's terms. While you wait, the free email checker lets you spot-check single addresses.
Bottom line: Schedule deep checks against the monthly allowance, and treat overage as unknown until you've confirmed it.
How do you run a capped cleanup? A step-by-step tutorial
Follow these steps in order. They're written for someone running their first large verification.
- Export your list as CSV. From your ESP or CRM, export the email column plus any engagement fields, such as last open or signup date. Save an untouched copy of the original.
- Remove known failures first. Pull your hard bounce, unsubscribe and complaint suppressions and remove them. Record the row count after this step. It's your baseline.
- Normalise and deduplicate. Trim whitespace, lowercase the addresses and remove duplicates. Duplicates cost allowance every time they're checked.
- Check size against all three limits. Count rows and file size. Split the file if it exceeds 25,000 rows on Pro, 150 rows on Free, or 10MB. Repeat the header row in every file.
- Run a small test first. Create a free account and upload a 150-row sample from your own list. This shows how your data sorts before you pay for Pro.
- Upload each split file. Open the upload page and upload each file. Confirm the email column was detected correctly.
- Record the buckets. Note the Valid, Risky and Invalid totals for each file. The Risky count is your candidate deep-check queue.
- Apply the three formulas. Calculate how many months of deep allowance the Risky queue needs. Rank those rows by engagement, most engaged first, and spread them across the months.
- Export before retention ends. Save each result as CSV, Excel or JSON. Results are kept 24 hours on Free and 30 days on Pro, so export the same day.
- Re-import and suppress. There are no native ESP, CRM or Zapier integrations, so re-import Valid contacts by CSV or push them through your own API script. Add Invalid addresses to your suppression list.
Bottom line: Shrink the list before upload, check every file against all three limits, and export results on the day you get them.
Which plan fits which workload?
| Workload | Volume | Free | Pro | What to watch |
|---|---|---|---|---|
| One-off check of a small list | 2,000 rows | Yes: 14 files, within 25 monthly lists | Yes: one file | Free's list count and 150-row cap |
| Monthly newsletter list | 40,000 rows | No: 3,750 emails a month at most | Yes: two files | Deep checks counted per month |
| Quarterly cleanup | 500,000 rows | No | Yes: 20 files | Deep allowance sets the timeline |
| Signup checks | ~8,000 a month | No API access | Yes: within 100,000 API emails | Bulk requests cap at 10,000 |
| Single address spot-check | 1 address | Yes, with the free checker | Yes | Single checks are a separate workflow |
Teams in email verification for ecommerce and SaaS often run several of these jobs side by side: a signup check through the email verification API, a periodic bulk cleanup and occasional spot-checks. For real-time checks at the form, the real-time validation at signup article covers the workflow.
For bulk cleanups, Pro is the plan that fits: 25,000-email files, a 25,000-address deep allowance and API access. Free works best as a sandbox for learning your list's mix before you pay.
Bottom line: Match the plan to your largest workload, whether that's a monthly send, a quarterly cleanup or a signup stream.
Which questions should you ask before a large run?
Fair use terms are easiest to manage when you know the answers in advance. The table shows what the published plan facts cover and what to ask.
| Question | Why it matters | Covered by the published plan facts? |
|---|---|---|
| Which checks count against the deep allowance? | Determines whether a standard pass costs anything | Partly: standard checks are unlimited, but the mode split isn't itemised |
| Do unknown or timed-out results use up a deep check? | Can quietly drain allowance | No |
| Does unused allowance roll over? | Decides whether light months are wasted | No |
| What happens past the monthly allowance? | Sets your overage risk | No overage is described |
| What are the file-size and request limits? | Sets how many files you need | Yes: 10MB per file, 25,000 rows per list, 10,000 per API request |
| How long are results kept? | Sets your export deadline | Yes: 24 hours on Free, 30 days on Pro |
If you're comparing against per-email vendors, one competitor's pricing logic is worth reading alongside this. The how to choose an email verifier guide lists more questions to put to any vendor.
Bottom line: Ask the questions the plan facts don't answer before you upload, not after the first capped run.
What mistakes do people make with fair use limits?
- Assuming "unlimited" covers deep checks. Standard checks are unlimited on Unlimited Verifier. Deep checks are metered.
- Running deep checks on the whole list. Most rows don't change your action, so a full deep pass spends allowance on answers you won't use.
- Spending allowance on known hard bounces. Suppress them before upload.
- Splitting on the wrong unit. On Free, the limits are 150 rows per list and 25 lists per month. On Pro, the limit is 25,000 rows per list. The 10MB file cap applies to both.
- Ignoring file size. A wide CRM export can hit 10MB before it reaches 25,000 rows.
- Losing results to the retention window. Free results last 24 hours and Pro results last 30 days. Export on the day.
- Treating catch-all results as settled. A catch-all domain can't confirm a specific mailbox, so decide your policy before you run the list.
- Mailing Risky addresses to meet a deadline. Uncertain addresses can raise bounces, which hurts deliverability.
- Re-verifying the whole list every month. Keep a master file and check only what has changed.
Bounce and reputation risk are covered in whether verification lowers your ESP bill and the cost of skipping verification. Mailbox providers set their own expectations for bulk senders, which are summarised in Google's email sender guidelines.
Bottom line: Most fair use problems come from mixing up units: rows versus lists, file size versus row count, and standard versus deep checks.
How we compared (and limitations)
This guide is based on public documentation and Unlimited Verifier's published plan facts. We haven't run controlled tests of how the caps behave under load, and this guide doesn't compare other vendors' fair use terms, which change often and are best read directly.
- The 99.5% accuracy figure is the company's stated number for deep verification, not an independent benchmark.
- The worked examples are illustrative. The 31,500-address deep-check queue and the 8,000 monthly signups are hypothetical.
- The reasoning about why deep checks are metered reflects how SMTP verification works in general. It is not a statement about the company's costs.
- Plan terms, prices and retention windows can change. Check the current pricing and terms before a large project.
- Background on SMTP behavior comes from RFC 5321, and sending rules come from the FTC's CAN-SPAM compliance guide.
Deep check budget for a 500,000-row list
| Scenario | Deep checks needed | Pro monthly allowance | Months needed |
|---|---|---|---|
| Every row deep-checked | 500,000 | 25,000 | 20 |
| Standard check first, 5% uncertain | 25,000 | 25,000 | 1 |
Frequently asked questions
What is fair use in email verification?
Fair use is a vendor's term for unlimited use within reasonable limits. It usually appears as monthly caps on deep checks, per-upload list sizes, API volume, acceptable-use rules and throughput controls. Check the vendor's published plan facts and terms for the exact numbers.
Does unlimited email verification really mean unlimited?
Not always. Unlimited often refers only to standard checks. Deep verifications, list sizes and API volume can have separate ceilings. Read each plan's metered limits before assuming the word unlimited covers everything.
How many deep verifications does Unlimited Verifier Pro include?
Pro includes 25,000 deep verifications a month, according to Unlimited Verifier's published plan facts. Standard verification is unlimited with no per-email fee on that plan.
What is the list size limit on the Free plan?
The Free plan allows lists of up to 150 emails each and 25 lists per month. Pro raises the per-list limit to 25,000 emails.
What happens to results after the retention window?
Results are deleted after the retention period. Per the published facts, that is 24 hours on Free and 30 days on Pro. Export your CSV, Excel or JSON files before the window closes.
How do I run a large cleanup without hitting deep check caps?
Run standard verification on the full list first. Then send only uncertain or risky addresses to deep checks. This keeps deep check usage well below the monthly allowance.
Can I split a large list to fit list size limits?
Yes. If a file exceeds the per-list cap, split it into smaller files that each fit the limit, then process them in sequence. Track the total deep checks used across files.
Is there a file size limit for uploads?
Uploads are CSV or Excel files up to 10MB, with the email column detected automatically. At 25,000 rows, file size can become the constraint, so check your file size before uploading.
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.