Article
Questions to Ask Before Buying an Email Verifier
By Unlimited Verifier Team ·

Summary
Before buying an email verifier, ask whether it checks the mailbox via SMTP, how it labels catch-all domains, what it costs at your real volume, what limits apply, and how long results are kept. These answers predict list quality better than a headline accuracy claim. Run a small sample with known outcomes to count false Valids before you pay.Before buying an email verifier, ask whether it checks the mailbox itself (via SMTP) rather than only the domain, how it labels catch-all addresses, what it costs per 1,000 addresses at your volume, what list and file limits apply, and how long results are kept. Those answers predict your results far better than a headline accuracy figure. This guide turns each question into a test you can run before you pay, and it is the detailed companion to our how to choose an email verifier buyer's guide.
Quick answer
- Check the mailbox, not just the domain. A verifier that stops at syntax and MX records cannot tell you whether a specific inbox exists.
- Ask how catch-all domains are labelled. A catch-all result should land in a Risky-type bucket, not Valid.
- Price it at your real volume. Calculate cost from the plan's quotas (deep checks, list caps, re-checks), not the monthly headline.
- Test false Valids, not overall accuracy. Run a sample with known outcomes and count bad addresses labelled Valid.
- Confirm retention and export. If results expire after 24 hours, you must download them the same day.
What does "verified" actually mean in an email verifier?
"Verified" means whatever the vendor's checks actually prove. The checks range from a format test to a live exchange with the recipient's mail server, so ask which ones run before you compare prices.
| Check | What it establishes | What it cannot establish |
|---|---|---|
| Syntax | The address follows the format defined in RFC 5322 | Whether anyone reads the mailbox |
| Domain and MX | The domain exists and has mail servers configured | Whether that domain accepts this particular user |
| SMTP mailbox | The receiving server accepts the recipient, without sending a message | That the mailbox is active or read by a human |
| Catch-all detection | The domain accepts mail for any local part | Which local parts are real |
| Disposable and role flags | Known throwaway providers, or role addresses such as info@ | Intent or consent |
| Engagement and consent | Nothing a verifier can check | Whether the person wants your mail |
The SMTP mailbox check is what separates a real verifier from a syntax checker. RFC 5321 defines the protocol. The verifier connects to the recipient's mail server, issues a RCPT TO command for the address, and reads the reply code, without transmitting a message body. A positive reply means the server will accept mail for that mailbox. A rejection means it won't.
Three things make this harder than it sounds:
- Some servers accept every recipient, so a positive reply proves nothing for those domains.
- Some servers greylist, meaning they temporarily reject a first contact. A good verifier retries rather than calling the address Invalid. Ask how the vendor handles temporary responses.
- Many cloud hosts restrict outbound port 25, so the verifier's own infrastructure determines whether SMTP checks run reliably. Ask how the vendor runs them.
For addresses on non-English or international domains, check coverage separately. See can an email verifier check international domains.
Bottom line: Ask for the exact check list in writing. If a vendor can't name its SMTP check, you may be buying a domain check.
Which buyer questions matter most for my use case?
The same five questions carry different weight depending on what you send and why. Rank them before you open a trial.
| Your situation | Ask first | Why it matters most |
|---|---|---|
| One-time cleanup of a dormant database | Catch-all handling and export format | You process the whole list once, and the labels decide what you mail first |
| Cold outreach or sales prospecting | False-Valid rate and mailbox check | A new sender has little reputation to absorb bounces, so each one counts more |
| Newsletter or ecommerce signup | API access and results retention | You need checks at the point of entry, not a clean-up after the fact |
| Agency managing many client lists | Per-list caps, monthly quotas and cost at scale | Limits set how many files you handle and what each client's cycle costs |
| Regulated or EU/UK data | Data processing terms, sub-processors and retention | Contract terms come before features in a compliance review |
If you are still shortlisting, best email verification tools gives you the field. Use the questions in this guide to choose between the finalists.
Bottom line: Put your situation at the top of the list. A cold-outreach team and an agency should not run the same trial.
Does the tool check the mailbox, or only the domain?
A domain-only check confirms that a company runs mail servers. It cannot confirm that a specific person's inbox exists, and that is what your send depends on. Ask whether the mailbox check runs on every address under standard verification, or only under deep verification.
The two cases fail differently. An address at a healthy domain can pass syntax and MX checks and still bounce because the mailbox was closed when the employee left. Only a mailbox-level check catches that.
Test it: Ask the vendor to show you the reason code for an address whose domain is valid but whose mailbox has been removed. If the answer is simply "domain valid," you are buying a domain check.
To spot-check one address before you commit, the free email checker tests a single address without a list upload.
Bottom line: Confirm the SMTP mailbox check and which tier includes it before you judge any accuracy claim.
How does the tool handle catch-all domains?
A catch-all domain accepts mail for any local part, so a positive mailbox reply tells you nothing about a specific address. A verifier should flag these as uncertain (Risky, or the equivalent), not as Valid. This one rule changes how many addresses you end up mailing.
The share of catch-all addresses varies a lot by audience, and in many corporate B2B lists it is substantial. Measure yours before you buy. Take a 500-row sample and count the catch-all domains. If a fifth of your list is catch-all and the tool calls all of them Valid, you have sent an unchecked segment to your first wave.
Unlimited Verifier detects catch-all domains and sorts results into Valid, Risky or Invalid, so you can isolate the catch-all set and decide how to use it. The catch-all email verification page covers how that step works. For the full decision on whether you need this check, see do I need catch-all verification or just standard checks.
Bottom line: A catch-all result is uncertainty, not confirmation. A tool that rounds it up to Valid is inflating your list.
Do I need standard or deep verification?
Standard verification handles the bulk of a list, and deep verification is for the uncertain tail. Unlimited Verifier separates the two: standard verification is unlimited on every plan, while deep verifications are a monthly quota of 750 on Free and 25,000 on Pro. Ask each vendor what its deeper tier adds over standard checks, because the answer decides whether the quota is worth paying for.
Spend deep checks where they change a decision: catch-all and Risky addresses, high-value accounts, and anything you plan to mail first. Spending them on addresses that have already been classified clearly wastes quota.
Here is the arithmetic on Pro's 25,000 monthly deep verifications:
- Deep-checking a full 60,000-row list would take 60,000 ÷ 25,000 = 2.4 months of quota.
- Deep-checking only the 9,000 uncertain rows takes 9,000 ÷ 25,000 = 36% of one month's quota.
For the quota math behind a one-off clean versus continuous checks, see email verifier for one-time cleanup vs ongoing hygiene.
Bottom line: Standard checks cover the list, and deep checks are a budget for the hard cases. Plan your quota around the uncertain rows.
How are results labelled, and what should I do with "Risky"?
Ask how many outcome categories the tool uses and whether the export shows why an address landed where it did. Valid, Risky and Invalid are the common buckets, but the reason behind each result is what lets you act on it.
| Bucket | Typical reasons | What to do |
|---|---|---|
| Valid | Passed the checks and was not flagged as catch-all, disposable or role-based | Eligible for your first sends |
| Risky | Catch-all, disposable, role-based, or an unresolved server response (confirm the mapping with each vendor) | Hold back, segment, and test a small slice |
| Invalid | Failed syntax, no MX, or a rejected mailbox | Suppress permanently |
"Risky" is a holding bucket, not a discard bucket. Holding these contacts back is a decision about what to mail first, not a verdict that the data is bad. Once your main list has shown stable results, test the best of the Risky segment in a small send.
Unlimited Verifier exports results as CSV, Excel or JSON, so you can filter on the bucket column in a spreadsheet or pipeline. Check in your test export which reasons are included and how each one maps to a bucket. That detail determines how precisely you can segment.
Bottom line: Buy a tool whose buckets map to actions you can take, and whose export shows why each address was sorted.
What is the stated accuracy, and how do I test it myself?
Unlimited Verifier states 99.5% accuracy for deep verification. That is the company's own figure, not an independent benchmark. Ask every vendor the same three questions: what was the sample, what was the ground truth, and how were catch-all and Risky addresses scored?
A single accuracy number hides two different errors:
- False Valid: a bad address labelled Valid. This is the dangerous one, because it becomes a bounce.
- False Invalid: a good address labelled Invalid. This costs you reach, but you can often recover it.
Suppose a tool labels 50,000 addresses Valid and 1% of them are actually bad. That is 500 bad addresses. Mail the full 50,000 and those 500 bounces alone produce a 1% bounce rate. Amazon SES's documentation describes a 5% bounce rate as the point where an account is placed under review, and 10% as a pause risk. Other platforms act at lower levels, and published sources don't agree on one exact figure. We recommend a planning ceiling of 2% total bounces. A 1% false-Valid rate would consume half of that margin before any other bounce occurs.
Don't rely on a vendor's figure. Run your own sample using the trial below. If one tool isn't enough confidence, should I double-verify my email list with two tools explains when a second pass is worth the cost. For other quality signals, see what makes one email verifier better than another.
Bottom line: Judge a verifier by its false-Valid rate on your own known-outcome sample, not by a headline percentage.
What will verification really cost per thousand addresses?
Verification pricing comes in a few models, and each scales differently. Compare them on the same workload, not on the monthly headline. For a general primer, see email verification pricing.
| Pricing model | How cost scales | What to check before you buy |
|---|---|---|
| Per-check credits | Cost rises with every check, including re-checks | Whether re-verifying the same address consumes credits again, and how uncertain results are charged |
| Monthly subscription with quotas | A fixed fee, capped by deep checks, list size or monthly volume | Which quota runs out first for your workload |
| Prepaid bundles | A set price per block of volume | Expiry rules for unused volume |
Unlimited Verifier's published plans, as stated by the company, work like this:
- Free ($0): 25 lists a month, up to 150 emails each, plus 750 deep verifications a month. No API access. That caps a month at 25 × 150 = 3,750 emails.
- Pro: $29 a month, or $25 a month billed annually ($300 a year). Lists of up to 25,000 emails each, 25,000 deep verifications a month, and API access covering 100,000 emails a month.
- Standard verification is unlimited on all plans, with no per-email fees.
To compare any vendor, use this formula:
Cost per 1,000 addresses = monthly fee ÷ (addresses processed ÷ 1,000)
For deep checks alone, Pro at full quota works out to $29 ÷ 25 = $1.16 per 1,000 deep verifications. At only 5,000 deep checks it rises to $29 ÷ 5 = $5.80 per 1,000, so utilisation matters as much as the plan price.
Worked example: a 60,000-row list on Pro
- Split the list into three files within the per-list cap: 25,000 + 25,000 + 10,000.
- Run standard verification on all 60,000 rows. There is no per-email charge.
- Deep-check the 9,000 rows flagged as catch-all or Risky. That uses 9,000 of 25,000 deep checks.
- Total cost: one Pro month at $29.
- Effective cost: $29 ÷ 60 = $0.48 per 1,000 addresses.
Run the same 60,000 rows through another vendor's pricing and include re-checks. Re-checks are where per-credit models often cost more than expected. For agencies running several client lists, which email verifier cold email agencies use compares the cost patterns that matter at that scale.
Bottom line: Price the workflow you will actually run, including re-checks and deep-check quota, and divide by the addresses you process.
What list size, file and API limits apply?
Limits decide whether a tool fits your workflow before price does. Check them against your largest real file, not a sample.
- File upload: CSV or Excel files up to 10MB, with the email column detected automatically.
- List size: Free lists hold up to 150 emails. Pro lists hold up to 25,000.
- API: Single-email checks and bulk batches of up to 10,000 emails per request. API access is not included on Free, and Pro covers 100,000 emails a month.
The 10MB cap is usually hit through extra columns, not row count. Divide the cap by Pro's list limit: 10MB ÷ 25,000 rows ≈ 400 bytes per row. An email column and an ID column fit comfortably. A wide CRM export with dozens of columns can exceed that and be rejected. Export only the email column plus a unique ID, then join results back to your records with that ID.
For the API, the arithmetic is simple. At the 10,000-email batch maximum, 100,000 monthly emails equals 10 full batches. For a broader view of how automated checks fit into your stack, see email verification API and automation. Ask the vendor how rate limits work, and what happens if your quota runs out mid-batch.
Bottom line: Export only the columns the verifier needs, and map your largest file to the per-list and per-request limits before you buy.
How long can I keep my results?
Unlimited Verifier keeps results for 24 hours on the Free plan and 30 days on Pro. Both windows are short enough to change your workflow, so plan downloads around them.
On Free, download results the same day. On Pro, export every batch to your own storage with a date in the filename, because 30 days can pass quickly when a dispute, audit or deliverability review arrives later. Keep both the raw results and the summary counts. Ask the vendor whether original uploads are deleted, and when.
For a re-verification schedule that fits these windows, see email list maintenance best practices.
Bottom line: Treat the vendor's storage as temporary. Your own dated exports are the record you will need later.
Will it connect to my ESP or CRM?
Unlimited Verifier has no native integrations with ESPs, CRMs or Zapier. The workflow is either to export a CSV, verify it and re-import the Valid contacts, or to call the API from your own scripts. Ask every vendor how many manual steps a cycle takes and who owns each one.
For a quarterly cleanup, the CSV route is usually enough, and one operator can handle the export, verification and re-import. For signup forms and CRM entry points, the API is the better fit, because it checks each address before the address enters your system. Teams running email verification for ecommerce and SaaS flows usually need that second pattern. Generate your keys on the Email verification API page, and see real-time email validation for where those checks belong in a signup flow.
If your prospecting platform already verifies addresses, decide whether its checks are enough. Is the email verification built into Apollo good enough walks through that comparison, and email verification for sales prospecting covers how verification fits into outreach.
Bottom line: Without native integrations, your real cost includes the time spent on each export and re-import, so budget for it up front.
Can I trust the vendor with my list?
Email addresses are personal data, so a verifier is a processor of your list. Ask for a written data processing agreement, the locations where processing happens, the list of sub-processors, and the retention and deletion rules. Under the GDPR, processors must act under a written contract (Article 28). The UK's Information Commissioner's Office publishes guidance on the same obligations.
Transparency also helps. Unlimited Verifier publishes its verification engine as open source on GitHub, so you can read how the checks are implemented. Confirm that the hosted service behaves the way the open-source code does, since deployment and configuration can differ.
Verification does not establish consent, and it does not change your obligations for each send. Under the US CAN-SPAM Act, honest headers and a working opt-out apply to every commercial message, whatever your list checks show. For the wider picture, see email verification compliance and hygiene.
Bottom line: Check the contract and data handling before the list goes in, and treat verification as one control in a compliance program, not a substitute for consent.
How do I run a fair trial before I buy?
A fair trial uses your own data with known outcomes, and it tests the false-Valid rate directly. Unlimited Verifier's Free plan is enough for the 1,000-row test below. For the full list of items to confirm, see the email verifier free trial checklist.
- Build a 1,000-row ground-truth sample. Take 500 addresses that hard-bounced with a 5.1.1 code in past sends. That code indicates a nonexistent mailbox under RFC 3463. Take 500 addresses that clicked recently. Use clicks rather than opens, because mail privacy features that preload images inflate open counts. If your history includes catch-all domains, include some in each group, so the total stays at 1,000.
- Split the sample into lists of 150. Six full lists of 150 (900 rows) plus one list of 100 gives seven files, well within Free's 25-list monthly allowance.
- Sign up for a free account.
- Prepare each file with two columns only: the email address and your unique ID. Keep the IDs so you can join results back to ground truth.
- Upload and verify each list. Confirm the email column is detected automatically.
- Run standard verification on all seven lists. Standard checks are unlimited on Free, so the 750 deep checks remain available for the catch-all rows you want to examine more closely.
- Export as CSV the same day. Results are kept for 24 hours on Free.
- Build a 2×2 tally by joining results to ground truth. Count known-bad labelled Valid (false Valid), known-bad labelled Risky, known-good labelled Invalid (false Invalid), and known-good labelled Risky.
- Apply a decision rule. For example, reject any tool that labels more than 5 of the 500 known-bad addresses (1%) as Valid. Treat a 500-row sample as a screen, not statistical proof. A higher false-Invalid rate is a tradeoff you can accept if your recovery process works.
- Repeat on the same 1,000 rows with a second tool, or with the vendor you already use. Disagreements show you where to look. They don't tell you which tool is right.
If the trial answers your questions, how to switch email verification providers explains how to move without losing suppression history.
Bottom line: A 1,000-row test with known outcomes tells you more than any sales demo, and it takes an afternoon.
Common mistakes when buying an email verifier
- Buying on the headline accuracy figure without asking which errors it counts or how the sample was built.
- Letting catch-all addresses default to Valid in the export, then mailing them in the first wave.
- Pricing on the monthly fee alone. Ignoring deep-check quotas and re-check costs is how a cheap plan becomes an expensive cycle.
- Uploading full CRM exports with dozens of columns, and hitting the 10MB cap in the middle of a cleanup.
- Running the trial on your cleanest list. Recent engaged subscribers reveal almost nothing about how a tool handles dead addresses.
- Forgetting the retention window. On Free, results expire after 24 hours, so an unexported run means repeating the work.
- Treating verification as proof of consent. A valid address can still belong to someone who never asked for your mail.
- Switching tools without comparing both on the same rows. Run the bake-off first, then decide.
Bottom line: Most bad purchases come from testing the wrong thing, and most of those mistakes are cheap to avoid before you pay.
How we compared (and limitations)
This guide draws on public documentation: RFC 5321 and RFC 3463, Google's bulk sender guidelines, Amazon SES's published bounce thresholds, FTC and ICO guidance, and Unlimited Verifier's published plan facts and open-source engine. We have not run controlled tests comparing verification vendors, and we have not independently benchmarked Unlimited Verifier's stated 99.5% figure. The trial above is a method you can run on your own data, not a result we are reporting. Vendor pricing, quotas and retention periods change, so confirm them on each vendor's site on the day you buy.
Bottom line: Treat every figure here as a claim to check against your own sample, and let the trial make the decision.
Pre-purchase test plan
- Assemble 200 addresses: 50 known active, 50 known invalid, 50 catch-all domain addresses, 50 disposable or role addresses.
- Run the sample through each trial account.
- Count false Valids (invalid addresses labelled Valid) per vendor.
- Check how many catch-all results are labelled Valid instead of Risky.
- Multiply the plan price by your monthly volume, adding re-check quotas.
- Export one result file and confirm the retention period before paying.
Frequently asked questions
What is the difference between SMTP verification and syntax checking?
SMTP verification connects to the recipient's mail server and asks whether it will accept mail for that address, without sending a message. Syntax checking only confirms the address follows a valid format. A syntax check cannot tell you whether a mailbox exists, so it is far weaker for list cleaning.
How should an email verifier label catch-all addresses?
A catch-all address should be labelled Risky or an equivalent uncertain category, not Valid. The domain accepts mail for any local part, so a positive reply does not prove that the specific mailbox exists. Ask the vendor to confirm this label in writing.
How do I test an email verifier before buying?
Build a sample of addresses whose status you already know, such as known active inboxes and known invalid ones. Run them through the trial and count how many bad addresses are labelled Valid. That false-Valid rate matters more than an overall accuracy percentage.
Why does volume affect email verifier pricing?
Plans often limit deep checks, list sizes, and re-checks, so the monthly headline price may not reflect your real cost. Calculate the cost per 1,000 addresses at your expected volume, including re-verification of older lists.
Do email verifiers store my data?
Retention varies by vendor. Some expire results after a set period, such as 24 hours, so you must export them promptly. Ask how long results and uploaded files are kept, and whether you can delete them on request.
Why do some email verifiers return unknown results?
Mail servers may greylist, rate-limit, or block verification probes, so the verifier cannot get a definitive answer. A good vendor retries temporary responses and reports unknowns clearly instead of guessing Valid or Invalid.
Can a verifier confirm that someone wants my emails?
No. Verifiers check technical signals such as mailbox acceptance, domain configuration, and disposable or role flags. They cannot confirm consent or engagement, so you still need proper opt-in and list hygiene practices.
Do cloud hosts affect SMTP email verification?
Yes. Many cloud providers restrict outbound port 25, which can block SMTP checks. Ask the vendor how it runs these checks reliably and whether it documents its infrastructure approach.
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.