Article
What Does Unlimited Really Mean in Email Verification?
By Unlimited Verifier Team ·

Summary
In email verification, "unlimited" usually means standard checks carry no per-email fee, while lists, deep checks, API volume and result retention stay capped. Read the plan limits, not the headline, to know what you can actually verify each month.In email verification, "unlimited" usually means standard checks carry no per-email fee, but lists, deep checks, API calls and result storage stay limited. At Unlimited Verifier, standard verification is unlimited on every plan, including Free, while deep verifications are capped at 750 a month on Free and 25,000 on Pro. This guide explains each limit, shows the arithmetic for a real list, and gives you a way to test any vendor's "unlimited" claim before you pay. For the wider cost picture, start with our email verification cost guide.
Quick answer
- Standard checks are unlimited. On every plan, including Free, standard verification has no per-email fee.
- Other limits still apply. Free allows 25 lists a month of up to 150 emails each, plus 750 deep verifications. Pro allows lists of up to 25,000 emails, 25,000 deep verifications and 100,000 API emails a month.
- Four numbers matter more than the word. Check emails per list, deep checks per month, API volume and result retention (24 hours on Free, 30 days on Pro).
- A 180,000-row list fits on Pro as eight uploads for about $29 for the month.
- Ask for the caps in writing. A claim of "unlimited" says nothing about the limit that will slow you down.
What does "unlimited" actually cover?
"Unlimited" describes the cost of a check, not every resource behind it. A verification service has at least five resources that can be capped: checks per month, list or file size, API calls, result storage and deep (premium) checks. A vendor can waive the fee on one of these and still cap the others.
| Resource | What "unlimited" usually promises | Where the cap usually hides |
|---|---|---|
| Cost per check | No per-email fee | A subscription tier is the real constraint |
| Emails per list or file | Unlimited lists | Each upload has a row or file-size ceiling |
| Deep or premium checks | Standard checks at no extra cost | Deep checks are metered by month |
| API calls | Unlimited integration use | Monthly API volume or batch size is capped |
| Result retention | Results available when you need them | Downloads may expire within hours or days |
Bottom line: "Unlimited" usually removes the per-email fee and leaves at least one other resource capped.
Why do vendors define "unlimited" so differently?
It helps to think of verification as three cost layers: DNS lookups (domain and MX), mailbox-level checks, and the infrastructure and support behind them. Vendors choose which layer to waive. The mailbox-level check is typically the hardest to offer without limits, because it depends on remote servers. RFC 5321 defines the RCPT TO exchange a sending server uses to ask whether a recipient is accepted. Many servers accept every recipient at that stage, or throttle repeated probes, which is why catch-all domains come back ambiguous. A vendor that meters mailbox checks is often responding to that reality.
The practical result is that "unlimited" is largely a marketing term. The same word can cover very different workloads. The table below shows four models that get called unlimited.
| Pricing model | What is really metered | What to check before you buy |
|---|---|---|
| Flat subscription, unlimited standard checks | Deep checks per month, per-list size, retention | Whether deep checks are counted per row or per file |
| Pay-per-check credits | Every check, including the ones that return unknown | Whether unknown or timed-out results still use a credit (see whether verifiers charge for unknown results) |
| Prepaid bundle with an expiry date | Volume and time | How unused credits are handled at renewal |
| Enterprise contract with a "fair use" clause | An undefined threshold | The exact number, in writing |
Comparing email verification pricing across these models only works when you convert everything to the same unit. Headline prices hide the caps.
Bottom line: Vendors waive different costs, so read the caps before you compare headline prices.
What are Unlimited Verifier's actual limits?
Standard verification is unlimited on both plans. The other limits are published as follows.
| Feature | Free ($0) | Pro ($29/month, or $25/month billed annually) |
|---|---|---|
| Standard verification | Unlimited, no per-email fee | Unlimited, no per-email fee |
| Lists per month | 25 | Unlimited |
| Emails per list | Up to 150 | Up to 25,000 |
| Deep verifications per month | 750 | 25,000 |
| API access | Not included | 100,000 emails a month |
| Results kept | 24 hours | 30 days |
| File format and size | CSV or Excel, up to 10MB | CSV or Excel, up to 10MB |
Three rows change the arithmetic more than the rest:
- Emails per list. This is the binding constraint for most real databases. A larger list needs multiple uploads.
- File size. The 10MB cap is roughly 10 million bytes. At 25,000 rows, each row must average about 400 bytes. An email address plus a name and a source tag fits easily. A wide export with dozens of columns may not, so trim exports before upload.
- Retention. On Free, results disappear after 24 hours, so export the same day. On Pro, the 30-day window lets you use results in a campaign or a compliance review.
Bottom line: For most lists, the per-list cap and the 10MB file limit bind before the monthly totals do.
Which kind of unlimited do you need?
The right plan depends on which limit your workload hits first.
| Your situation | Binding limit | Fit |
|---|---|---|
| Occasional checks, up to 3,750 emails a month | Free: 25 lists × 150 emails | Free covers it |
| Testing your file format before paying | Free: 150 rows per list | Free, on a small sample |
| One-time cleanup of 20,000 to 500,000 contacts | Per-list size, then deep checks | Pro, split into uploads |
| Checking signups as they arrive | API volume and batch size | Pro, via the email verification API (see real-time validation at signup) |
| Monthly re-verification by an ecommerce or SaaS team | Per-list size, plus deep checks each cycle | Pro |
| Weekly re-verification of a 10,000-row list | Per-list size on Free | Pro |
Pro also suits teams that want to automate bulk jobs through the API rather than manual uploads.
Bottom line: Free suits small, occasional checks. Anything at list scale needs Pro, and the planning question becomes how to spend the 25,000 deep checks.
How much does it cost to verify 180,000 contacts on Pro?
A B2B SaaS company has 180,000 contacts across a CRM export, a webinar archive and an old newsletter list. It wants everything verified before a re-engagement send.
Step 1: Split the list. Pro allows 25,000 emails per list.
180,000 ÷ 25,000 = 7.2, so 7 full lists of 25,000 (175,000 rows) plus one of 5,000 = 8 uploads.
Step 2: Check the file size. At 25,000 rows, each row must stay under about 400 bytes. An email, a name and a source tag is usually far below that.
Step 3: Count the standard checks. Standard verification is unlimited on Pro, so all 180,000 addresses get a standard check with no per-email cost.
Step 4: Plan the deep checks. The published allowance is 25,000 deep verifications a month. Confirm on the upload page how a deep check is applied to each file before you run the largest job. If you can run one file deep, the allowance covers a full 25,000-row file, so put the riskiest file there: the oldest webinar leads and addresses that bounced before.
Step 5: Cost. One month of Pro at $29 covers the job. Billed annually, the same month costs $25.
Step 6: Divide by usable output. Suppose 120,000 of the 180,000 rows come back Valid. That split is illustrative, not a benchmark. Then:
$29 ÷ 120 = $0.24 per 1,000 valid addresses on monthly billing $25 ÷ 120 = $0.21 per 1,000 valid addresses on annual billing
This is the number that matters for planning, because you pay for every row you check but only send to the Valid ones. The cost of not verifying your list is the comparison to make against it.
On Free, the same database would need:
180,000 ÷ 3,750 (25 lists × 150 emails) = 48 months, with only 750 deep checks
Bottom line: The 180,000-row job is eight uploads and one month of Pro, provided each file stays under the 10MB limit.
How do you test an "unlimited" claim in 15 minutes?
You can check any vendor's claim, including ours, against its published plan details and your own file sizes.
- Find your largest file's row count. Use the biggest file, not the average. The per-list cap hits that file first.
- Find the per-list cap. Look for the maximum emails per file or per job. If the page says only "unlimited," ask in writing.
- Find the deep-check allowance. Note whether premium checks are metered separately and how many you get each month.
- Find the API volume and batch size. Divide your monthly API needs by the monthly cap, then check the maximum emails per request.
- Find the retention window. A 24-hour window means same-day exports. A 30-day window allows a review cycle.
- Run the arithmetic on your largest file. Divide rows by the per-list cap, then compare the number of uploads and the total cost with your budget.
If a vendor cannot answer steps 2 to 5 in one sentence each, treat its "unlimited" as a marketing term. Our buyer's checklist for choosing a verifier covers the rest of the evaluation.
Bottom line: Four caps decide whether "unlimited" fits your workload, and you can find all of them on a pricing page.
How do you verify a list bigger than your plan's per-list cap?
This walkthrough uses Pro's 25,000-row lists. Free follows the same steps at 150 rows.
- Sign up for a free account. Start on Free to confirm your file format before you commit to a paid plan.
- Export your contacts as a CSV. Keep the email column and one or two fields you need for segmentation, such as last open date. This keeps each row within the 400-byte budget.
- Split the export. For 180,000 rows, create eight files: seven of 25,000 rows and one of 5,000. Put the header row in each file.
- Upload and verify a list. CSV and Excel files up to 10MB are accepted, and the email column is detected automatically. Start with the highest-risk file.
- Read the three buckets. Valid addresses are safe for your main sends. Invalid addresses should be removed and suppressed. Risky addresses include catch-all domains, disposable addresses and role accounts. For a closer look at catch-all results, see catch-all email verification.
- Export each file the same day. Save CSV, Excel or JSON copies, since Pro keeps results for 30 days.
- Keep a deep-check tally. Record how many of the 25,000 monthly deep checks each file uses, so the final files are not left without the depth you planned.
- Re-import the Valid contacts. There are no native ESP, CRM or Zapier integrations, so this is a manual upload or an API call from your own scripts (see API and automation patterns). Add Invalid contacts to your suppression list.
Bottom line: Eight files, same-day exports and a deep-check tally turn a 180,000-row job into a routine task.
What does "unlimited" really cost per 1,000 emails?
When standard checks are unlimited, the cost is the subscription. Here is the pricing as published:
- Free: $0, with 750 deep verifications a month and unlimited standard checks.
- Pro, monthly: $29 a month, or $348 over 12 months.
- Pro, annual: $25 a month, or $300 a year. That saves $48 a year.
If you use all 25,000 deep verifications in a month, the subscription works out to:
$29 ÷ 25 = $1.16 per 1,000 deep checks on monthly billing $25 ÷ 25 = $1.00 per 1,000 deep checks on annual billing
If you use only 5,000 deep checks, the same $29 becomes $5.80 per 1,000. That gap is why your monthly volume matters more than the subscription price. For broader comparisons, see what email verification costs in 2026, annual versus monthly billing and verifiers under $30 a month. For a 500,000-email job, see the cost of verifying 500,000 emails. Whether the savings reach your ESP bill is covered in whether verifying emails lowers your ESP bill.
Some vendors charge per check or per credit, so their total depends on volume. Our article on why some verifiers are priced so high explains that model in more detail.
Bottom line: At full use, Pro's deep checks cost about $1.00 to $1.16 per 1,000, while standard checks add nothing per email.
What mistakes do people make with unlimited plans?
- Assuming unlimited lists means unlimited size. Pro allows unlimited lists, but each list tops out at 25,000 emails. A 60,000-row file needs three uploads.
- Exporting on Free after 24 hours. A Friday run can be gone by Monday. Export the same day.
- Spending the deep checks on the first file. Rank files by risk before you start, and track the tally as you go.
- Sending an oversized file. A file over 10MB will exceed the upload limit even under 25,000 rows. Trim columns first.
- Expecting native integrations. There are no native ESP, CRM or Zapier connections. Build the export, verify and re-import steps into your routine, or use the API.
- Planning automation on Free. API access is part of Pro.
- Treating a valid result as permission. A valid address can receive mail. That does not mean the person agreed to get it. The next section covers this in detail.
Bottom line: Most surprises come from a cap you did not check, not from the price.
Does verification replace consent?
No. Verification checks whether an address is syntactically valid, has a working domain and MX records, and, where a mailbox can be tested, appears to accept mail. It does not show that the person opted in.
Consent rules come from law and from mailbox providers. In the US, the FTC's CAN-SPAM compliance guide sets the baseline for commercial email. Google's sender guidelines recommend keeping the spam rate below 0.10% and avoiding 0.30% or higher. Some guides cite 0.3% as a limit, so we recommend the stricter 0.10% as your working target. M3AAWG publishes sending best practices that include list hygiene. Verification helps by removing addresses that bounce or trap mail, which is part of email verification compliance and hygiene. It does not replace permission.
Bottom line: Use verification to remove bad addresses, then confirm that you had permission to email the rest.
How we compared (and limitations)
This article is based on public documentation and the plan details Unlimited Verifier publishes. We have not run head-to-head tests of competitors' caps, and we have not compared every entry in our best email verification tools roundup for this topic. Plan terms change, so check the current pricing page before you buy. The arithmetic uses the published limits: 25 lists of 150 emails on Free; 25,000 emails per list, 25,000 deep checks and 100,000 API emails a month on Pro; and a 10MB file cap. The worked examples, including the 120,000 Valid split, are illustrative and are not customer data.
Unlimited Verifier states 99.5% accuracy for deep verification. That is the company's own figure, not an independent benchmark. Mailbox-level results can vary for catch-all domains, disposable addresses and servers that rate-limit checks, which is why Risky results are held back in the tutorial.
When you're ready to test the caps on your own data, create a free account, run a small sample through the free email checker, and compare the results with the limits above.
Bottom line: The word "unlimited" is only as useful as the caps behind it, and those are published in the plan details.
Upload math for a 180,000-row list
Step 1: Confirm the per-list maximum on the plan (25,000 emails on Pro). Step 2: Divide the list size: 180,000 / 25,000 = 7.2. Step 3: Round up to 8 uploads. Step 4: Check that deep checks used stay under the 25,000 monthly allowance. Step 5: Download results within the 30-day retention window.
| Step | Value |
|---|---|
| List rows | 180,000 |
| Per-list max | 25,000 |
| Uploads needed | 8 |
| Deep checks cap | 25,000/month |
Frequently asked questions
Is unlimited email verification really free?
Usually not entirely. Unlimited normally means no per-email fee for standard checks, but you still pay a subscription, and features like deep checks, large lists or API access may be capped or priced by tier. Check the plan page for each resource.
What is a deep email verification?
A deep verification is a more thorough check, typically involving mailbox-level probing and catch-all analysis, beyond basic syntax and DNS checks. Vendors often meter it monthly because it is more expensive to run than a standard check.
How do I calculate how many uploads a large list needs?
Divide your total rows by the per-list maximum. For example, a 180,000-row list on a plan allowing 25,000 emails per list needs eight uploads. Multiply by your plan's upload rules to confirm it fits your monthly allowance.
Why does result retention matter?
If results expire, you must download and store them before the window closes or re-run the check, which costs time and possibly credits. Retention periods vary by plan, so confirm them before relying on a platform for ongoing campaigns.
Do catch-all domains affect verification counts?
They can. Catch-all servers accept every address at the probing stage, so the result is ambiguous and may require a deep check. That can consume your monthly deep-verification allowance faster than standard checks would.
What should I ask a vendor about unlimited claims?
Ask in writing for limits on emails per list, deep checks per month, API calls and batch size, and result retention. Also ask whether deep checks are counted per row or per file, and what happens when a cap is reached.
Does unlimited mean I can verify the same list repeatedly?
Not necessarily. Re-verifying a list may count against list, row or API limits again, and results may expire. Confirm whether repeat checks are billed or capped before scheduling recurring verification.
How can I test an unlimited claim before paying?
Run a small sample that mirrors your real list, including catch-all domains, then compare your usage against the published caps. Use the free tier to confirm limits match the documentation before committing to a paid plan.
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.