Article
Which Email Verifier Do Cold Email Agencies Use? What the Data Shows
By Unlimited Verifier Team ·

Summary
No public data shows which email verifier most cold email agencies use, because agency stacks are private. The tools that appear most often in published comparisons are ZeroBounce, NeverBounce, Kickbox, Hunter and MillionVerifier. Choose between them by catch-all handling, cost per valid address and workflow fit, tested on your own prospect data.No public data shows which email verifier most cold email agencies use, since agency stacks are private. ZeroBounce, NeverBounce, Kickbox, Hunter and MillionVerifier appear most often in published comparisons, and catch-all handling and cost per valid address should decide between them.
Quick answer
- No published data settles it. Treat any "most used by agencies" list as opinion unless it explains how it was compiled.
- The usual shortlist is ZeroBounce, NeverBounce, Kickbox, Hunter and MillionVerifier. Unlimited Verifier can be added to the same bake-off.
- Decide on three measurable things: how the tool labels catch-all and risky addresses, what a valid address costs you at your volume, and how well results fit your workflow.
- Run your own bake-off on about 1,000 rows of real prospect data. Disagreement between tools tells you more than any review score.
- For Unlimited Verifier, the Pro plan is $29/month, or $25/month billed annually. It includes unlimited lists of up to 25,000 emails each and unlimited standard verification.
Why is there no reliable answer to "which verifier do agencies use"?
There is no reliable public answer because the signals that would show it are weak. Agencies rarely publish their stacks. Vendor logo pages show customers who agreed to be listed, forum posts are anecdotes, and most published lists of the best email verification tools rank by review volume, which reflects who asks for reviews. The G2 and Capterra rankings carry the same bias.
The more useful question is which verifier fits a cold agency's constraints. An agency runs many sending domains, pulls lists from several sources, and serves clients with different tolerance for bounces. A tool that suits one in-house newsletter may be a poor fit for that workload. Our verifier comparison checklist template turns the question into a scorecard you can reuse.
Bottom line: Stop looking for the agency favourite and test against your own constraints.
What does a cold email agency need that a newsletter sender doesn't?
Cold agencies need catch-all visibility, trap awareness, per-list volume control and tight complaint discipline, because cold lists are riskier than opted-in ones. Many cold lists come from scraping, discovery tools or purchased data, so they tend to contain more stale, invented and catch-all addresses than a list people joined themselves.
The difference is consent. A store's signup list is mostly opted in, which is the case covered by email verification for ecommerce and SaaS. A prospect file is not, and that changes what you need from a verifier. If your sends are weekly newsletters to people who signed up, best email verifiers for weekly newsletter senders is a better starting point. For outbound work, the four requirements below matter most. They are also the core of email verification for sales prospecting.
- Catch-all handling. A catch-all domain accepts mail for any address, so a verifier cannot confirm that a particular mailbox exists. The share of catch-alls varies by industry and by country. If your prospects span regions, check how a tool handles international domains. Measure your own share rather than assuming one.
- Spam-trap exposure. Spam traps are addresses that exist to catch senders with poor list practices. ZeroBounce's documentation describes separate statuses for spamtraps and abuse, which gives cold senders more to act on than a single "invalid" label.
- Per-list volume. Lists get divided by client and campaign, so per-list size limits shape how you organise files.
- Complaint discipline. Google's sender guidelines put the line at 0.3% user-reported spam, which bulk senders should not reach, and recommend staying below 0.1%. Some teams treat 0.3% as the ceiling. We recommend 0.1% as the working target, because cold recipients did not ask for your mail and are more likely to report it. Verification helps, but it cannot fix a list nobody consented to.
Bottom line: Cold agencies need catch-all and trap visibility more than a tool that only says "valid" or "invalid."
Which email verifiers do cold email agencies shortlist?
The five tools most often compared are ZeroBounce, NeverBounce, Kickbox, Hunter and MillionVerifier, and each does the core job of checking mailboxes. They differ in how they label results, how they price, and what they are built around, so the table compares those differences rather than rating accuracy. Vendor features and pricing change, so check each vendor's current pages before you buy.
| Tool | How it labels results (per public docs) | Key differentiator | Cons specific to this tool | Strongest fit |
|---|---|---|---|---|
| ZeroBounce | Separate statuses for catch-all, spamtrap, abuse and do-not-mail | Granular codes give you more detail to act on | Each status needs a written rule; a team that treats every non-valid code alike gets little value | Agencies separating trap and abuse risk from ordinary invalids |
| NeverBounce | Valid, invalid, disposable, catch-all and unknown | A familiar valid/invalid focus for bulk cleaning | "Unknown" results aren't resolved in the first pass, so you need a retry or hold-back rule | Teams cleaning large one-off lists |
| Kickbox | Sendex, a 0–1 deliverability score | One tunable number instead of fixed buckets | You set and document the cut-off; two teams with different thresholds get different lists | Agencies that want to set their own risk tolerance |
| Hunter | Verification results alongside email finding and domain search | Combines discovery and verification in one product | If you only clean lists you already have, you may pay for discovery features you won't use | Agencies building prospect lists from scratch |
| MillionVerifier | Deliverability labels; confirm how catch-alls are labelled before buying | Credit-based usage | Monthly cost tracks how many credits your lists consume, so forecast from last month's real list sizes | Agencies with spiky, unpredictable volume |
| Unlimited Verifier | Valid, Risky and Invalid, plus catch-all, disposable and role-address flags | Unlimited standard verification on every plan, with a flat Pro price | No native ESP, CRM or Zapier integration; Pro lists cap at 25,000 emails; results kept 30 days on Pro and 24 hours on Free; no API on Free | Agencies that want predictable cost for large cleaning jobs and a scriptable API |
The cons column matters more than the feature list. Most of these tools do the core job; the differences show up in workflow friction and in how each treats the uncertain middle of your list. Before you narrow the field, work through questions to ask before buying an email verifier. For a wider view, see our tool-by-tool roundup.
Bottom line: Shortlist two or three tools whose result categories match how you plan to act on them.
What should you measure when you compare verifiers?
Three measurements separate a good choice from a convenient one: catch-all handling, cost per valid address, and agreement between tools. Run all three on the same sample, not on each vendor's own demo file. For a feature-by-feature view of which items deserve weight, see which email verifier features actually matter.
1. Catch-all handling. Check whether the tool flags catch-all domains and keeps them separate from confirmed-valid addresses. If a tool labels catch-alls as valid, your bounce rate will rise when you send to them. Hold catch-alls back until the confirmed-valid segment has shown stable results.
2. Cost per valid address. Price per check is the wrong comparison, because what matters is what each usable contact costs. Compare email verification pricing on this basis:
Cost per valid address = price per check ÷ share of the list that comes back valid
A cheaper check that returns fewer valid addresses can cost more per usable contact. The worked example below runs this on flat-fee and per-check numbers. Our email verifier comparison checklist template has a column for each of these measures.
3. Agreement across tools. Run the same sample through two verifiers. Where they disagree, you have found the part of your list that carries risk. A high disagreement rate means the list needs more scrutiny, not that one tool is right.
Bottom line: Judge verifiers on catch-all handling, cost per valid address and agreement, not on headline accuracy claims.
How do you run a verifier bake-off in a week?
A bake-off is a structured test on your own data. It replaces opinion with a few numbers, and it gives you evidence a client can check.
- Build a stratified sample of about 1,000 rows. Draw the same proportions from each source you use, such as scraped, purchased and discovery-tool exports. A sample drawn only from your cleanest source makes every tool look good.
- Run the same file through two or three verifiers. Keep the file identical, and record how long each run takes and what it costs.
- Build an agreement grid. Count how many addresses each tool marks Valid, Risky and Invalid, and note where they disagree.
- Hand-check about 50 disagreements. For each address, check whether the domain accepts mail at all, using the free email checker and your own judgement. Record which tool was closer.
- Run a small test send. Send about 200 confirmed-valid addresses from your primary sending domain, and about 50 catch-all addresses from a separate domain. Track bounces for each group separately. Only send to addresses you have a lawful basis to contact.
- Score the results. Compare cost per valid address, disagreement rate and the bounce rate of each group. Pick the tool that wins on cost per valid address without a higher bounce rate.
For the test group, keep bounces under 2%. Sources differ on the line you must avoid: Amazon SES's documentation describes a 5% bounce rate as its review threshold, but waiting for a platform to act is a poor plan. We recommend 2% as your working ceiling. The one-week timeline is a practical target, not a standard. Most teams need a few days of sending data to judge catch-all results.
Bottom line: A bake-off with a real test send gives you evidence you can show a client, which a review score cannot.
How much does verification cost for a 120,000-prospect month?
Costs for a month like this depend on list caps, monthly allowances and one division. The figures below are illustrative. The plan limits are real.
The scenario: A cold email agency has 120,000 prospects across six client campaigns this month.
Step 1: Split for the list cap. Pro allows lists of up to 25,000 emails each, so 120,000 rows become five files: 25,000 + 25,000 + 25,000 + 25,000 + 20,000. Keep each file tied to one client so results trace back to campaigns.
Step 2: Verify everything. Standard verification is unlimited on every plan, so all 120,000 rows can be checked without per-email fees.
Step 3: Spend deep verification where it matters. Pro includes 25,000 deep verifications a month. Spend them on addresses the standard pass flagged as uncertain, such as catch-alls and unknown results, and keep a reserve for spot-checks.
Step 4: Illustrative results.
- Valid: 85,200 (71%)
- Risky: 10,800 (9%)
- Invalid: 24,000 (20%)
The three buckets total 120,000.
Step 5: Cost. One Pro month is $29.
$29 ÷ 85,200 valid addresses = $0.00034 per valid address, or about $0.34 per 1,000 valid addresses.
Comparison with a per-check tool. Suppose a hypothetical tool charged $0.004 per check. Checking all 120,000 rows would cost $480. At the same 71% valid share:
$0.004 ÷ 0.71 = $0.0056 per valid address
The check agrees: $480 ÷ 85,200 = $0.0056. Plug in real vendor prices and your own valid share, because the ratio is the number to compare, not the sticker price.
The API limit. Pro includes 100,000 API emails a month. Running this 120,000-row month through the API would exceed that allowance, so the CSV route is the practical choice. The email verification API suits ongoing, scripted checks, where it accepts single addresses or batches of up to 10,000 emails per request.
Bottom line: The arithmetic is simple, but only if you respect list caps and monthly allowances when you plan the month.
How should you handle catch-all and risky addresses in cold campaigns?
Hold catch-all and risky addresses out of your first sends, and test them in a separate segment. A catch-all result means the domain accepts everything, so the verifier cannot confirm the individual mailbox.
The mailbox check works by asking the receiving server about a recipient during an SMTP conversation, as described in RFC 5321. A catch-all server accepts any recipient, so a yes tells you nothing about that particular mailbox.
A safe approach looks like this:
- Send confirmed-valid addresses first from your main warmed domain.
- Segment catch-alls into their own list, with the domain recorded.
- Test them in small batches from a separate sending domain, so any damage stays contained.
- Remove role addresses such as
info@andsales@from cold sequences. They often route to shared inboxes that don't welcome cold outreach. - Suppress anything that bounces, then re-verify the segment before the next send.
Consent rules differ by country. In the US, the FTC's CAN-SPAM compliance guide sets requirements such as honouring opt-outs and including a valid postal address. In the UK, the ICO publishes guidance on electronic marketing. Verification improves hygiene, but it does not give you a lawful basis to contact someone. See email verification compliance and hygiene for how the two fit together.
Bottom line: Catch-alls are a testing segment, not a send-now segment.
How do you verify a prospect list in Unlimited Verifier?
Export, verify, keep Valid, suppress Invalid and keep your own copy of the results. A first run takes about 15 minutes. If you are doing a one-time cleanup rather than ongoing upkeep, one-time cleanup versus ongoing hygiene explains how the workflow changes.
- Export your prospect list as a CSV from your discovery tool or CRM. Include the email column and any source or client tag, so you can trace results later.
- Sign up for free if you haven't already.
- Start with a sample. The Free plan allows 25 lists a month of up to 150 emails each, plus 750 deep verifications. Use your first 150 rows to check the workflow.
- Upload and verify a list. CSV and Excel files up to 10MB are accepted, and the email column is detected automatically.
- Let verification run. Each address is checked for syntax, domain, MX records and the SMTP mailbox. Catch-all domains are detected, and disposable and role-based addresses are flagged. For catch-all handling in detail, see the catch-all email verification page.
- Read the three buckets. Valid addresses are safe for first sends. Invalid addresses are suppressed permanently. Risky addresses, including catch-alls, wait for the test segment.
- Export results as CSV, Excel or JSON, and save a copy. Pro keeps results for 30 days and Free keeps them for 24 hours, so your own copy is the audit trail.
- Re-import only Valid contacts into your sending tool as a new list, and add Invalid addresses to its suppression list. Unlimited Verifier has no native ESP, CRM or Zapier integration, so this step is manual unless you script it against the API.
Bottom line: Export, verify, keep Valid, suppress Invalid, and keep your own copy of the results.
Where does Unlimited Verifier fit in an agency stack?
Unlimited Verifier fits best as the cleaning layer of a cold workflow. It gives you a flat, predictable cost for verifying large prospect files, with catch-all, disposable and role flags on every result. Because standard verification is unlimited on every plan, you can re-check a list after fixing it without paying per email. The JSON export works well if your team processes results in its own scripts, and the API covers single checks and batches of up to 10,000 emails.
The limits are equally specific. There is no native ESP, CRM or Zapier integration, so you export and re-import or script the workflow. It verifies addresses but does not find them, so many agencies pair it with a discovery tool. Pro lists cap at 25,000 emails, so larger files need splitting. Pro results are kept for 30 days, and Free results for 24 hours.
Before you decide, check whether your sending platform's built-in checks are enough. Some agencies run a second verifier on a sample or on uncertain results, and our guide to whether one verifier is enough or you should use two covers when the second opinion is worth paying for. For ongoing upkeep after the initial clean, email list maintenance best practices sets out a schedule.
Bottom line: Use Unlimited Verifier as a predictable cleaning layer, and decide separately whether you need a second opinion.
What are the common mistakes cold agencies make with verifiers?
- Choosing by review rank. Review sites reflect who reviews, not which tool fits your lists. Check the red flags when choosing an email verification service before you commit.
- Treating "Valid" as "won't bounce." A valid result is the verifier's judgement at the moment of checking, not a guarantee of delivery. Catch-all results are uncertain by definition.
- Sending catch-alls first. They belong in a test segment, not your opening send.
- Losing the audit trail. Results on Free expire after 24 hours and on Pro after 30 days, so save your own copy.
- Verifying after sending. Verify before the list touches a sending domain. Checks at capture, such as real-time checks at capture, stop bad addresses before they enter the list.
- Ignoring role addresses. Shared inboxes respond poorly to cold outreach.
- Comparing cost per check instead of cost per valid address. The cheapest check can be the most expensive per usable contact.
- Mixing results from several tools without a rule. Decide in advance which tool's verdict wins on disagreements.
Bottom line: Most agency problems come from process gaps, not from the verifier itself.
How we compared (and limitations)
This article is based on public documentation: vendor pages, Google's sender guidelines, RFC 5321, the FTC's CAN-SPAM guide, the ICO's guidance and Amazon SES's published thresholds. We have not run controlled tests on any vendor's accuracy, and we have no access to agency tool stacks. Vendor feature descriptions are as each vendor states them, and prices and features change.
For Unlimited Verifier, the 99.5% accuracy figure is the company's stated figure for deep verification, not an independent benchmark. The worked-example percentages and the hypothetical per-check price are illustrative. Run your own bake-off before relying on any ratio here. For selection criteria beyond this comparison, see our buyer's guide to choosing an email verifier.
Bottom line: Treat this as a method for choosing, not a verdict on which tool wins.
Four-step verifier bake-off
- Pull 1,000 rows of real prospect data, deduplicated and with the same list fed to every tool.
- Run each shortlisted verifier and record valid, invalid, catch-all and risky counts.
- Calculate cost per valid address: total spend divided by addresses confirmed deliverable.
- Review rows where tools disagree, then choose the tool whose labels best match your bounce results on a small test send.
Frequently asked questions
Which email verifier do most cold email agencies use?
No public data reliably shows this, because agency stacks are private and most published lists rank by review volume. Tools that appear often in comparisons include ZeroBounce, NeverBounce, Kickbox, Hunter and MillionVerifier. Test them against your own constraints rather than relying on a popularity claim.
What is a catch-all email address?
A catch-all address is a mailbox on a domain configured to accept mail for any local part, so the server confirms receipt without proving the specific person exists. Verifiers usually label these as risky or catch-all rather than valid. Cold lists often contain many of them, so how a tool labels them matters.
How do I run a bake-off between email verifiers?
Take about 1,000 rows of real prospect data and run it through each shortlisted verifier. Record valid, invalid, catch-all and risky counts, plus the cost per verified row. Disagreements between tools show where their accuracy differs and are more informative than review scores.
What is cost per valid email address?
It is the total verification spend divided by the number of addresses the tool confirms as deliverable. A cheaper per-check price can still cost more per usable contact if it flags many valid addresses as risky. Compare this metric rather than the headline rate.
Should cold email agencies verify catch-all domains?
Verification can flag catch-all domains but cannot confirm a specific mailbox on them. Many agencies send to catch-all addresses carefully, in small volumes, with monitored bounce and complaint rates. The right policy depends on the client's tolerance for risk.
Why do cold lists need more verification than newsletter lists?
Cold lists usually come from scraping, discovery tools or purchased data, so they include more stale, invented and catch-all addresses. Newsletter subscribers have opted in and tend to be more current. Cold outreach therefore needs stricter catch-all handling and trap awareness.
Do email verifiers guarantee delivery?
No. A verifier estimates deliverability using checks such as syntax, domain records and mailbox probing, but it cannot guarantee inbox placement or that a person reads the message. Treat results as a risk reduction step alongside list hygiene and sending practices.
How often should a prospect list be re-verified?
Re-verify before each campaign, especially for lists older than a few weeks, because addresses go stale as people change jobs. Verifying once at import and then sending months later increases bounces. Many teams re-check the most recent sends and any list that has aged.
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.