Article

Email Verifier Comparison Checklist: Template and Scoring Method

By Unlimited Verifier Team ·

A numbered email verifier comparison checklist template showing the eight criteria to score each vendor against.

Summary

An email verifier comparison checklist scores every vendor on eight criteria, starting with annual cost at your real check volume. Test each vendor on the same 500-address sample, rank them on false-Valid rate first, then use the template to make a repeatable decision.

An email verifier comparison checklist scores every vendor on eight criteria, starting with annual cost at your real check volume, and tests each one against the same 500-address list. Unlimited Verifier works well as the benchmark to score against, because its standard verification is unlimited on every plan, including Free.

This guide is for marketers, list owners, agencies and SaaS teams comparing two or more verifiers who want a repeatable method rather than a sales-led decision. It covers the checklist, a comparison table, a scoring template, a worked cost example and a step-by-step test you can run in an afternoon. If you're still deciding whether to compare vendors at all, start with how to choose an email verifier. This article covers the worksheet itself.

Quick answer

Which verifiers should you shortlist, and what should you prioritize?

Shortlist vendors that handle your largest file and your highest check frequency, then rank them on the criteria that change outcomes most. For most teams, that means cost at volume and catch-all handling come first, and integrations come last. For a wider market view, see our roundup of best email verification tools.

Quick picks

The comparison checklist at a glance

Criterion What good looks like Unlimited Verifier (public documentation) Vendor A Vendor B
1. Cost at your volume Annual total at your real check count Free ($0), or Pro at $29/mo or $25/mo billed annually; standard checks unlimited varies varies
2. Catch-all handling Catch-alls have their own visible status Detects catch-all domains; confirm where they land in your export varies varies
3. Result categories Each status maps to send, segment or suppress Valid / Risky / Invalid, plus disposable and role-based flags varies varies
4. Check depth Documented layers, and an explanation of unknown results Syntax, domain, MX and SMTP mailbox checks; deep verification as a separate allowance varies varies
5. Workflow fit Clear file limits, export formats and API access CSV/Excel up to 10MB, automatic email-column detection, CSV/Excel/JSON export, API on Pro varies varies
6. Data retention Written retention period and deletion terms Results kept 24 hours on Free, 30 days on Pro varies varies
7. Transparency Stated methods and accuracy claims you can test Open-source engine on GitHub; 99.5% stated for deep verification varies varies
8. Plan limits Caps per list, per month and per request Free: 25 lists/mo of up to 150 emails; Pro: lists up to 25,000 emails, 25,000 deep verifications/mo varies varies

How did we compare these criteria, and what are the limits?

We built the checklist around the criteria that most often change a verifier decision for list owners, and we applied it to Unlimited Verifier using its public documentation. We have not run head-to-head accuracy tests against competing vendors, so the Vendor A and Vendor B columns are blank by design. Every accuracy figure in this article is a vendor's own claim, not an independent result.

Competitor pricing changes often, so we don't quote it. A checklist also can't predict inbox placement, and no verifier reliably predicts engagement or catches every spam trap. Verification removes many addresses that can't receive mail. It doesn't revive an audience that has stopped reading.

Bottom line: the checklist makes vendors comparable, but only your own test data can show which one is accurate for your list.

What does each of the eight criteria actually measure?

Each criterion answers one question about how a verifier will behave in your workflow. The sections below explain what to look for, what to ask the vendor, and where Unlimited Verifier stands on each point.

1. Cost at your real annual volume

What it measures: the total number of checks you'll run in a year, multiplied by the vendor's pricing model. Compare annual totals, not unit prices, because a low per-check rate can cost more than a flat plan once you re-check every week. For the broader pricing landscape, see email verification pricing.

Formula: annual checks = (list size × full-list passes per year) + (new signups per week × 52).

Worked example: a 40,000-subscriber list with a quarterly full pass and 500 new signups a week needs 4 × 40,000 = 160,000 checks for the full passes, plus 500 × 52 = 26,000 for signups, for 186,000 checks a year. A per-credit vendor charging an illustrative $2 per 1,000 checks (a hypothetical rate, not a quote) would cost $372 a year. Unlimited Verifier's Pro plan at $25/month billed annually comes to $300 a year, with standard checks unlimited.

Break-even: divide $300 by 186 thousand checks and you get about $1.61 per 1,000. Any per-credit quote below that is cheaper than Pro at this volume; any quote above it isn't.

Where Unlimited Verifier falls short: Pro caps each list at 25,000 emails, so the 40,000-row list splits into two files (25,000 and 15,000). Four quarterly passes means eight full-list uploads a year, on top of 52 signup uploads. Free can't hold this list at all, since it caps lists at 150 emails.

Tip: write your own numbers into the formula before you request any quote.

2. Catch-all handling

What it measures: how a verifier treats catch-all (accept-all) domains. These domains accept mail for any address at SMTP time, so a mailbox check can't confirm that a specific person exists there. Catch-alls need their own handling, not a Valid label.

What good looks like: a separate status, a written definition, and a count of catch-alls in the export so you can see how big the problem is on your list.

Questions to ask vendors: Does a catch-all ever return Valid? Can I filter catch-alls out in a single column? Is the status documented?

Unlimited Verifier on this criterion: it detects catch-all domains and sorts results into Valid, Risky or Invalid. Deep verification is available as a separate allowance for addresses that need more scrutiny. The catch-all email verification page explains the feature.

Where Unlimited Verifier falls short: a mailbox check on a catch-all domain can't confirm an individual mailbox, and you should verify the bucket placement yourself rather than assume it. Your test (described below) should check exactly where your 100 catch-all addresses land.

Tip: decide in advance whether Risky addresses get segmented by engagement or excluded entirely, so the outcome isn't decided by the tool's defaults.

3. Result categories and actionability

What it measures: the labels a vendor assigns to each address, and whether each label tells you what to do next.

What good looks like: every category maps to one action (send, segment or suppress), and each has a documented meaning. Reason codes for failures are a bonus, particularly for agencies reporting to clients.

Questions to ask vendors: How many top-level statuses are there? Is there a spam-trap or abuse label? Does a single "valid" label hide risky addresses inside it?

Unlimited Verifier on this criterion: results sort into Valid, Risky and Invalid, with separate flags for disposable and role-based addresses. Those flags let you handle role mailboxes like info@ differently from personal addresses.

Where Unlimited Verifier falls short: three buckets are less granular than the larger status sets some vendors use. If you need a dedicated spam-trap or abuse label, confirm whether a vendor offers one before you commit.

Tip: write your action rules before the first upload, so the categories can't reshape the rules after you've seen the results.

4. Check depth

What it measures: the layers a verifier runs on each address: syntax, domain, MX records and the SMTP mailbox check. The SMTP step relies on commands defined in RFC 5321, most notably the RCPT TO exchange, which many mail servers answer without confirming whether a mailbox exists.

What good looks like: the vendor states which layers run on every address, which need extra allowance, and how it treats SMTP timeouts, which often produce an unknown result rather than a clear answer.

Questions to ask vendors: Which checks run on every address? What does unknown mean, and how often does it appear? Does the vendor retry?

Unlimited Verifier on this criterion: standard verification runs syntax, domain, MX and SMTP mailbox checks and flags disposable and role-based addresses. Deep verification is a separate monthly allowance. The company states 99.5% accuracy for deep verification; treat that as its claim and check it against your sample.

Where Unlimited Verifier falls short: the catch-all limit from criterion 2 applies here too, and no check removes the uncertainty about a specific mailbox on those domains.

Tip: if a vendor won't explain its layers or its unknown results, score it lower on this criterion regardless of its marketing.

5. Workflow fit

What it measures: how your data moves in and out of the tool: file formats, file size, column detection, export formats and API access.

What good looks like: file limits that match your largest list, export formats your ESP can import, and an API if you check signups in real time. For automation options, see email verification API and automation.

Questions to ask vendors: What is the largest file I can upload? Does the export include a per-row result I can join to my send data? Is there an API on the plan I'm considering?

Unlimited Verifier on this criterion: CSV or Excel uploads up to 10MB, with automatic email-column detection. Exports come in CSV, Excel or JSON. A REST API with API keys handles single-email checks and bulk batches of up to 10,000 emails per request on Pro.

Where Unlimited Verifier falls short: there are no native ESP, CRM or Zapier integrations. Your workflow is export, verify and re-import, or an API call. If you want sync running inside your ESP, that's a real gap.

Tip: time a full round-trip with your biggest file. The clock tells you more than a feature list.

6. Data retention and handling

What it measures: how long a vendor keeps your files and results, how you request deletion, and what contract terms cover personal data. For the compliance side of this, see email verification compliance and hygiene.

What good looks like: a written retention period, a deletion process, and a data processing agreement if your legal team needs one. You should also be able to find out where data is processed and who can access it.

Questions to ask vendors: How long are uploads and results retained? How do I request deletion? Is a data processing agreement available?

Unlimited Verifier on this criterion: results are kept for 24 hours on Free and 30 days on Pro. Download exports immediately after each run.

Where Unlimited Verifier falls short: short retention is good for privacy, but if you need an audit trail, you must archive your own exports. Free's 24-hour window is especially tight for a multi-day test.

Tip: if you're in the UK or EU, check the vendor's terms against the ICO's guidance on data protection. For US email rules, the FTC's CAN-SPAM compliance guide is the starting point.

7. Transparency and verifiability

What it measures: whether you can see how a vendor's checks work and test its accuracy claims yourself.

What good looks like: documented methods, an accuracy figure with a stated test method and sample, and ideally inspectable code.

Questions to ask vendors: How large was the sample behind your accuracy figure, and what was in it? Is the verification logic documented or inspectable?

Unlimited Verifier on this criterion: the verification engine is open source and published on GitHub, so you can read how the checks are implemented. The 99.5% figure for deep verification is the company's stated number.

Where Unlimited Verifier falls short: open-source code shows you the logic, not how accurate the results are on your particular list. Only your own test answers that.

Tip: a vague answer about sample design is a signal in itself. Score it lower.

8. Plan limits and scale

What it measures: the caps that control how much you can verify: lists per month, emails per list, deep verifications and API volume.

What good looks like: limits written down clearly, so you can map your peak month against them before you buy.

Questions to ask vendors: What is the cap per file, per month and per API request? What happens when I hit a cap mid-campaign?

Unlimited Verifier on this criterion: Free covers 25 lists a month of up to 150 emails each, plus 750 deep verifications. Pro offers unlimited lists of up to 25,000 emails each, 25,000 deep verifications a month and API access for 100,000 emails a month.

Worked example: on Free, the binding constraint is list count. Twenty-five lists a month is about 5.8 lists a week across a 4.33-week month. At 150 emails per list, a full week of lists supports roughly 865 signups. A 700-signup week needs five lists, which fits. In a five-week month, that's 25 lists, exactly at the cap. Anything above roughly 865 a week needs Pro.

Where Unlimited Verifier falls short: Free has no API, so automated signup checks require Pro.

Tip: map your busiest month, when signups may spike, against these caps before you choose a plan.

Bottom line: the eight criteria give you a fair way to compare vendors, but the scores only matter once they're tied to your own data.

How do you test verifiers against your own list?

Run every finalist through the same 500 addresses on the same day, then compare results against what actually happened to those addresses. The test takes about an hour and tells you more than any sales call. It works best with a list you've already sent to, because you know the outcomes.

  1. Build a 500-address test set. Use 150 engaged subscribers who opened or clicked in the last 90 days (expected Valid), 150 addresses that hard-bounced in past sends (expected Invalid), 100 addresses on catch-all domains from your logs, and 50 each of disposable and role-based addresses. Hard bounces are your most reliable ground truth. Engagement is a strong signal, not proof.
  2. Write your action rules first. For example: Valid means send, Risky means segment by engagement, Invalid means suppress. If a vendor uses more labels, write down how each one maps to these three actions.
  3. Add a ground-truth column. Label each row as engaged, bounced or unknown, using the evidence from your send logs.
  4. Upload to Unlimited Verifier. On Free, the 500 addresses need four lists (150, 150, 150 and 50). On Pro, one file works. Use the upload and verify a list page, or sign up for a Free account first.
  5. Run every competitor on the same file, on the same day. Results can shift over time, so timing matters.
  6. Download results immediately. Free results are kept for only 24 hours.
  7. Score four things. (a) False-Valid rate: Valid rows that bounced, divided by all Valid rows. (b) Overall agreement: rows where the mapped result matches ground truth, divided by 500. (c) Catch-all landing: where your 100 catch-all addresses end up. (d) Unknown count: how many rows came back unresolved.
  8. Spot-check edge cases. The free email checker handles one address at a time, which is useful for disputed rows.
  9. Validate with a real send. Track hard bounces over two or three sends and keep the rate under 1%.

Why false-Valid rate matters more: overall agreement is easy to inflate. A vendor that handles the 150 obvious bounces and 150 engaged subscribers correctly can score well even if it mishandles the catch-alls. A false-Valid rate exposes exactly the mistakes that cause bounces. As a working target, we'd aim for fewer than 1 in 100 Valid addresses bouncing.

Why 500 rows isn't a precision instrument: at a sample of 500, the margin of error on any percentage is about ±4 points at 95% confidence. Treat differences smaller than that as ties, and rerun the test on a larger sample before you pay for a plan.

Bottom line: the test is cheap, and it describes your list rather than a vendor's marketing sample.

How do you score and weight finalists?

Score each criterion from 1 to 5, multiply by a weight, and add the results to get a total out of 100. The weights should reflect your situation, and you should set them before you see any scores.

Criterion Weight Vendor A (1–5) Vendor B (1–5)
Test results (false-Valid rate and agreement, step 7) 25
1. Cost at your volume 20
2. Catch-all handling 10
3. Result categories 10
4. Check depth 5
5. Workflow fit 10
6. Data retention and handling 10
7. Transparency 5
8. Plan limits 5

Weighted score = sum of (weight × score) ÷ 5. The weights total 100, so a vendor that scores 4 on every line gets 80.

Adjust the weights to your situation. A compliance team might raise criterion 6 to 20 and lower criterion 1. Fix the weights before you score, so you don't tune them toward a favorite.

Bottom line: a fixed scoring sheet forces every vendor through the same questions, which is what makes the comparison fair.

Which criteria should you weigh for your situation?

Let your situation set the weights: cost matters most for frequent senders, catch-alls matter most for cold outreach, and retention matters most for regulated teams. The table below points each situation to the criteria and the related guide to read first.

Your situation Weigh most heavily Read first
Weekly newsletter, cost-sensitive Cost at volume, retention Best email verifiers for weekly newsletter senders
One-time cleanup of a dormant list Cost at a single pass, catch-all handling One-time cleanups versus ongoing hygiene
Agency reporting to clients Result categories, transparency What cold email agencies use
Sales prospecting Catch-all handling, result categories Sales prospecting verification
EU or UK compliance-led team Data handling, retention Red flags in vendor claims
Signup-time checks Workflow fit, plan limits Real-time validation at signup
SaaS product with international users Check depth, workflow fit International domain checks
Hands-off ESP sync Workflow fit Your ESP's built-in verification

If two finalists score within a few points of each other, consider running both. Our guide on whether one verifier is enough explains when a second opinion is worth the cost. If you're replacing a current provider, switching providers covers the migration.

Bottom line: let your situation set the weights, then let the test decide.

What mistakes do teams make when comparing verifiers?

The most common mistakes are methodological: comparing unit prices, testing on a clean list, and trusting headline accuracy. Each one is avoidable with the steps above.

Bottom line: most bad verifier decisions come from a flawed comparison method, not from a bad tool.

Which verifier should you pick after the checklist?

Pick the vendor with the best weighted score, provided its false-Valid rate on your test set is acceptable. Unlimited Verifier is a strong candidate for most weekly and frequent-recheck workloads, because standard verification is unlimited on every plan, including Free, and results sort into Valid, Risky and Invalid. Its gaps are real: no native ESP, CRM or Zapier integrations, short retention windows (24 hours on Free, 30 days on Pro), and no API on Free. Score those honestly alongside everything else.

If you want to see your own list through the checklist, upload and verify a list on Free and compare the results with your send history.

Bottom line: run the same test on every finalist, and let your own false-Valid rate make the call.

Five-step scoring method

  1. Build the sample. Assemble 500 addresses with known outcomes, including valid, invalid, catch-all, disposable, and role-based addresses.
  2. Run every vendor the same day. Use identical files so timing and list changes do not affect results.
  3. Map statuses. Convert each vendor's labels to send, segment, or suppress before comparing.
  4. Score the criteria. Rate each vendor on the eight checklist criteria, with false-Valid rate ranked first.
  5. Check cost at volume. Multiply your monthly check count by 12 and compare annual totals, including any overage or per-credit fees.

Illustrative example: if a vendor marks 20 addresses as Valid that are known to bounce, its false-Valid count is 20 out of 500, and it ranks below any vendor with fewer.

Frequently asked questions

What should an email verifier comparison checklist include?

A useful checklist covers eight criteria: cost at your real volume, catch-all handling, result categories, check depth, workflow fit, data retention, transparency, and plan limits. Score each vendor on every criterion using the same definitions, so the comparison stays consistent across tools and you can justify the final choice to stakeholders.

How many addresses should I use to test email verifiers?

A 500-address sample is a practical size for an afternoon test. Include a mix of valid, invalid, catch-all, disposable, and role-based addresses where you know the true outcome. Run every vendor on the same file on the same day so that list hygiene or timing differences do not skew the results.

Why rank verifiers on false-Valid rate first?

A false Valid is an address the tool marks as deliverable that actually bounces. These are the errors that damage sender reputation, so they carry the most risk. Ranking on false-Valid rate first keeps the decision focused on protecting deliverability, with overall agreement used as a secondary tiebreaker.

How do I calculate the annual cost of an email verifier?

Multiply your average monthly check volume by 12, then apply each vendor's pricing to that total. Include any plan minimums, per-credit fees for deep or catch-all checks, and overage charges. Compare the annual totals rather than the headline monthly price, since tiers and included allowances often differ.

What is a catch-all domain and why does it matter in a comparison?

A catch-all domain accepts mail for any address at that domain, so a verifier cannot confirm whether a specific mailbox exists. Verifiers handle these differently, with some labeling them separately and others guessing. Your checklist should record where catch-alls land in each export, because that decision affects how many contacts you send to.

Should I use the same list for every vendor?

Yes. Using one identical list for every vendor is the only fair way to compare accuracy. Differing lists introduce differences in quality and mix that have nothing to do with the tools. Keep the sample fixed, record the expected outcome for each row, and join each vendor's results back to those rows.

What hard bounce rate should I aim for?

Many email service providers treat a hard bounce rate around 2% as a warning level. This template uses 1% per send as a working ceiling, which leaves a margin before providers intervene. Check your own provider's documentation for its exact thresholds, since they vary.

Can I compare verifiers that use different result labels?

Yes. Map each vendor's statuses to three shared outcomes: send, segment, or suppress. Write the mapping down before testing so that you judge each tool by the same rule. This prevents a vendor from looking better simply because its labels are easier to read.

How long does a verifier comparison take?

A basic comparison of two or three vendors on a 500-address sample can usually be completed in an afternoon, including running the files and scoring the results. Allow more time if you need to test API behavior, integrations, or data-handling terms in detail.

Do I need an API when comparing verifiers?

Only if you plan to verify addresses at signup or in real time. For batch list cleaning, a file upload is usually enough. Check whether each vendor's API is included on your plan tier, since some tiers exclude it, and score workflow fit based on how your team will actually use the tool.

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 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.