Article
Debounce vs MillionVerifier: Pricing, Labels and Accuracy Compared
By Unlimited Verifier Team ·

Summary
Debounce and MillionVerifier run similar core checks, so the real differences come down to how each prices repeat passes, labels results and connects to your tools. Neither can prove a contact wants your email, so cost per clean contact and label mapping should drive the decision. A 200-good and 200-bad seed test from your own history settles close calls.Debounce and MillionVerifier both describe similar core checks (syntax, domain, MX records and mailbox status), so the real differences lie in how each prices repeat passes, labels results and connects to your tools. Neither can prove that a contact wants your email.
If you're weighing the wider market, start with our email verifier alternatives overview. This article covers the head-to-head: what each tool does well, how result labels map to sending decisions, the cost per clean contact across repeat passes, and a seed test you can run in an afternoon.
Quick answer
- Both bill by credit or per check. Your real cost is credits per address multiplied by the number of passes, so re-running a list three times can cost three times as much.
- Neither proves consent. Both test whether an address can accept mail, not whether the person wants it.
- Decide on workflow first. Connectors, API granularity and how labels map to your sending buckets usually settle the choice before headline accuracy does.
- Unlimited Verifier prices differently. Standard verification is unlimited on every plan, including Free. Deep verifications are capped at 750 a month on Free and 25,000 a month on Pro.
- Settle close calls with a seed test. Run 200 known-good and 200 known-bad addresses from your own history through each tool, then compare false-valid rates.
How do Debounce and MillionVerifier compare side by side?
Both vendors sell credit-based access, and both offer bulk upload and an API. The differences show up in label handling, connectors and how cost grows when you re-check a list.
| Factor | Debounce | MillionVerifier | Unlimited Verifier |
|---|---|---|---|
| Pricing model | Prepaid credits, per its pricing page | Credit-based, per its site | $0 Free; Pro $29/month or $25/month billed annually |
| What drives cost | Credits per address checked | Credits per address checked | Standard verification unlimited on all plans; deep verifications capped (750 Free, 25,000 Pro) |
| Result categories | Its own label set; you map each label to your buckets | A main result plus a sub-result field, per its API documentation | Valid, Risky or Invalid |
| Catch-all handling | Accept-all label | catch_all result, per its API documentation | Catch-all domains detected and flagged |
| API | Offered | Offered, with result and sub-result fields | REST API with keys; single checks and bulk requests up to 10,000 emails; Pro includes 100,000 API emails a month |
| Integrations | Markets platform connectors; confirm yours is listed | Not a focus of the documentation we reviewed | No native ESP, CRM or Zapier integrations; export CSV and re-import, or call the API |
All three check the same underlying signals. We have not confirmed every limit for the two competitors, so check their current pages before budgeting.
Bottom line: Compare label handling, integrations and cost per re-run before you compare anything else.
What is each tool best at, and where does it fall short?
Each tool has a clear strength and a specific trade-off. Here is what separates them.
- Debounce. Its differentiator is connector-led workflows, which matter if your ESP or CRM is on its list. Its own label set has to be translated into your buckets before exports are comparable. The connector advantage disappears for teams running API-only pipelines.
- MillionVerifier. Its API documentation describes a main result plus a sub-result field, which lets developers route disposable and role-based addresses differently. The sub-result only helps if your pipeline reads it. A CSV-only team gets the same main decision either way. For a direct comparison, see MillionVerifier vs NeverBounce.
- Unlimited Verifier. It offers unlimited standard verification on every plan with no per-email fees, a three-bucket Valid, Risky and Invalid output that maps directly to sending decisions, and an open-source verification engine on GitHub that you can inspect. It also provides free single-email and domain blacklist checkers. Its trade-offs are no native ESP, CRM or Zapier integrations, and Free results that expire after 24 hours.
If Debounce's connectors don't fit your stack, our Debounce alternatives guide covers other options. If ZeroBounce is also on your shortlist, start with best ZeroBounce alternatives.
Which is more accurate? We know of no independent head-to-head benchmark that covers both tools on your kind of data, so accuracy has to be measured on your own list. Unlimited Verifier's 99.5% figure for deep verification is the company's own stated number.
Bottom line: Each tool wins on a different axis, so match the axis to your workflow before you look at accuracy.
What do the result labels actually mean?
Every verifier names its results differently. You need a mapping from each label to a sending action before you can compare exports.
| Typical label | What it usually means | Suggested bucket | Action |
|---|---|---|---|
| Mailbox not found, bad syntax, dead domain | Mail to this address will bounce | Invalid | Suppress permanently |
| Accept-all or catch-all | The domain accepts any address, so the mailbox can't be confirmed | Risky | Hold back from first sends |
| Disposable | Temporary or throwaway provider | Risky (Invalid under a strict policy) | Exclude from marketing |
| Role-based (info@, sales@) | Shared inbox, often low engagement | Risky | Exclude from cold outreach |
| Unknown or timeout | The server gave no clear yes or no | Risky | Retry once later, then hold |
| Spam trap or toxic | Linked to trap networks or poor history | Invalid | Remove and trace the source |
Spam-trap labels deserve caution. No verifier catches every trap, and pristine traps, which were never used by a real person, are generally described as the hardest to detect. Treat a trap label as a reason to audit where the address came from.
SMTP mailbox checks depend on how the receiving server answers a recipient query, as described in RFC 5321. Some servers accept every recipient or limit repeated checks, which is why catch-all results need their own category. For a closer look at how Unlimited Verifier handles them, see the catch-all email verification page.
Bottom line: Build your own label-to-action map first, because you'll act on those labels every day.
Which one costs less per clean contact?
The fairest metric is cost per clean contact: total spend divided by the valid contacts you keep. Sticker price per 1,000 checks ignores the re-run multiplier entirely. This is one of the key email verification pricing questions to ask any vendor.
Cost per clean contact = total verification spend ÷ valid contacts retained
These figures are illustrative. A hypothetical credit price of $0.004 per check is used throughout. Replace it with your own quote.
- One pass on 100,000 contacts: 100,000 × $0.004 = $400. If 85,000 come back valid, that's $400 ÷ 85,000 ≈ $0.0047 per clean contact.
- Three passes on the same list: 300,000 checks × $0.004 = $1,200. With the same 85,000 valid, that's about $0.0141 per clean contact.
Later passes often recover few additional valid contacts, because the addresses left over are frequently the ones that time out or stay unresolved. Three passes can triple your spend while adding little to the valid count. Set a pass limit before you start.
Unlimited Verifier's model works differently. Standard verification is unlimited on every plan with no per-email fees, so repeat standard passes don't change your bill. Deep verifications are the capped resource, at 750 a month on Free and 25,000 a month on Pro.
Bottom line: Calculate cost per clean contact across the passes you will actually run, not the price of one check.
Which should you choose for your workflow?
Choose based on the constraint you can't work around. Start with the table, then follow the process below it.
| Your situation | Lean toward | Why |
|---|---|---|
| Checks needed inside your ESP, without file exports | Debounce, if its connector covers your platform | Connectors remove the export and re-import step |
| Developer pipeline that needs granular result codes | MillionVerifier | Sub-results let you route disposable and role addresses separately |
| Large lists re-verified every month | Unlimited Verifier Pro | Standard checks are unlimited, so repeat passes add no per-email cost |
| Corporate lists heavy with catch-all domains | Whichever tool wins your seed test on catch-all handling | Catch-all share drives both cost and risk, so measure it on your data |
| One small file under 150 addresses | Unlimited Verifier Free | Free covers 25 lists a month of up to 150 emails each |
| Live Zapier or CRM sync required | A tool with a native connector for your stack | Unlimited Verifier has none, so it is not the fit here |
| Outbound cold email | Compare on false-valid rate first | Cold lists carry the most bounce risk; see ZeroBounce vs MillionVerifier for cold email |
A five-step decision process:
- Write down your monthly volume, the number of re-run passes and whether you need native integrations.
- Calculate cost per clean contact for each vendor at its current rates.
- Build a seed set and run the head-to-head test below.
- Compare false-valid rates first, then false-invalid rates.
- Choose the tool that meets your integration need at the lowest cost per clean contact, with an acceptable false-valid rate.
For a broader framework, read how to choose an email verifier and our overview of the best email verification tools.
Bottom line: Integrations and re-run cost usually decide the choice, and your own seed test settles any close call.
How do you run a fair head-to-head test?
A seed test measures your data, not a vendor's claims. The most important number is the false-valid rate: the share of known-bad addresses a tool labels Valid. Those are the addresses that bounce and damage sender reputation.
- Build a known-good set of 200 contacts. Use people who opened or clicked in the last 60 days and have no hard-bounce history. Recent engagement is strong evidence of a live mailbox, but it is not proof.
- Build a known-bad set of 200 addresses. Use addresses that hard-bounced in past sends with a permanent failure. A
5.1.1code means the mailbox doesn't exist, as defined in RFC 3463. - Run both sets through each tool on the same day. Results can change over time, so keep timing consistent.
- Calculate the metrics in the table below.
- Check the margin of error. With 200 per group at 95% confidence, the worst-case margin is about ±6.9 points (1.96 × √(0.25 ÷ 200)). Gaps smaller than that aren't conclusive. For close calls, use 400 per group, which gives about ±4.9 points. This assumes random sampling, which a seed set rarely achieves, so treat the result as a rough guide.
| Metric | Formula | How to read it |
|---|---|---|
| False-valid rate | Known-bad labelled Valid ÷ 200 | Lower is better; this drives bounces |
| False-invalid rate | Known-good labelled Invalid ÷ 200 | Lower is better; this drops real customers |
| Agreement rate | Correct labels ÷ 400 | Useful for a summary, but weigh the two error rates more heavily |
| Catch-all count | Addresses labelled catch-all or accept-all | Shows how much of your list needs holding back |
| Cost for the test | Credits or plan share used | Compare against cost per clean contact |
Bottom line: Compare false-valid rates first, because a false valid is the error that causes bounces.
How do you run the test with Unlimited Verifier?
This tutorial takes about 20 minutes for a 400-row seed set and needs no technical background.
- Export your seed set as a CSV. Include the email column. Keep a separate sheet that records each address's group (known-good or known-bad) so you can score the results later.
- Create an account. Sign up for free. The Free plan allows 25 lists a month of up to 150 emails each, so 400 rows need three lists.
- Split the file. Create three CSVs with 150, 150 and 100 rows. Mix the known-good and known-bad groups across all three files so no file is a single group.
- Upload each file. Go to upload and verify a list. CSV and Excel files up to 10MB are accepted, and the email column is detected automatically.
- Score each group. For known-good addresses, count Invalid results. For known-bad addresses, count Valid results. Those are your false-invalid and false-valid counts.
- Export the results the same day. Free results are kept for 24 hours. Save them as CSV, Excel or JSON.
- Repeat for the other vendors. Use each vendor's own upload or API, then fill in the metrics table with the same 400 addresses.
To check a single address that looks unusual, such as a VIP contact that came back Risky, the free email checker is quicker than a full upload.
Bottom line: Export, split, upload, score and export again the same day. Do this with the same 400 addresses for each vendor.
What does a 100,000-contact cleanup cost in practice?
Here is a worked example that respects Unlimited Verifier's real limits. The percentages are illustrative, not measured results.
Scenario: A SaaS company has 100,000 contacts, including 30,000 imported from a trade show last year.
Step 1: Split under the Pro cap. Pro allows lists of up to 25,000 emails each. 100,000 ÷ 25,000 = 4 lists. Also check file size. Wide CSVs with many columns can exceed the 10MB upload limit at 25,000 rows, so split further if needed.
Step 2: Run standard verification on everything. Standard checks are unlimited on Pro, so all 100,000 addresses are covered with no per-email charge.
Step 3: Deep-verify the risky subset. Suppose standard verification places 18,000 addresses in Risky, mostly catch-all and role-based. Deep verifications used: 18,000. Remaining from the 25,000 monthly allowance: 25,000 − 18,000 = 7,000.
Step 4: Illustrative outcome.
| Bucket | After standard | After deep on Risky | Share of 100,000 |
|---|---|---|---|
| Valid | 79,000 | 91,000 | 91% |
| Risky | 18,000 | 3,000 | 3% |
| Invalid | 3,000 | 6,000 | 6% |
Check: 91,000 + 3,000 + 6,000 = 100,000. The 15,000 addresses that left Risky split into 12,000 newly Valid and 3,000 newly Invalid.
Step 5: Cost. The Pro plan is $29 for the month. That covers all four lists, all standard checks and the 18,000 deep checks.
Comparison at the hypothetical $0.004 credit rate: Holding the valid count at 91,000 for both, for simplicity:
- Unlimited Verifier Pro: $29 ÷ 91,000 ≈ $0.00032 per clean contact
- Credit model, three passes: $1,200 ÷ 91,000 ≈ $0.0132 per clean contact
The credit comparison assumes deep-style checks cost the same as standard ones. If they cost more, the gap widens. Confirm the pricing before budgeting.
API variant: Sending the same 100,000 contacts by API means 10 bulk requests of 10,000 emails each. Pro includes 100,000 API emails a month, so this one list uses the full allowance. For developer workflows, see email verification API and automation and the Email verification API key page.
Bottom line: For this list, the cost gap comes from re-run passes, not from the price of one check.
How should you act on Valid, Risky and Invalid results?
The bucket determines what you send and when. Don't mix buckets in one campaign.
| Bucket | Re-enter sending? | Action | Timing |
|---|---|---|---|
| Valid | Yes, starting with the most engaged segment | Import and segment | First ramp |
| Risky, catch-all | Hold back; test later with a small batch | Keep out of the main ramp | After sending stabilises |
| Risky, role or disposable | Exclude from marketing | Decide by written policy | Ongoing |
| Invalid | No | Suppress permanently; never re-import | Immediately |
Keep complaints low while you ramp. Google's email sender guidelines recommend keeping spam rates below 0.10% and say they should never reach 0.30%. Verification reduces bounces, but it does nothing about complaints from people who never wanted the email. For the maintenance schedule that keeps the list clean afterward, see email list maintenance best practices.
Bottom line: Valid contacts go out first, Risky contacts wait, and Invalid contacts never come back.
What are the most common mistakes?
- Comparing accuracy claims without a seed test. Vendor figures, including Unlimited Verifier's 99.5% stated deep-verification accuracy, are claims until your own data confirms them.
- Ignoring the pass multiplier. Re-checking unknowns three times can triple the cost for a small gain in valid contacts.
- Counting catch-all addresses as Valid to hit volume. A catch-all result means the mailbox was not confirmed, so hold these back.
- Judging a tool by its total valid count. A tool that labels more addresses Valid can look better while sending more bounces. Measure false valids.
- Using an unrepresentative seed set. If your known-good group is only your most loyal subscribers, every tool will look accurate.
- Forgetting Free's 24-hour retention. Export results the same day or you will have to run the list again.
- Uploading oversized files. Full CRM exports often exceed 10MB, so split them before upload.
- Re-importing Invalid contacts or unsubscribes. Carry your suppression list into every new tool, or old bounces return.
- Treating a Valid result as permission. Verification tests deliverability, not consent.
Bottom line: Most mistakes come from measuring the wrong thing: total valid count instead of false valids, and sticker price instead of cost per clean contact.
What can no verifier prove?
A verifier answers one question: can this address probably receive mail? It cannot tell you whether the person opted in, whether they still want your email, or whether a mailbox that answered yesterday will bounce tomorrow.
For compliance, the baseline is consent and an easy opt-out. In the US, the FTC's CAN-SPAM compliance guide sets out the requirements. Verification supports email verification compliance and hygiene, but it doesn't replace opt-in records. If your list was bought or scraped, no verifier can fix the underlying problem.
To stop bad addresses entering your database in the first place, add real-time email validation to signup forms.
Bottom line: Verification cleans deliverability. Consent and engagement still need their own processes.
How we compared (and limitations)
- This comparison is based on public documentation from each vendor, the RFCs cited above and Google's published sender guidelines. We have not run controlled tests of Debounce or MillionVerifier and have not benchmarked their accuracy.
- Descriptions of Debounce and MillionVerifier reflect their public pages and documentation at the time of writing. Labels, connectors and pricing change, so check current pages before buying.
- Unlimited Verifier figures come from the company's published plan facts. The 99.5% deep-verification accuracy is the company's stated figure, not an independent benchmark.
- All dollar amounts in the worked examples, including the $0.004 credit rate, and all scenario percentages are hypothetical. Replace them with your own quotes and seed-test results.
- Margin-of-error figures assume random sampling. Your seed set may not be random.
- If your question is whether MillionVerifier is trustworthy as a company, not how it performs, see whether MillionVerifier is legit.
Bottom line: Treat every vendor figure here as a claim to verify, and let your own seed test make the final call.
Cost per clean contact across repeat passes
| Scenario | Passes | Credits used per address | Notes |
|---|---|---|---|
| One-time cleanup | 1 | 1 | Lowest cost, no re-check |
| Quarterly re-check | 4 per year | 4 | Cost grows with each pass |
| Pre-campaign plus monthly | 12 per year | 12 | Highest spend, use only for high-risk lists |
Steps: 1) Count addresses. 2) Multiply by credits per address. 3) Multiply by planned passes. 4) Divide by the number of clean contacts you expect to send to. Compare the result across tools using current vendor pricing.
Frequently asked questions
Is Debounce more accurate than MillionVerifier?
Neither vendor's accuracy is established in this article, and both run similar core checks. The best way to compare is a seed test using 200 known-good and 200 known-bad addresses from your own history, then measuring false-valid rates for each tool.
How much does MillionVerifier cost compared with Debounce?
Both sell credit-based access, so cost depends on credits per address and how many passes you run. Check each vendor's current pricing page, because limits and rates change. Multiply credits per address by the number of re-runs to estimate true cost.
Does Debounce integrate with my ESP or CRM?
Debounce markets platform connectors, but whether yours is supported depends on its current list. Confirm your specific ESP or CRM before buying, since API-only pipelines do not benefit from connectors.
What does a catch-all result mean?
A catch-all result means the domain accepts mail for any address, so a verifier cannot confirm that a specific mailbox exists. Treat these contacts as a separate bucket and decide whether to send based on your risk tolerance and engagement history.
Do email verifiers prove someone wants my emails?
No. Verification only tests whether an address can accept mail. It does not prove consent or interest, so you still need opt-in practices and engagement-based suppression.
Why does re-verifying a list raise my costs?
Credit-based tools charge per check, so each pass over the same list spends credits again. Running a list three times can cost roughly three times as much, so schedule re-checks only when addresses have aged or your sending data changed.
How should I map verifier labels to sending buckets?
Map each vendor's labels to three buckets: send, review and suppress. Valid addresses go to send, catch-all and risky addresses go to review or a low-volume segment, and invalid addresses are suppressed. Document the mapping so results from different tools stay comparable.
What is a seed test for email verification?
A seed test runs a known set of addresses through each tool and compares the results to the truth. Use 200 addresses you know are good and 200 you know are bad, drawn from your own history, then compare false-valid and false-invalid rates.
Is Unlimited Verifier a cheaper option?
Unlimited Verifier lists standard verification as unlimited on all plans, with deep verifications capped monthly. Compare its limits and pricing with Debounce and MillionVerifier on your actual volumes before deciding.
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.