Article
What Support Should an Email Verifier Offer? A Buyer's Checklist
By Unlimited Verifier Team ·

Summary
A good email verifier should publish how its accuracy is measured, explain every Valid, Risky, or Invalid result, document its API and file formats, state its data-retention policy, and commit to a written first-response time. Support is what lets you defend the verdicts you act on, especially when a result is wrong or a bounce spike hits.A good email verifier should publish how its accuracy is measured, give a reason for every Valid, Risky or Invalid result, document its API and file formats, state its data-retention policy, and offer human support with a stated first-response time, which we recommend as one business day.
Many buyers compare verifiers on price and a headline accuracy figure, and those matter. But they say little about what happens when a result is wrong, a bounce spike hits overnight, or a compliance reviewer asks how your data was handled. Support is what lets you defend the verdicts you act on. When you compare the best email verification tools, score them on support as well as on features.
Quick answer
- Ask how accuracy was measured, not just the number. Find out what the vendor tested against, how big the sample was, and how catch-all domains are scored.
- Require a reason for every Risky result. A verdict without a reason tells you what to delete but not why, which makes the source of the problem hard to fix.
- Check the API docs before you automate. Look for error codes, batch limits and sample code, then test them against your real volumes.
- Get the data terms in writing. Know how long results are kept, how deletion works, and whether you need a data processing agreement under GDPR.
- Set a response benchmark. A written first response within one business day, plus a clear route for urgent sending problems, is a reasonable minimum.
What does "support" mean for an email verifier?
For an email verifier, support means five things: transparency about accuracy, documentation for using the results, clarity on data handling, guidance on compliance, and people who answer when something goes wrong. For many teams, live chat matters least.
The reason is that a verifier's output drives decisions that are hard to reverse. A Valid label can put an address on a campaign that bounces, and a bounce pattern can lead to an ESP review. An Invalid label can remove a real prospect from a sales sequence. If the vendor can't explain its results, you are guessing.
Split support into two layers:
- Pre-purchase support: published methodology, documentation, a way to test on your own data, and clear pricing and retention terms.
- Post-purchase support: response times, help with file and API errors, and help interpreting results during an incident.
Many vendors are strong on one layer and thin on the other, so score both. For the product features that sit beside support, see which email verifier features actually matter. For the wider buying process, start with how to choose an email verifier.
Bottom line: Treat support as the information you need to trust and defend each verdict, not as a chat window.
Why does verifier support matter more than it looks?
Verifier support matters because email verification sits upstream of your sender reputation, and mailbox providers judge that reputation on numbers. Google's sender guidelines set 0.3% as the spam-complaint level bulk senders must not reach, and advise staying well below it. ESPs often act on bounce rates far below that. A wrong verdict repeated across a large list can move your numbers quickly.
Bounces follow a standard too. A hard bounce is a permanent failure, and the enhanced status code 5.1.1 means the destination mailbox does not exist. RFC 3463 defines these codes. If a verifier can't map its results to these conditions, you can't tell whether a Valid label means "the mailbox accepted the check" or "the domain has a mail server."
The mailbox check itself works by asking the receiving server, during an SMTP conversation, whether it will accept a recipient (RFC 5321 describes the protocol). Some servers accept everything, some block or rate-limit probes, and some return ambiguous replies. A verifier that is honest about these cases labels them Risky or unknown. One that forces every answer into Valid or Invalid is hiding its uncertainty.
The most expensive error is a false Valid, because each one is a potential bounce. A false Invalid costs you one contact. Your support questions should focus on how the tool handles the cases where it isn't sure.
Bottom line: Judge a verifier's support by how well you can predict and explain its errors, because bounces hit your sender reputation.
What accuracy information should a vendor give you?
A vendor should tell you what its accuracy figure measures, how it was tested, and how it treats uncertain results. A single headline number without that context is a marketing claim, not evidence.
Ask these questions:
- What was the ground truth? Accuracy against real delivery outcomes means more than agreement with other tools.
- What was the sample size and mix? Ask whether it included catch-all domains, role accounts and disposable addresses.
- Is accuracy reported per category? A tool can be strong on clearly invalid addresses and weak on catch-all domains.
- How are catch-all domains handled? Catch-all servers accept mail for any address, so the mailbox cannot be confirmed. A good vendor flags these as Risky rather than Valid. The catch-all email verification page explains how Unlimited Verifier categorises them.
- How are inconclusive SMTP responses labelled? Ask what happens when a server blocks the check.
- Does standard and deep verification differ? Check whether the figure applies to both.
On the last point, Unlimited Verifier states 99.5% accuracy for deep verification. That is the company's own figure, not an independent benchmark, so treat it as a claim to test. Accuracy also varies by market, so if your list has many non-US addresses, read can an email verifier check international domains before you run your test.
Worked example: a 500-address accuracy test
Build your own labelled test set from your history:
- 250 addresses that hard-bounced in past campaigns (known bad).
- 250 addresses that clicked a campaign in the last 90 days (known good, as a practical proxy).
Use clicks rather than opens. Apple Mail Privacy Protection pre-loads images for many users, which makes opens an unreliable signal.
Suppose a vendor returns the results below. The numbers are hypothetical and for illustration only.
| Your known label | Valid | Risky | Invalid |
|---|---|---|---|
| Known bad (250) | 5 | 14 | 231 |
| Known good (250) | 241 | 6 | 3 |
- False-Valid rate on known-bad: 5 ÷ 250 = 2%.
- False-Invalid rate on known-good: 3 ÷ 250 = 1.2%.
- Risky share overall: (14 + 6) ÷ 500 = 4%. If your real list shows a similar share, your Risky-handling process matters as much as the verdicts.
Apply a 2% false-Valid rate to a list with 4,000 dead addresses, and about 80 would still land in the Valid bucket. That is the number to weigh, not the headline accuracy. If two verifiers disagree on the same addresses, is one email verifier enough or should I use two explains when a second opinion is worth paying for.
Bottom line: Ask for the method, the sample mix and the per-category results, then test on a sample you labelled yourself.
What documentation and API help should you expect?
Good documentation lets an engineer integrate the tool in an afternoon and lets an operations person understand each response. Look for an API reference that covers authentication, request limits, batch size, error codes and response fields, plus sample code in the languages your team uses.
Unlimited Verifier's REST API uses API keys and supports single-email checks as well as bulk batches of up to 10,000 emails per request. API access is included on the Pro plan, which covers 100,000 emails a month, and is not included on Free. You can set up keys on the email verification API page. If you plan to check addresses at the point of sign-up, the real-time email validation guide covers the workflow. For how verification fits into automated systems, see email verification API and automation.
Ask these before you automate:
- What does an error response look like, and what should a retry do?
- Are there rate limits, and how do they behave on large runs?
- Which response fields are stable across versions?
- Are there sample scripts for CSV batching, and how should timeouts be handled?
Note what isn't in Unlimited Verifier's facts: there are no native ESP, CRM or Zapier integrations. Most teams therefore use one of two patterns: export a CSV, verify it, and re-import the Valid contacts, or call the API from their own scripts. If your ESP offers its own checker, should I use my ESP's built-in email verification sets out the trade-offs.
Worked example: a 60,000-contact audit on Pro
Suppose you have 60,000 contacts to verify.
- File upload: each list can hold up to 25,000 emails. That's 25,000 + 25,000 + 10,000, so three lists.
- API: 60,000 ÷ 10,000 = 6 requests. The 100,000-email monthly allowance covers the run, with 40,000 left over.
- Deep verification: the Pro plan includes 25,000 deep verifications a month. Deep-checking all 60,000 would need 60,000, so you would deep-check the riskiest 25,000 (for example, imported or old records) and run standard verification on the rest. Standard verification is unlimited on every plan.
Check file size as well. The upload limit is 10MB, and 10MB ÷ 25,000 rows is roughly 400 bytes per row. If your rows carry long notes or many engagement fields, the file size limit can bind before the 25,000-row cap. Trim the export to the email column plus the one or two fields you need for segmentation.
Bottom line: Judge documentation by whether a developer can run your real volumes without contacting support.
What data-handling and privacy support is non-negotiable?
Your verifier holds personal data every time you upload a list, so you need written answers on retention, deletion and processing. Email addresses are personal data under the GDPR text, and Article 28 requires a written contract with any processor that handles that data for you.
Ask for:
- Retention periods. Unlimited Verifier's stated facts are that results are kept 24 hours on the Free plan and 30 days on Pro. Export within that window and keep your own copy.
- Deletion on request. Confirm how to request deletion and how long it takes.
- A data processing agreement. Required if GDPR applies to you, and worth asking for even if it doesn't.
- Sub-processors and data location. Ask which third parties touch the data and where it is processed.
- Secondary use. Your list should be used to verify your list, not to build a product or train models, unless you agree to it in writing.
If you later move providers, keep your suppression history. How to switch email verification providers covers how to carry that history across.
Bottom line: Get retention, deletion and processing terms in writing before the first upload.
What compliance guidance should a verifier give?
A verifier should be clear about what verification does and doesn't prove. A Valid result tells you a mailbox is likely to accept mail. It does not tell you the person opted in.
That distinction matters for the rules you must follow. The FTC's CAN-SPAM compliance guide covers opt-out and identification requirements for commercial email in the US. Consent and lawful-basis rules come from the regulator in your market. A verifier can't supply consent records, but it should say so plainly.
Good compliance support includes documentation that explains what each check does, a note on how catch-all and disposable addresses are flagged, and a clear retention policy. The wider picture is in email verification compliance and hygiene.
Bottom line: A verifier that implies verification proves consent is overstating what it does. Walk away from that claim.
What human support should you expect, and how fast?
You should expect a named support channel, a written first-response target, and an escalation route when a live problem affects your sending. No published industry standard sets these times, so the one-business-day figure is our recommended benchmark, not a sourced norm.
| Criterion | What good looks like | Red flag |
|---|---|---|
| Published support hours | Stated hours and time zone | Hours that appear only on a sales call |
| First response | Written, within one business day (our benchmark) | No stated target |
| Incident handling | Same-day acknowledgement when a bounce spike threatens a suspension | Routed into the billing queue |
| Escalation path | A named route for urgent sending problems | Only the standard contact form |
| Written answers | Replies you can forward to a compliance reviewer | Verbal assurances only |
Support matters most during a suspension, when a reviewer wants a clear account of your cleanup. Your verifier's written answers become part of that evidence, so save them.
Test the response before you commit. Send a pre-sales question about retention or catch-all handling, then time the reply and read it closely.
Bottom line: A written, timed first response is the cheapest test of support quality, and it costs you only an email.
How do you test a vendor's support before you pay?
To test a verifier's support before paying, run a short, structured trial that checks accuracy, documentation, data terms and response time together. The whole process takes about an afternoon.
- Send three pre-sales questions in writing: how catch-all domains are categorised, how long results are kept, and whether you can get a data processing agreement. Record the response time and the quality of each answer.
- Build a labelled test set of about 500 addresses, split between known bounces and recent clickers, as in the worked example above.
- Run the test on the Free plan. Free allows 25 lists a month of up to 150 emails each, plus 750 deep verifications, and no API access. Split 500 addresses into four lists of 125. If you run them as deep verifications, that uses 500 of the 750 available.
- Export results the same day. Free results are kept 24 hours, so download the CSV, Excel or JSON file before the window closes.
- Score the output. Calculate your false-Valid and false-Invalid rates as shown earlier, and check that every Risky result has a reason.
- Read the documentation for the endpoints you would use, and note any gaps.
- Compare the scores against the table in this article, and factor in email verification pricing. A cheaper plan with no written response target can cost more during an incident.
Start with the free email checker to spot-check individual addresses. For the full test, create an account and upload your sample on the upload and verify a list page. The questions to ask before buying an email verifier guide has a longer list to work through.
Bottom line: A small, labelled test tells you more about a verifier's support than any feature page.
Which support matters most for your use case?
The support that matters most depends on how you use the verifier. A one-time cleanup needs clear results and a good export. An ongoing program needs API documentation and a retention policy you can plan around. An agency with many clients needs separate files per client and written data terms.
| Use case | Support that matters most | Concrete check |
|---|---|---|
| One-time cleanup | Accuracy disclosure and export formats | Run a labelled sample and confirm CSV or Excel exports |
| Ongoing hygiene | API docs, batch limits and retention | Map monthly volume to the API allowance, and set a re-verification schedule |
| Sales prospecting | Risky-result handling and role-address flags | Check how role and catch-all results are labelled |
| Agencies with many clients | Separate files per client and written data terms | Confirm each client's results can be kept apart |
| Ecommerce and SaaS | Signup-time checks and retention for churned users | Confirm the API can handle signup volume |
For a deeper look at each pattern, read email verifier for one-time cleanup vs ongoing hygiene, email verification for sales prospecting and email list maintenance best practices. Ecommerce and SaaS teams can also look at email verification for ecommerce and SaaS.
Bottom line: Match the support checklist to your use case, rather than buying the option with the longest feature list.
Common mistakes
- Judging support by the sales demo. Test the written support channel yourself.
- Accepting one accuracy number. Ask what it measures, then test it on your own labelled data.
- Ignoring Risky results. A high Risky share tells you something about your list. Ask how the vendor defines the category.
- Missing the retention window. Exporting after results expire means re-running the job and paying for it again.
- Assuming integrations exist. Confirm the workflow you need, whether that is CSV re-import or API calls.
- Treating verification as consent. A Valid address is not an opted-in address.
- Skipping data processing terms when you handle EU or UK contacts.
- Testing on a list you can't label. Without known-good and known-bad examples, you can't measure false Valids.
For a broader set of warning signs, see red flags when choosing an email verification service.
Bottom line: Most support failures are predictable, and a short written test catches many of them before you pay.
How we compared (and limitations)
This article is based on public documentation: Google's sender guidelines, the enhanced status-code definitions in RFC 3463, the SMTP protocol in RFC 5321, the GDPR text on processors, and FTC guidance on CAN-SPAM. We have not contacted any vendor's support team, so we make no claims about response times for any provider, including Unlimited Verifier.
The Unlimited Verifier details come from the company's published plan facts: result retention, plan limits, API batch size and the 99.5% deep-verification figure, which the company states itself. The worked-example percentages are hypothetical. Support policies, pricing and retention windows change, so check each vendor's current terms before you buy.
Bottom line: Verify every support claim yourself, starting with a written question and a labelled test.
What support should explain for each verdict
| Result | What support should explain | Why it matters |
|---|---|---|
| Valid | The basis for the verdict | Confirms the address is reasonable to send to |
| Risky | The specific reason, such as catch-all or full mailbox | Shows whether to suppress, retest, or accept risk |
| Invalid | The failure type, such as no mailbox or no domain | Shows what to remove and why |
Frequently asked questions
What is a catch-all domain in email verification?
A catch-all domain accepts mail for any address at that domain, so a verifier often cannot confirm whether a specific mailbox exists. Good support tells you how catch-all addresses are scored, usually as Risky, and whether they are excluded from Valid counts. Ask for that rule in writing before you rely on the results.
Do I need live chat from an email verifier?
Live chat is rarely the most important support feature. Most teams benefit more from published methodology, complete documentation, and a written response within one business day. Live chat helps only if the vendor also gives clear answers and escalation paths during a sending incident.
What should a Risky result reason include?
A useful reason names the specific condition, such as a catch-all domain, a full mailbox, a role address, or a temporary server error. That detail tells you whether to suppress the address, retest it later, or accept some risk. A bare Risky label gives you no way to fix the cause.
How do I test an email verifier before buying?
Run a sample from your own list, ideally a few thousand addresses with known outcomes, and compare results against your past bounce data. Check whether the vendor explains each verdict and how it handles catch-all domains. Ask support to review any results that look wrong before you commit to a plan.
What data terms should an email verifier provide?
Ask how long results and uploaded lists are stored, how deletion requests are handled, and where data is processed. If you are subject to GDPR, ask whether the vendor offers a data processing agreement. Get these terms in writing before you upload customer data.
Is a data processing agreement required for email verification?
Whether you need a data processing agreement depends on your role and your jurisdiction, so check with your legal or privacy team. If you send personal data to a vendor that processes it on your behalf, GDPR generally expects a written agreement. Ask the vendor whether it provides a standard one.
What should I do if a verifier's results cause bounces?
Report the affected addresses to support with sample results, timestamps, and bounce codes. A good vendor will investigate, explain the cause, and tell you whether re-verification or a credit is available. Keep a record of the exchange, since it helps if your sending reputation is reviewed.
What API documentation should an email verifier offer?
Look for a full list of result codes, error codes, rate and batch limits, sample code in common languages, and a sandbox or test mode. Good documentation also explains timeouts and retry behavior. Test these details against your real volumes before you automate any workflow.
Should an email verifier have a service-level agreement?
A written service-level agreement is useful for teams that depend on verification in real time, because it sets uptime and response targets. For smaller senders, a clearly published response time and status page may be enough. Ask what remedies apply if the vendor misses its commitments.
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.