Article
What Email Verifier Do Deliverability Experts Recommend?
By Unlimited Verifier Team ·

Summary
Deliverability experts do not recommend one universal email verifier. They choose based on whether the tool runs a real SMTP mailbox check, flags catch-all and disposable addresses separately, and proves its accuracy on your own data. Keeping bounces under 2% is a practical target.No single email verifier is the answer for every list. The right pick runs a real SMTP mailbox check, separates catch-all and disposable addresses from confirmed-valid ones, and helps you keep bounces under 2%.
This guide covers the criteria that matter, a six-step selection framework, a comparison of five options as publicly described, a back-test you can run on your own data before paying, and the mistakes that undo good tools. For the wider selection process, start with our guide to choosing an email verifier.
Quick answer
- No single winner. The best verifier depends on your list type, volume and integration needs. Choose by criteria, not by ranking.
- Non-negotiable: a real SMTP mailbox check, with catch-all and disposable addresses flagged separately instead of counted as Valid.
- Back-test on your own data. Run each shortlisted tool against addresses whose outcomes you already know. Treat vendor accuracy claims as a starting point.
- Use 2% as your bounce ceiling. Google asks bulk senders to keep spam rates below 0.10% and warns against 0.30% or higher. Amazon SES documents review at a 5% bounce rate. Stay under 2% and you have headroom below both.
- Unlimited Verifier includes unlimited standard verification on every plan, including Free, and sorts every address into Valid, Risky or Invalid.
What do deliverability experts look for in an email verifier?
Five criteria separate a useful verifier from a checkbox: depth of the mailbox check, handling of uncertain results, accuracy you can test, data terms, and cost per verified address. Judge each one by asking whether it changes what you actually do with your list.
1. Depth of the check
A syntax check confirms an address is well formed under the rules in RFC 5321. That is the floor, not the job. jane@gmial.com has valid syntax and will still bounce. A solid verifier also confirms the domain exists, checks for MX records, and runs an SMTP mailbox check: it opens a conversation with the receiving server and asks whether the recipient exists, without sending a message.
The check has real limits. Some servers accept every address, some rate-limit lookups, and some defer their answer. An "unknown" result is not a tool failure. It means the server would not commit. What matters is what the tool does next: retry, flag it, or guess.
2. Handling of uncertain results
The most important question to ask a vendor is what it does with catch-all domains. These servers accept mail for any address, so a Valid result there says nothing about the specific mailbox. Treat catch-all addresses as Risky and send to them last.
Ask vendors to show a sample file with raw categories for catch-all domains, not just a summary count. The summary tells you the score. The raw category tells you whether the tool is making the call you need.
Also check how disposable and role-based addresses (such as info@ or sales@) are flagged. Role addresses often reach a shared inbox, so they are rarely wasted sends, but they are poor targets for personal outreach. Most senders should hold them as Risky rather than delete them.
3. Accuracy you can test
A stated accuracy figure means little without its ground truth: which addresses were tested, how their true status was established, and how many were in the sample. Ask for all three. Unlimited Verifier states 99.5% accuracy for deep verification. That is the company's own figure, not an independent benchmark.
4. Data terms
Unlimited Verifier keeps results for 24 hours on the Free plan and 30 days on Pro, so build an export step into your process. If you hold EU or UK contacts, ask the vendor whether it acts as your data processor, and request its data processing terms before you upload personal data.
5. Cost per verified address
Compare total cost at your real volume, including re-checks. The worked examples below show the arithmetic.
| Criterion | What good looks like | Why it matters |
|---|---|---|
| Mailbox check | SMTP handshake, not just syntax and MX | Catches dead mailboxes that look valid on paper |
| Catch-all handling | Flagged as Risky, not Valid | Prevents false confidence in B2B lists |
| Result categories | Clear buckets you can act on | Turns output into send, hold or remove decisions |
| Testable accuracy | Claims you can check against your own bounces | Reduces reliance on marketing figures |
| Data retention | Stated windows and deletion terms | Supports your own compliance records |
| Cost per address | Known price per 1,000 at your volume | Avoids surprise bills after the first run |
For a fuller list of features that actually move results, see which email verifier features actually matter.
Bottom line: Judge a verifier on mailbox depth, catch-all handling, testable accuracy, data terms and real cost, in that order. Cost comes last because a cheap tool that mislabels catch-all addresses costs more in bounces later.
How do you choose an email verifier in six steps?
Work through these steps in order. Each one produces a decision you need before you commit.
- Classify your list. Record each segment's source (signup, imported, trade show, scraped or purchased), its size, and how often you send. Source matters. A two-year-old trade-show import and last week's signups will show very different bounce rates, and a single average hides that gap.
- Write your Risky policy first. Decide who receives Risky addresses, when, and what happens to them after a set period, such as 30 or 60 days. If you decide after seeing results, you will be tempted to keep the addresses you want.
- Shortlist three tools by integration model. Choose based on how your data moves: CSV or Excel upload, API, or a native connector. The vendor questions to ask before buying will filter the field quickly.
- Back-test on a stratified sample. Build 300 addresses with known outcomes, split across your real sources. The method is in the sections below.
- Price at your real volume. Include re-checks and per-list limits, then calculate the cost per 1,000 verified addresses.
- Pilot one segment, then schedule. Verify one segment end to end, confirm the results match your bounce data, and only then run the full list and set a re-verification cadence.
Bottom line: The tool that wins your back-test on your own sources, at your volume, is the right choice, even if it isn't the most-mentioned name.
Is there one email verifier that deliverability experts all agree on?
No. Lists differ, and so do the risks. A newsletter's engaged subscribers, a sales team's prospect list and a SaaS signup flow each need something different from a verifier, so the same tool can suit one and disappoint another. Anyone who names one universal winner is simplifying. For the wider field, see our roundup of best email verification tools.
We did not survey deliverability consultants. In this guide, "what experts recommend" means the criteria and trade-offs that public documentation and practitioner write-ups emphasise, with each vendor's self-described features as the starting point.
| Option | Differentiator (as the vendor describes it) | Best fit | Specific watch-out |
|---|---|---|---|
| ZeroBounce | Describes AI-based scoring and activity-based signals alongside its results | Teams that want extra scoring signals on B2B lists | Scores are vendor-defined, so the cut-off you pick matters more than the score itself |
| NeverBounce | Uses an "unknown" result category and lists integrations with several ESPs and platforms | Teams that want connectors to their sending platform | Unknowns need a written re-check rule, or they quietly accumulate in the list |
| Kickbox | Returns a single Sendex score for each address | Teams that want one number to set send thresholds | A single score doesn't show which check drove a rejection, so you'll need category data to explain results |
| Hunter | Domain search and email finder built around prospecting | Sales teams sourcing new contacts | Designed to find people, so cleaning an existing CRM export uses only part of the product |
| Unlimited Verifier | Unlimited standard verification on every plan; Valid/Risky/Invalid sorting; open-source engine | Teams cleaning CSV or Excel lists who want predictable costs | No native ESP, CRM or Zapier integrations; Pro caps each list at 25,000 emails |
Star ratings on G2 and Capterra reflect how people experience the software. They don't measure accuracy, so use them to build a shortlist, not to choose a winner.
The Unlimited Verifier engine is published as open-source code on GitHub, so technical teams can read how its SMTP checks are written. That helps when a compliance reviewer asks how a result was produced. Ask the vendor how closely the hosted service matches that code, because the two are not the same thing by default.
Bottom line: Experts don't converge on one brand because the lists differ. Choose by list type, integration needs and how you will test the result.
How do you back-test a verifier before you buy?
Run each candidate against addresses whose true outcome you already know. Your own bounce history is a better benchmark than any published figure, because it reflects your sources and your sending habits.
Build a seeded test set in four groups:
- Known good: addresses that delivered in the last 90 days. Delivery is strong evidence, not proof.
- Known bad: addresses that hard-bounced in your last two campaigns.
- Disposable: addresses from throwaway domains.
- Catch-all: addresses on domains you know accept everything.
Then measure three things:
- Catch rate: the share of known-bad addresses the tool marks Invalid. Higher is better.
- False-positive rate: the share of known-good addresses the tool marks Invalid. Every false positive is a real customer you've stopped emailing.
- Catch-all handling: the share of catch-all addresses marked Risky. Marking them Valid is a fail.
Which error matters more depends on the list. On a cold outbound list, missed bad addresses drive your bounce rate. On a customer list, false positives cost real relationships, so a tool with a slightly lower catch rate but a clearly lower false-positive rate may be the better buy. The email verifier comparison checklist helps you record results side by side.
Bottom line: A back-test on your own bounce history tells you more than any vendor's accuracy claim, and you should weigh false positives and missed bad addresses by what each costs your list.
How do you run a verifier back-test in Unlimited Verifier?
- Build your test file. Create a 300-row CSV with three columns:
email,known_statusandsource. Use 150 delivered, 100 bounced, 25 disposable and 25 catch-all addresses. Label each row accurately. - Create a free account. Sign up for a free account. Free lists are capped at 150 emails, so shuffle the rows and split the file into two 150-row lists. Shuffling ensures each list mixes all four groups.
- 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.
- Read the buckets. Each address lands in Valid, Risky or Invalid. Bounced addresses should mostly land in Invalid and catch-all addresses in Risky. Record where disposable addresses land, because that depends on your policy.
- Export both results immediately as CSV. Free results are kept for 24 hours. Stack the two exports into one sheet before you score them.
- Score with formulas. These assume your result column is D. Check the header in your export and adjust the letter if needed:
- Catch rate:
=COUNTIFS(B:B,"bounced",D:D,"Invalid")/COUNTIF(B:B,"bounced") - False-positive rate:
=COUNTIFS(B:B,"delivered",D:D,"Invalid")/COUNTIF(B:B,"delivered") - Catch-all as Risky:
=COUNTIFS(B:B,"catch-all",D:D,"Risky")/COUNTIF(B:B,"catch-all")
- Catch rate:
- Spot-check surprises. For any address that looks wrong, use the free single-email checker.
- Repeat with your shortlist. Run the same file through each other tool and record the numbers side by side.
Worked example (illustrative results): Suppose Tool A marks 91 of 100 bounced addresses Invalid, and 6 of 150 delivered addresses Invalid. Its catch rate is 91 ÷ 100 = 91%, and its false-positive rate is 6 ÷ 150 = 4.0%. Tool B marks 96 of 100 bounced addresses Invalid, but flags 15 of 150 delivered addresses, a false-positive rate of 10%. Tool B catches five more bad addresses, but for a customer list it would suppress one in ten good contacts. For that list, Tool A is the better buy.
Bottom line: Two hundred and fifty lines of setup and three formulas give you a defensible comparison in under an hour.
What does a verifier cost for a real list?
The number to compare is the cost per 1,000 verified addresses at your real volume. Email verification pricing is easy to misread, because headline plan prices can hide per-list limits, monthly quotas and result-retention windows.
Unlimited Verifier's published plan facts are:
- Free ($0): 25 lists a month, up to 150 emails each, 750 deep verifications a month, no API access, and results kept for 24 hours.
- Pro: $29 a month, or $25 a month billed annually. Unlimited lists of up to 25,000 emails each, 25,000 deep verifications a month, API access covering 100,000 emails a month, and results kept for 30 days.
Standard verification is unlimited on every plan, with no per-email fees.
Cost arithmetic: Pro at $29 a month, used for 12,000 deep verifications, comes to $29 ÷ 12,000 × 1,000 = $2.42 per 1,000 deep-checked addresses. On annual billing at $25 a month, the same 12,000 addresses cost $2.08 per 1,000.
To compare with a per-credit tool, multiply its price per 1,000 deep checks by 12 to get the cost of the same 12,000 addresses, then compare that with $29. Confirm the quote covers the same checks: mailbox, catch-all and disposable flags.
Worked example: a 40,000-contact list
A B2B company has 40,000 contacts, including 12,000 imported from a trade show two years ago. Illustrative plan:
- Dedupe first. Suppose 1,800 duplicates are removed, leaving 38,200.
- Split for the Pro cap. 38,200 exceeds one list's 25,000-email limit, so split it into 25,000 and 13,200.
- Standard verification. All 38,200 are checked with no per-email fee.
- Deep verification for the riskiest segment. The 12,000 trade-show contacts use 12,000 of the 25,000 monthly deep verifications. That leaves 13,000 for re-checks.
- Cost. One Pro month is $29, or $2.42 per 1,000 deep-checked addresses.
Worked example: the Free plan's limits
A 2,000-row list on the Free plan must be split into 150-email lists: 2,000 ÷ 150 = 13.33, so 14 lists. That uses 14 of 25 monthly list slots, leaving 11. One full run fits in the month. A weekly schedule would need 14 × 4 = 56 lists, far beyond the 25 available. The Free plan suits occasional checks, not a weekly routine.
Bottom line: Work out the arithmetic at your real list size, including per-list caps and monthly quotas, before comparing headline prices.
Which verifier fits your use case?
Match your situation to the profile that matters most.
| Your situation | What to prioritise | Start here |
|---|---|---|
| Weekly newsletter | Frequent re-checks at low cost | Best email verifiers for weekly newsletter senders |
| SaaS or ecommerce signups | Checks at the point of entry | Real-time email validation |
| Sales prospecting | Catch-all handling and B2B accuracy | Email verification for sales prospecting |
| One-time legacy cleanup | Bulk accuracy and one clean export | One-time cleanup vs ongoing hygiene |
| Agency managing several clients | Per-list limits and predictable cost | Pro, for lists up to 25,000 emails each |
For SaaS and ecommerce teams, the goal is to stop bad addresses before they reach your database. That is the core of email verification for ecommerce and SaaS. Unlimited Verifier's Email verification API handles single-email checks and bulk batches of up to 10,000 emails per request. API access is included on Pro, which covers 100,000 emails a month. Teams building email verification API and automation workflows call the endpoint from their own code, because Unlimited Verifier has no native integration.
If your B2B list is mostly company domains, expect a large share of catch-all results. Read about Catch-all email verification and set a separate send policy for those addresses.
Unlimited Verifier fits best when your data lives in CSV or Excel files, you want predictable costs as volume grows, and you can work without a native connector. If a connector inside your ESP is a hard requirement, check that against the integration column in the table above.
Bottom line: Match the verifier to where addresses enter your system: signup, import or periodic cleanup.
Should you use one verifier or two?
Most teams need one primary verifier for bulk cleaning. A second tool earns its cost only when your back-test reveals a specific gap, such as a large catch-all share that needs a second opinion. The one-verifier-or-two question covers when the extra spend is justified.
Bottom line: Start with one tool, and add a second only where your back-test shows a clear gap.
What bounce and spam thresholds should your verifier protect?
Verification matters because mailbox providers and ESPs enforce limits. Sources don't agree on one number, and they measure different things:
| Source | Metric | Stated figure | What it tells you |
|---|---|---|---|
| Google's sender guidelines | Spam rate | Keep below 0.10%; avoid 0.30% or higher | Complaints, not bounces |
| Amazon SES documentation | Bounce rate | Review at 5%; pause possible at 10% | Bounces, on SES accounts |
| Our recommendation | Total bounce rate | 2% ceiling; under 1% for first sends | Headroom below platform triggers |
Yahoo also publishes sender requirements, so check its current figures before you set your cut-offs. Platform figures change, so confirm them on the source pages before you rely on them.
Hard bounces follow a standard. The SMTP enhanced status code 5.1.1 means a bad destination mailbox, as defined in RFC 3463. Removing these before you send is the single most effective thing a verifier does for your numbers.
For US senders, the FTC's CAN-SPAM compliance guide sets the legal baseline. Verification sits within email verification compliance and hygiene: it protects deliverability, but it cannot confirm that someone opted in. Treat consent as a separate check.
Bottom line: Use 2% as your bounce ceiling, with spam rates kept well below 0.10%, and treat the verifier as the control that keeps you under both.
What are the most common mistakes when choosing and using a verifier?
- Treating Risky as Valid. A Valid label on a catch-all domain means the server accepts mail for everyone, not that this mailbox exists. Send to Risky addresses last.
- Choosing on a star rating or an accuracy headline. Run the back-test, and ask what ground truth the accuracy figure was measured against.
- Testing on a single source. A sample of recent signups will flatter almost any tool. Your legacy import is where the tool gets tested, so stratify by source.
- Verifying once and forgetting it. Lists decay as people change jobs. Email list maintenance best practices sets out a re-verification cadence.
- Paying twice for the same address. Dedupe before upload, or duplicates consume your list and deep-verification quota.
- Losing results to a retention window. Free results are kept for 24 hours and Pro results for 30 days. Download as soon as each run finishes.
- Re-importing Invalids. Export the Invalid list and suppress it in your ESP before any new send.
- Relying only on your ESP's built-in check. Built-in checks can give you less visibility into why an address failed. Compare the trade-offs in whether to use your ESP's built-in verification.
- Skipping vendor red flags. Vague accuracy claims, missing retention terms and unclear pricing are warning signs. See the red flags when choosing a verification service checklist.
- Mistaking verification for consent. A Valid address can still be unwelcome. Verification handles deliverability, not permission.
Bottom line: Most failures come from misreading Risky results, trusting unverified claims, or letting results go stale.
How we compared (and limitations)
This guide is based on public documentation: vendor product descriptions, Google's and Amazon SES's published sender thresholds, and the RFCs cited above. We have not run controlled tests of any tool, and we have not measured accuracy independently. Vendor descriptions are presented as claims. Unlimited Verifier's 99.5% deep-verification accuracy is the company's stated figure.
The worked-example list sizes, back-test results and percentages are illustrative, not measured results. Plan limits, pricing and sender thresholds change, so confirm current figures before you buy. Your own back-test is the most reliable way to decide, because it uses your data rather than anyone's published claim.
How to act on each verifier result
| Result | What it usually means | What to do |
|---|---|---|
| Valid | Mailbox confirmed by SMTP check | Send normally, first in queue |
| Risky (catch-all) | Server accepts any address, so mailbox is unconfirmed | Send last, in small batches, monitor bounces |
| Risky (role-based) | Shared inbox such as info@ or sales@ | Keep, but do not use for personal outreach |
| Risky (disposable) | Temporary or throwaway domain | Remove from marketing lists |
| Invalid | Syntax error, missing domain, or rejected mailbox | Remove |
| Unknown | Server did not commit to an answer | Retry later or treat as Risky |
Frequently asked questions
Which email verifier do deliverability experts recommend?
Experts generally do not name one universal winner. They recommend choosing a verifier by criteria: a real SMTP mailbox check, separate handling of catch-all and disposable addresses, and accuracy you have tested on your own list. The best tool depends on your list type, volume, and integration needs.
What is an SMTP mailbox check?
An SMTP mailbox check is a verification step where the tool opens a conversation with the recipient's mail server and asks whether the mailbox exists. It does this without sending an email to the recipient. It goes beyond syntax checks, which only confirm an address is well formed.
How do catch-all addresses affect email verification?
Catch-all servers accept mail for any address on their domain, so a Valid result does not confirm that a specific mailbox exists. Experts typically label these addresses Risky and send to them last. Ask any vendor for a sample file showing raw catch-all categories before you trust its summary score.
What bounce rate should I keep my list under?
A common working ceiling is 2% bounces. Google asks bulk senders to keep spam rates below 0.10% and warns against 0.30% or higher. Amazon SES documents review at a 5% bounce rate. Staying under 2% leaves headroom below both thresholds.
Should I trust a verifier's accuracy percentage?
Treat vendor accuracy claims as a starting point, not proof. A useful figure states which addresses were tested, how their true status was confirmed, and the sample size. Run a back-test with addresses whose outcomes you already know before committing to a paid plan.
How do I back-test an email verifier?
Gather a sample of addresses whose delivery outcomes you already know, including past hard bounces and confirmed-good contacts. Run each shortlisted tool on that sample, then compare its Valid, Risky, and Invalid labels against the known outcomes. The tool with the fewest costly misclassifications on your data is usually the better fit.
What does an unknown or inconclusive result mean?
An unknown result usually means the receiving server would not give a clear answer, often because it rate-limits lookups or defers its response. It is not necessarily a tool failure. What matters is whether the verifier retries, flags the address as Risky, or guesses. Prefer tools that flag rather than guess.
Do role-based addresses like info@ or sales@ need to be removed?
Not usually. Role-based addresses often reach a shared inbox, so they are rarely wasted sends. They are poor targets for personal outreach, though. Most senders hold them as Risky instead of deleting them, and decide case by case based on the campaign.
Is syntax checking enough to prevent bounces?
No. Syntax checking only confirms an address follows the formatting rules in RFC 5321. An address such as jane@gmial.com can be well formed and still bounce because the domain or mailbox is wrong. A solid verifier also checks the domain, MX records, and the mailbox itself.
How often should I verify my email list?
Verify new sign-ups at the point of capture, and re-verify older segments before large sends or after long periods of inactivity. Addresses go stale over time, so a list verified once can decay. The right cadence depends on your list growth and how often you mail it.
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.