Article
Is MillionVerifier Legit? How to Check Its Company, Data Terms and Accuracy
By Unlimited Verifier Team ·

Summary
MillionVerifier is a real, operating bulk email verification service, but legitimacy is only one check. Confirm who runs the company and what its data terms say, then test accuracy on a labelled 500-address sample before relying on its results.MillionVerifier is a real, operating bulk email verification service, but legitimacy is only one of three checks: confirm who runs it and what its data terms say, then test its accuracy on a labelled 500-address sample before you trust a single result.
This article does not independently verify MillionVerifier's company registration, ownership or customer reviews, so the checklists below show you how to close that gap yourself.
Quick answer
- Operating service, as far as public information shows. We did not verify company registration or ownership for this article, so check those yourself.
- Legitimacy is not accuracy. A real vendor can still mislabel addresses. Test a labelled 500-address sample before you commit.
- Set a pass line. For a list you mail regularly, treat more than 2% of known-bad addresses marked valid as a failure. This is our recommendation, not an industry standard.
- Get data and billing terms in writing. Ask for a data processing agreement, a retention period, renewal terms and credit rules before uploading anything.
- Use published terms as a benchmark. Unlimited Verifier's Pro plan is $29/month, or $25/month billed annually, and standard verification is unlimited on every plan, including Free. Treat this as a reference point, not a verdict on MillionVerifier.
Is MillionVerifier a legitimate company or a scam?
Legitimacy means the company exists, runs the service it advertises, and handles your data and payments the way its terms say. Fraudulent or low-quality verification services tend to share a few warning signs: hidden operators, no privacy policy, prices visible only after payment, and promises of perfect accuracy. None of these settles the question for one vendor, so check each one.
| Signal | What a legitimate vendor shows | Red flag |
|---|---|---|
| Operator identity | Named company, business address, a support contact that replies | Web form only, no address, anonymous team |
| Privacy and data terms | Published privacy policy, data processing terms, retention statement | No policy, or wording that allows sharing with "partners" |
| Pricing | Per-unit prices visible before signup, clear credit and quota rules | Price shown only after payment; unclear expiry |
| Result definitions | Written meaning for each result label | "100% accurate" with no definitions |
| Cancellation and renewal | Documented cancellation and renewal terms | Renewal you cannot find or cancel easily |
| Technical docs | API reference, error codes, rate limits | Missing or vague documentation |
To check ownership, look up the operating company in the business registry of the country it names (for example, Companies House for UK-registered firms), then compare the name and address with the vendor's website and terms. Reviews can show that people use a product, but they don't audit the company or prove that each review is genuine.
Bottom line: Use the checklist to confirm the business is real. Legitimacy tells you the company is functioning, not that its labels are right.
What does an email verifier like MillionVerifier actually check?
Verification runs in layers, and each layer rules out a different kind of bad address. Syntax and domain checks are largely deterministic. The mailbox probe is probabilistic, and most accuracy disputes come from that layer.
- Syntax. Is the address well formed? This catches errors such as
name@gmial,com. - Domain and MX. Does the domain exist and publish mail exchange (MX) records? A domain with no MX record usually cannot receive mail.
- SMTP mailbox probe. The verifier opens a conversation with the receiving server and asks whether it accepts the recipient, without sending a message. Reply codes are defined in RFC 5321, and enhanced status codes in RFC 3463.
- Catch-all detection. Some domains accept mail for any address, so the probe says "yes" to everything. The verifier cannot confirm the individual mailbox. It can only flag the domain.
- Flags. Disposable domains, role accounts such as
info@orsales@, and other risk patterns.
Servers may greylist unfamiliar senders, rate-limit verification IPs, or give ambiguous answers. A careful verifier moves these cases into a "risky" or "unknown" bucket rather than guessing. When you evaluate any vendor, check how it treats catch-all and unknown results. A tool that labels every catch-all address valid is guessing, not verifying.
Verification also cannot show that someone consented, still reads mail, or is a spam trap. It supports email verification compliance and hygiene, but it does not replace opt-in records. The FTC's CAN-SPAM compliance guide covers the opt-out obligations that still apply to what you send.
Bottom line: Judge a verifier by how it labels the uncertain middle, not by how it handles the easy cases.
Is MillionVerifier accurate enough for your list?
Accuracy can only be judged against a labelled sample whose true status you already know. Published accuracy figures are usually measured on test sets the vendor chooses, so one vendor's "99%" may describe something quite different from another's. Treat any published figure, from MillionVerifier or anyone else, as a claim to test.
Three error types matter:
| Error type | What it costs you | Suggested tolerance (our recommendation) |
|---|---|---|
| False valid (bad address marked valid) | Bounces, and reputation damage from repeated bounces | Under 2% of known-bad addresses |
| False invalid (good address marked invalid) | Lost reach, partly recoverable with a re-check | Under 5% of known-good addresses |
| Risky inflation (too many addresses in the middle bucket) | Unresolved addresses you still have to decide on | Set a policy for the risky bucket before you run the list |
False valid is the expensive error. Google's sender guidelines set 0.3% as the spam-rate level bulk senders must stay below, and advise aiming well under it. Bounces are a separate metric, but both feed the same reputation system, and a verifier that passes dead addresses works against that goal.
Sample size matters too. A test set of 200 known-bad addresses is small. If the true miss rate is 2%, you would expect about 4 misses, and the 95% confidence interval runs from roughly 0.1% to 3.9%. A 200-address set can reveal a large problem, but it cannot reliably tell 1% from 3%. Use it as a go/no-go gate and retest with a larger set when the decision is close.
For comparison, Unlimited Verifier states 99.5% accuracy for its deep verification. That is the company's own figure, not an independent benchmark, so check it the same way you would check any other.
Bottom line: Accuracy only counts when you measure it on your own labelled sample, and the false-valid rate matters most.
How do you test MillionVerifier on your own list?
This afternoon test works for any verifier, so reuse it when comparing the best email verification tools.
- Build a labelled sample of 500 addresses. Take 300 known-good addresses (they replied, purchased or logged in within the last 90 days) and 200 known-bad addresses (they hard-bounced in your last two sends and you have not mailed them since). Keep the labels in a separate file.
- Strip the labels. Create an upload file with only the email column. If the verifier sees your labels, you are not testing the tool.
- Run the same file through each tool. Use MillionVerifier's own upload or API, following its documentation, then repeat with a second tool. To run the sample through Unlimited Verifier, sign up and upload the sample. Free accepts 150 emails per list, so 500 addresses need four lists (150, 150, 150 and 50), well within the 25-list monthly cap.
- Download results immediately. Free results are kept for 24 hours and Pro results for 30 days, so export each run as CSV the moment it finishes.
- Merge results with your labels. Use XLOOKUP or VLOOKUP on the email column. Lowercase and trim both sides first, or capitalisation differences will look like mismatches.
- Build the confusion grid. Count four cells: known-good marked valid, known-good not valid, known-bad marked valid, known-bad not valid.
- Calculate both rates. False valid = known-bad marked valid ÷ 200. False invalid = known-good not valid ÷ 300.
- Note the risky count separately. Risky is not a failure, but a tool that places most of your list there has given you little to act on.
- Apply the pass line. If false valid is above 2%, don't use the tool for re-entry sends or for mailing aged addresses.
Bottom line: A labelled 500-address test takes an afternoon and tells you more than any review, including this one.
What does a failed 500-address test look like?
The figures below are hypothetical and exist to show the arithmetic.
- Known-good (300): 287 marked valid and 13 not valid. False invalid = 13 ÷ 300 = 4.3%. This is inside the 5% tolerance.
- Known-bad (200): 9 marked valid and 191 not valid. False valid = 9 ÷ 200 = 4.5%. This fails the 2% line.
With 9 misses out of 200, the 95% interval runs from about 1.6% to 7.4%. That interval includes 2%, so the result is not conclusive. It still fails on the point estimate, so retest with a larger known-bad set (1,000 addresses would narrow the interval considerably) before you trust the tool.
The risk is easy to size. Suppose a 40,000-contact list contains 3,200 invalid addresses (8%). At a 4.5% false-valid rate, about 144 of them (3,200 × 0.045) would be classed as valid and mailed. That is the exposure your sample is measuring.
Bottom line: A 4.5% false-valid rate is a real problem for re-entry sends, even if the false-invalid rate looks acceptable.
How does MillionVerifier pricing work, and what should you check?
Email verification pricing usually follows one of three models. Compare them on cost per clean address after re-checks, not on the headline rate.
| Model | How cost scales | What to check before buying |
|---|---|---|
| Pay-as-you-go credits | Emails × price per credit; re-checks and retries may also consume credits | Price per credit at your volume; whether credits expire; whether failed or ambiguous checks are charged |
| Monthly subscription | Fixed fee within plan caps | Monthly quota, per-list limits, overage rules, auto-renewal and cancellation steps |
| Free tier | A small monthly allowance | List-size limits, result retention, API access |
The hidden cost is re-verification. One pass over a list is cheap. Re-checking it every month is where per-credit pricing compounds. Ask each vendor how repeat runs are billed.
Unlimited Verifier's published plans are below:
| Plan | Price | Lists | Deep verifications | API | Results kept |
|---|---|---|---|---|---|
| Free | $0 | 25 lists a month, up to 150 emails each | 750 a month | Not included | 24 hours |
| Pro | $29/month, or $25/month billed annually | Unlimited lists, up to 25,000 emails each | 25,000 a month | 100,000 emails a month | 30 days |
Standard verification is unlimited on every plan, with no per-email fees. Deep verifications are a separate monthly quota. Pro includes API access, so teams running checks from their own scripts can use the API keys page and the email verification API and automation workflow.
Ask MillionVerifier the same questions in writing: whether it offers a free tier, whether renewals are automatic, how cancellation works and what its refund terms are. This article does not assume any refund policy for MillionVerifier.
Bottom line: Price by the cost of clean addresses after recurring checks, and get renewal, expiry and refund terms in writing before you buy.
What does a 40,000-contact list cost to keep verified?
Assume a 40,000-contact B2B list that you re-verify every month on Unlimited Verifier Pro.
- List caps. Pro allows up to 25,000 emails per list, so split the file into 25,000 + 15,000 (two lists).
- Standard verification. All 40,000 addresses are covered at no per-email cost, and that holds for each monthly re-run.
- Deep verification. Suppose 6,000 catch-all and risky addresses get deep verification each month. That uses 6,000 of the 25,000 allowance, leaving 19,000.
- Monthly cost. $29 on monthly billing, or $25 on annual billing ($300 a year).
- Subscription cost per 1,000 contacts. $29 ÷ 40 = $0.73 on monthly billing, or $25 ÷ 40 = $0.63 on annual billing.
To compare with a pay-as-you-go vendor, multiply 40,000 by its current price per verification, then add the cost of each monthly re-run. Use the price on its pricing page rather than a figure from a review, since prices change.
Bottom line: Compare vendors on the total cost of your recurring checks, not on a single per-1,000 rate.
Is it safe to upload my email list to a verifier?
An email list is personal data. Under the EU's GDPR, a service that processes personal data on your behalf is a processor, and Article 28 requires a written contract covering that processing. The same logic applies under the UK GDPR and similar regimes, whatever the vendor's reputation.
Get written answers to these five questions before you upload:
- Is there a data processing agreement, and can your legal team sign it?
- Where is data processed and stored, and who are the sub-processors?
- How long are uploads and results kept, and can you request deletion?
- Does the vendor use your list to build or enrich its own database? If so, can you opt out?
- What security controls apply, such as encryption in transit and restricted staff access?
As a benchmark, Unlimited Verifier states that results are kept for 24 hours on Free and 30 days on Pro. Ask MillionVerifier for its equivalent figures. Whatever the answers, download your Valid list and delete the rest once you have finished.
Bottom line: Retention and reuse are risks you can control. Get the answers in writing before any list leaves your systems.
How does MillionVerifier compare with other verifiers?
Compare vendors on the same labelled sample and the same published terms, not on their marketing pages. The table lists what to confirm on MillionVerifier's own site, next to Unlimited Verifier's published terms. We have not copied MillionVerifier's plan figures into it, because they may be out of date.
| Question | MillionVerifier (confirm on its site) | Unlimited Verifier (published) |
|---|---|---|
| Pricing model | Current model and price on its pricing page | $0 Free; $29/month or $25/month billed annually for Pro |
| Free allowance | Current limits, if any | 25 lists a month, up to 150 emails each, plus 750 deep verifications |
| Result labels | Documented definitions for each label | Valid, Risky, Invalid |
| Catch-all handling | How catch-all domains are labelled | Catch-all domains detected and flagged |
| API | Documentation, rate limits and error codes | REST API with API keys; single checks and batches up to 10,000 emails per request |
| Stated accuracy | Whether it publishes a figure, and how it was measured | 99.5% for deep verification (company figure) |
| Open-source component | Whether any engine is public | Verification engine published on GitHub |
| Results retention | Stated retention period | 24 hours (Free), 30 days (Pro) |
| Integrations | Whether it connects to your ESP or CRM | No native ESP, CRM or Zapier integrations; use CSV export and re-import, or the API |
For head-to-head breakdowns, read MillionVerifier vs NeverBounce and Debounce vs MillionVerifier. For the wider market, see email verifier alternatives. If a rival's accuracy claims need the same scrutiny, is NeverBounce accurate applies the same testing logic.
Bottom line: A question-by-question comparison beats a headline feature list, because each answer changes what a vendor costs you.
Should you use MillionVerifier or a different tool?
Let the sample test decide, and use price and brand only to break ties.
| Your situation | Recommended next step |
|---|---|
| Occasional cleans of a few thousand contacts | Run the 500-address test on a free tier, then decide |
| Large list (40,000+) with monthly re-verification | Test on a 1,000-address labelled sample and compare cost per clean address |
| Heavy EU or UK personal data | Obtain the data processing agreement and retention terms before any test upload |
| Checks needed at signup or form submission | Read up on real-time email validation and choose an API-first workflow |
| Choosing a vendor for a team | Score each vendor with how to choose an email verifier |
| Spot-checking a few addresses | Use the free single-email checker |
Teams running email verification for ecommerce and SaaS should weight accuracy and data terms above headline price, because a bad list damages every campaign that follows. If you are also reviewing other vendors, best ZeroBounce alternatives, Bouncer vs ZeroBounce and top Kickbox alternatives apply the same criteria. For ongoing maintenance, email list maintenance best practices covers how often to re-verify.
If you want to test Unlimited Verifier on your own data, start with the free single-email checker, then run your full 500-address sample. Catch-all domains are covered on the catch-all email verification page, so you can see how each one is labelled.
Bottom line: The sample test should choose the tool. Price and branding only break ties.
What are the common mistakes when judging an email verifier?
- Judging by reviews alone. Reviews describe experience, not accuracy on your list.
- Testing with only good addresses. A sample that is entirely valid proves nothing. You need known-bad addresses to measure false valid.
- Counting only the first pass. Re-verification is where costs compound.
- Treating catch-all "valid" as confirmed. A catch-all domain accepts everything, so an address there is uncertain.
- Ignoring per-list limits. A 40,000-row file on Pro must be split into lists of 25,000 or fewer, and Free lists cap at 150 emails.
- Missing the retention window. Free results are kept for 24 hours, so export them the moment a run finishes.
- Skipping data terms because the vendor seems established.
- Confusing verification with consent. A deliverable address is not an opted-in address.
- Treating one small test as final proof. Use a 500-address run as a go/no-go gate, then retest with a larger sample if the decision is close.
Bottom line: Most bad vendor decisions come from testing the wrong sample, counting the wrong costs or skipping the data terms.
How we compared (and limitations)
This article is based on public documentation: IETF RFCs 5321 and 3463, the GDPR text, the FTC's CAN-SPAM guide and Google's sender guidelines. We have not run a controlled benchmark of MillionVerifier or any other verifier. We did not verify MillionVerifier's company registration, ownership, plan details or customer reviews. Its terms and result labels can change, so confirm them on its site before relying on them. Figures attributed to Unlimited Verifier are the company's own published claims. Worked-example numbers are hypothetical and show the arithmetic. The 2% false-valid and 5% false-invalid tolerances are our recommendations, not industry standards.
Labelled 500-address accuracy test
- Build 500 addresses: about 250 known-valid (your own confirmed customers) and 250 known-invalid (hard bounces, typos, dead domains).
- Label each row in a spreadsheet with its true status before uploading.
- Run the full sample through the verifier using default settings.
- Count known-invalid addresses marked valid. Example: 9 of 250 = 3.6%, which fails a 2% pass line.
- Count known-valid addresses marked invalid to measure over-rejection.
- Decide: pass only if false-valid rate is at or below your threshold and over-rejection is acceptable for your list.
Frequently asked questions
Is MillionVerifier a scam?
No public evidence in this article shows MillionVerifier is a scam, and it operates as a bulk verification service. However, we did not verify its company registration or ownership, so check the registry listing, privacy policy and billing terms yourself before uploading data.
Is MillionVerifier accurate?
Accuracy varies by list and must be tested rather than assumed. Build a labelled sample of about 500 addresses with known good and known bad entries, run it through the service, and measure how many known-bad addresses are marked valid.
How much does MillionVerifier cost?
Published terms show the Pro plan at $29 per month, or $25 per month billed annually, with standard verification unlimited on every plan including Free. Confirm current pricing on the vendor's site, as plans can change.
How do I check who owns MillionVerifier?
Find the operating company named in its terms, then search the official business registry for that country, such as Companies House for UK firms. Compare the registered name and address with the vendor's website and legal pages.
Does MillionVerifier sell or share my email list?
Check the privacy policy and data processing terms for how uploaded data is stored, shared and deleted. Be cautious of vague wording about sharing with partners, and request a written retention period before uploading.
Is MillionVerifier safe to upload customer data to?
Safety depends on its data processing agreement, retention period, security practices and your legal obligations such as GDPR. Get these terms in writing and confirm they fit your compliance needs before sending any customer data.
What is a good accuracy threshold for an email verifier?
There is no industry standard. For a regularly mailed list, a reasonable pass line is that no more than 2% of known-bad addresses are marked valid, which is a recommendation you should adjust to your own risk tolerance.
Are MillionVerifier reviews trustworthy?
Reviews show that people use a product but do not audit the company or prove each review is genuine. Read several sources, weigh recent and detailed reviews more heavily, and rely on your own labelled test for accuracy.
Can I get a refund from MillionVerifier if results are wrong?
Refund and credit rules should be stated in the vendor's terms. Ask about credit policies for inaccurate results before purchasing, and keep a record of your test sample to support any claim.
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.