Article

Red Flags When Choosing an Email Verification Service: 7 Warning Signs

By Unlimited Verifier Team ·

Checklist graphic showing seven red flags to check when choosing an email verification service.

Summary

The seven biggest red flags when choosing an email verification service are unpublished accuracy claims, Valid/Invalid-only results, per-credit billing for unknown outcomes, opaque SMTP handling, unclear data retention, restrictive limits, and vendors who refuse a small test. The fastest way to spot them is to run 500 to 1,000 addresses with known bounce outcomes through each candidate.

Seven red flags matter most when choosing an email verification service: an accuracy figure with no published method, Valid/Invalid-only results, per-credit billing for unknown outcomes, opaque SMTP handling, unclear data retention, limits that break your workflow, and sales teams who refuse a 1,000-address test. Any one of them can cost more in bounces and wasted spend than the subscription itself. The fastest way to spot them is to test a vendor on your own data rather than trust its homepage. For the full selection process, start with our pillar guide on how to choose an email verifier.

Quick answer

What does an email verification service actually check?

A verification service runs several layers of checks, and each one answers a different question. Most red flags come from vendors blurring those layers, so know what each layer can and cannot prove before you compare anyone.

Check What it tells you What it cannot tell you
Syntax The address is well-formed Whether the mailbox exists
Domain The domain resolves Whether this person works there
MX record The domain has mail servers configured Whether the specific mailbox exists
SMTP mailbox check The receiving server's response about the recipient, obtained without sending a message (the dialogue is defined in RFC 5321) Whether a server that stays non-committal holds the mailbox
Catch-all detection The domain accepts mail for any address Whether an individual address is real
Disposable and role flags The address is a throwaway service or a shared inbox such as info@ Whether the person wants your email
Engagement and consent Nothing; verifiers don't see this Whether you are allowed to email them

The last row matters most. A verifier can tell you an address is reachable. It cannot tell you that the person opted in. A "Valid" result is never permission to send cold email.

Bottom line: A verifier answers technical questions about addresses. Treat any vendor that implies more than that as a warning sign.

Why does a bad verifier cost more than its subscription?

A bad verifier's real cost is the bounces it lets through, not its price per email. Each false "Valid" becomes a bounce on your next send, and bounce rate is one of the signals mailbox providers and ESPs watch.

Consider a hypothetical 20,000-address list where a verifier misses 3% of dead addresses. That produces 600 bounces on the first campaign, a 3% bounce rate. Many deliverability teams aim to keep total bounces under 2%, so that single send already breaches their target. Amazon SES's documentation describes a 5% bounce rate as the level that triggers review, so repeated misses like this move you toward a suspension. For the thresholds in detail, see what bounce rate gets your ESP account suspended.

The cheaper tool is not necessarily the cheaper choice. Suppose one vendor charges $3 per 1,000 and another charges $6 per 1,000. On 20,000 addresses, that is $60 against $120, a $60 difference. If the cheaper tool leaves 600 bounces and the dearer one leaves 100, the saving is trivial next to the reputation cost of 500 extra bounces.

Bottom line: Judge a verifier by its false-valid rate first and its price second. Price is easy to see; the false-valid rate is where the real money goes.

What are the red flags at a glance?

Use this table as a checklist during vendor calls. The right-hand column is what a credible vendor will show you, not just say.

Red flag What it looks like What a credible vendor does
Accuracy with no method "99% accurate" with no sample or ground truth Describes its test set and explains how Risky results were scored
Two-bucket output Only Valid and Invalid Separates uncertain addresses into a Risky tier
Per-credit surprises Costs rise with catch-all or deep checks Shows credit cost per check type and bills predictably
Vague SMTP handling "100% confirmation" for every address Explains greylisting, retries and rate limits
Opaque data handling No retention policy in writing Publishes retention periods and deletion steps
Hidden limits Caps you find only after uploading States file size, rows per list and API batch size upfront
Refusal to test Demands payment before any sample run Runs a sample on your data

Bottom line: Any "no" on the right-hand column is a reason to pause, not a reason to negotiate on price.

Is a headline accuracy percentage a red flag?

Yes, when it arrives without a method behind it. An accuracy figure means nothing until you know the sample, the ground truth and how Risky results were counted, and vendors often define those differently.

Ask four questions before you accept any headline number:

  1. What was the sample? Random addresses from the open web behave very differently from addresses drawn from a clean B2B database.
  2. How was the ground truth established? A "correct" result needs an independent outcome to check against, such as a delivered message or a confirmed bounce.
  3. Were catch-all domains included? If they were excluded, the figure describes an easier problem than your list presents.
  4. Were Risky results counted as wrong, right or ignored? A tool that moves hard cases into a separate bucket can post a high score while leaving you with the same uncertainty.

Catch-all domains are where accuracy claims usually break down. If a domain accepts mail for any address, no SMTP check can reliably confirm one specific mailbox. A vendor scoring 99% on a sample with few catch-alls is measuring a narrower problem than most B2B lists present.

For context, Unlimited Verifier states 99.5% accuracy for its deep verification. That is the company's own figure, not an independent benchmark, so treat it as a claim to test in your own bake-off, described below.

Bottom line: An accuracy number is only as good as the method behind it. If a vendor can't describe its method, the number is marketing.

Is a Valid-or-Invalid-only output a red flag?

Yes. A two-bucket output forces every uncertain address into one of two categories, and both choices cause damage. Put catch-all addresses in Valid and you overstate your list's quality. Put them in Invalid and you discard real leads.

A three-bucket output lets you act on each category differently:

Bucket What it usually means What to do
Valid Strong evidence the mailbox exists Send first, starting with your most engaged contacts
Risky Catch-all domain, an inconclusive result, or a flag that needs judgement Hold back, test with a small segment, and decide by engagement
Invalid Permanent failure, such as a nonexistent mailbox or domain Suppress permanently

Unlimited Verifier sorts every address into Valid, Risky or Invalid, detects catch-all domains, and flags disposable and role-based addresses. Check how those flags map to buckets in your own export, because the vendor's category rules determine what your results mean. For more on how catch-alls are handled, read whether you need catch-all verification or just standard checks, or see catch-all email verification.

Bottom line: If a vendor cannot separate uncertain addresses from confident ones, you will either send to dead mailboxes or quietly lose good leads.

Is per-credit pricing a hidden cost?

Often, yes. The sticker rate per 1,000 ignores how many credits each check consumes, and the total bill depends on your list's makeup. When you compare email verification pricing, check these points:

Here is a worked example using a hypothetical rate of $5 per 1,000 credits. Suppose you have a 50,000-address list, and 15% of it sits on catch-all domains, which is 7,500 addresses. Vendor A charges 1 credit for a standard check and 3 credits for a catch-all check.

If you looked only at the headline rate, you would budget 50,000 ÷ 1,000 × $5 = $250. The hidden $75 is a 30% overrun, and it comes entirely from the list's catch-all share.

Now compare a subscription. Unlimited Verifier's standard verification is unlimited on every plan, with no per-email fees. Pro costs $29 a month, or $25 a month billed annually, and includes 25,000 deep verifications a month. To check the same 50,000 addresses, split the file into two lists of 25,000, which is the Pro per-list limit, and run standard verification on both. If you deep-verify only the 7,500 catch-all addresses, you use 7,500 of your 25,000 deep verifications and keep 17,500 for later work.

The shape of the bill matters more than the sticker rate. Confirm any vendor's credit rules before relying on this arithmetic. For a broader view of one-off cleanups versus ongoing checks, read an email verifier for one-time cleanup versus ongoing hygiene.

Bottom line: Work out total cost for your real list, including catch-alls and unknowns, not the price per 1,000 on the pricing page.

How do you spot vague SMTP methodology?

Vague SMTP methodology is a red flag when a vendor promises certainty it cannot deliver. The SMTP check is the most powerful layer and the easiest to misuse. A good verifier does not send messages. It opens a dialogue with the receiving server, reads the response, and handles the hard cases responsibly.

Warning signs include:

Test this yourself. Run the same 200 addresses twice, a week apart. A repeatable method gives nearly identical categories both times, and any differences should cluster in the Risky bucket rather than jumping between Valid and Invalid.

Unlimited Verifier's engine is published on GitHub at github.com/unlimitedverifier/free-email-verifier, so you can read how the checks are coded. Open code does not describe every production setting, though, so ask the vendor to confirm that the hosted service uses the same logic and configuration. You can also run single addresses through the free email checker to see how a result is presented before a bulk run.

Bottom line: Ask how a vendor handles temporary responses, rate limits and unknowns. A tool that can't explain those has not solved the hardest part of the job.

Should you worry about how a verifier handles your data?

Yes. Your list contains personal data, and a verifier that processes it on your behalf is usually a data processor. Under the GDPR, that brings obligations for how the vendor stores, uses and deletes the data. Even outside the EU, these are the questions a compliance reviewer will ask. For more, see email verification compliance and hygiene.

Ask for written answers to these:

Retention varies by plan, so check each tier. Unlimited Verifier's published plan details say results are kept for 24 hours on the Free plan and 30 days on Pro. That difference is practical: on Free, export your results the same day or lose them. The UK's Information Commissioner's Office publishes general guidance on controllers and processors that is useful when you draft these questions.

Bottom line: A vague retention policy is a compliance risk you inherit. Get the retention period, deletion process and processor terms in writing before uploading a real list.

Which limits should you check before you buy?

Check limits before you buy, because a verifier can be accurate and still fail on your file size, row count or integration needs. Compare these against your largest real file:

What to ask Why it matters Unlimited Verifier's published limits
File size and format Large CSVs may fail to upload CSV and Excel up to 10MB, with the email column detected automatically
Rows per list Caps force you to split files Free: up to 150 emails per list, 25 lists a month. Pro: up to 25,000 per list, unlimited lists
Bulk API Single-address calls are slow for big lists Bulk batches of up to 10,000 emails per request
API volume Metered APIs can get expensive Pro includes 100,000 API emails a month; API access is not on Free
Export formats Locked formats make switching hard CSV, Excel or JSON
Native integrations Determines whether syncing is automatic None for ESP, CRM or Zapier; workflows are export-verify-import or API calls

The integration row is a real trade-off. If you need results to sync automatically into your CRM, a tool without native connectors means building that yourself or running a scheduled export-verify-import routine. If your cleaning happens monthly, that routine is often enough. For signup-time checks, see real-time email validation. For scripted workflows, see email verification API and automation and the email verification API setup.

Bottom line: Match limits to your largest real file and your actual process. Splitting files is a workaround, but it should be a planned one, not a surprise at upload.

What sales behaviour should make you walk away?

Walk away from any vendor that refuses to let you test before you pay. The sales conversation reveals as much as the product. These behaviours are warning signs:

Bundled verification deserves its own check. Many sales and contact-data platforms include a built-in verification step. It can be adequate, but it is rarely evaluated separately, so run it through the same test as a standalone tool. Our article on whether the verification built into Apollo is good enough shows how to approach that question. For sales-specific workflows, see email verification for sales prospecting, and for B2B contacts that churn quickly, see email verification for ecommerce and SaaS.

Bottom line: A vendor's willingness to let you test is one of the most reliable signals of whether its product will hold up.

How do you run a bake-off before you commit?

Run a blind bake-off on your own data. Testing against a list whose outcomes you already know is the only way to measure false valids and false invalids, which are the metrics that matter. Shortlist candidates from our roundup of best email verification tools first, then test the top two or three.

  1. Build a labelled sample of 1,000 addresses. Take them from past sends where you know the outcome. Include hard bounces, delivered and engaged contacts, and some addresses on catch-all or unusual domains.
  2. Remove duplicates and record ground truth. Note which addresses bounced and which were confirmed engaged subscribers. Keep this file separate from the vendors' outputs.
  3. Run the same file through each vendor. Use identical inputs and record the category each address receives.
  4. Calculate two rates.
    • False-valid rate = addresses marked Valid that actually bounced ÷ all addresses marked Valid
    • False-invalid rate = addresses marked Invalid that you knew were engaged subscribers ÷ all addresses marked Invalid
  5. Record cost and speed. Note the credits or dollars used and how long each run took.
  6. Score the Risky bucket. Check whether it holds the addresses you would have wanted to hold back, or whether it swallows everything uncertain.
  7. Decide with a simple scorecard. Weight false-valid rate highest, then false-invalid rate, then cost per usable result, then workflow fit.

Here is an illustrative result using two hypothetical vendors on the same 1,000 addresses:

Metric Vendor A (hypothetical) Vendor B (hypothetical)
Marked Valid 640 700
Valid that bounced 14 49
False-valid rate 2.2% (14 ÷ 640) 7.0% (49 ÷ 700)
Marked Invalid 200 180
Invalid that were engaged subscribers 6 3
False-invalid rate 3.0% (6 ÷ 200) 1.7% (3 ÷ 180)
Marked Risky 160 120

Vendor B looks better on raw Valid count, 700 against 640. But its false-valid rate is 7.0%, about three times Vendor A's 2.2%. A high Valid count is a vanity metric if those addresses aren't really deliverable. Vendor A is the safer choice for sending, even though it is more conservative.

You can run a version of this bake-off on Unlimited Verifier's Free plan. Standard verification is unlimited, but Free includes only 750 deep verifications, so you cannot deep-verify all 1,000 addresses. Free also allows 150 emails per list and 25 lists a month. Splitting 1,000 addresses gives six lists of 150 and one of 100, which is seven lists and well within the monthly allowance. Export results the same day because Free keeps them for 24 hours. To begin, sign up, then upload and verify a list. Take the questions to ask before buying an email verifier into the test as your checklist.

Bottom line: Measure false valids on your own labelled data. A vendor's Valid count tells you how generous its labels are, not how accurate they are.

How do you switch away from a bad verifier safely?

Plan the switch before you leave. Export your results in an open format, keep your own suppression list separate, and run the new tool on a sample before migrating everything. The key rule is to keep suppression history, because a new vendor won't know which addresses you already suppressed. Our guide on how to switch email verification providers covers the sequence.

Bottom line: Own your data and your suppression list so you can leave any vendor without losing your history.

Common mistakes when choosing a verifier

Bottom line: Most bad purchases come from judging a verifier on a headline figure instead of testing it on the data you will actually send to.

How we compared (and limitations)

This guide is based on public documentation. Google's sender guidelines advise bulk senders to keep user-reported spam below 0.10% and never reach 0.30%. Amazon SES's documentation describes a 5% bounce rate as the level that triggers review and 10% as the level at which sending may be paused. Sources differ on exact thresholds, so we recommend a total bounce ceiling of 2%, which leaves room below any platform's automated trigger.

We did not run controlled tests against any vendor's review process, and we did not independently measure competitors' accuracy. The hypothetical vendors, bounce counts and per-1,000 rates in this guide are illustrative. Unlimited Verifier's 99.5% deep-verification accuracy is the company's own stated figure. Its plan limits and retention periods come from its published plan details and may change, so check the current pricing page before you buy.

Cost per usable result

Vendor Price per 1,000 Unknown results billed? Usable results Cost per usable result
Vendor A $5.00 No 900 $5.56
Vendor B $4.00 Yes, 1 credit each 800 $5.00 (1,000 credits billed, 800 usable)

Vendor B looks cheaper per email but costs less per usable result only if its unknown rate stays low. Hypothetical figures for illustration.

Frequently asked questions

What is the biggest red flag in an email verification service?

An accuracy percentage with no published method is the biggest red flag. Without knowing how accuracy was measured, the number cannot be compared across vendors. Ask how the test set was built, what counted as correct, and whether catch-all and unknown results were included before trusting any headline figure.

Should an email verifier return only Valid and Invalid?

No. A good verifier should return at least Valid, Risky and Invalid. Catch-all domains and unknown mailboxes cannot be confirmed either way, so forcing them into Valid or Invalid will mislead you. A Risky category lets you decide whether to send, suppress or test those addresses separately.

Is it a red flag if I am charged for unknown results?

Yes, it can be. If you pay a credit for every unknown or timed-out check, your effective cost per usable result rises sharply. Ask the vendor whether unknowns, timeouts and retries consume credits, and calculate cost per usable result rather than the listed price per email.

How do I test an email verification service before buying?

Export 500 to 1,000 addresses from past campaigns where you already know which ones bounced and which were delivered. Run them through the tool, then compare its Valid and Invalid results against those known outcomes. Measure false Valid results first, since they produce the bounces that hurt sender reputation.

Does email verification prove someone wants my emails?

No. Verification only checks technical signals such as syntax, domain, MX records and mailbox response. It cannot confirm consent or engagement. A Valid result means the address is probably reachable, not that the recipient opted in, so cold outreach still needs a lawful basis under rules such as GDPR or CAN-SPAM.

What should an email verifier's data retention policy include?

It should state how long uploaded lists are kept, how and when they are deleted, whether data is used to train models, and which sub-processors handle it. Get these terms in writing and review the data processing agreement before uploading a real customer list.

Why does catch-all detection matter?

Catch-all domains accept mail for any address, so an SMTP check returns a positive response even when the mailbox does not exist. A verifier that does not flag catch-alls can label dead addresses as Valid, which leads straight to bounces and wasted sends.

How many bounces is too many for an email list?

Many deliverability teams aim to keep hard bounces below about 2% per campaign. Bounce thresholds vary by ESP and provider policy, so check your sending platform's documented limits. Repeated high bounce rates can lead to throttling or suspension.

Do I need an API or a bulk upload tool?

It depends on your workflow. Bulk upload suits periodic list cleaning, while an API suits real-time checks at signup forms. Confirm batch size, rate limits, file size caps and export formats match how you actually send before committing.

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.