Article
Should I Use My ESP's Built-In Email Verification?
By Unlimited Verifier Team ·

Summary
Use your ESP's built-in verifier for signup checks, but test it against known bad addresses before trusting it on a full list. If it misses more than 1 in 10 of them, run a dedicated bulk verifier. Built-in checks give a fast pass or fail, which is weaker evidence for purchased or imported lists.Use your ESP's built-in verifier for signup checks, but not as your only check on a full list: test it first, and if it misses more than 1 in 10 known bad addresses, bulk-verify with a dedicated tool.
Built-in checks are designed around the platform's own workflow. They suit a fast yes or no when someone types an address. They are weaker evidence for a list you didn't collect yourself, because a single pass-or-fail flag can't separate catch-all, disposable and role addresses from real mailboxes.
Quick answer
- Keep it at the door. Built-in checks suit signup forms and single-address entry, where a fast answer is enough.
- Don't rely on it alone for a full database cleanup, a purchased or imported list, or a suspension appeal that needs per-category counts.
- Judge it by its miss rate. Test it against addresses you already know are bad. Its headline "valid" percentage tells you less.
- Look for three things: a Valid, Risky and Invalid split, catch-all and disposable flags, and an export you can keep.
- Use a dedicated bulk verifier for full-list audits. Upload and verify your list in Unlimited Verifier, which sorts every address into Valid, Risky or Invalid and exports CSV, Excel or JSON.
For the full buyer's framework, see how to choose an email verifier. This article answers a narrower question: when is the tool your platform already gives you enough, and how do you prove it?
What does "built-in email verification" actually mean?
Built-in email verification is any address check that runs inside a platform you already pay for, such as an email service provider (ESP), a CRM or a sales-prospecting tool. It usually takes one of three forms:
- Inline validation on forms checks syntax and sometimes the domain as someone types. Its job is to stop typos before they're saved.
- Bulk checks inside the platform let you upload or sync a list and get a status for each row.
- Checks attached to contact data run inside an enrichment or finder product and usually consume credits per lookup.
Don't confuse any of these with bounce suppression. Your ESP keeps a record of addresses that bounced when you mailed them. That record is reactive. It only knows about addresses you've already sent to.
The surprise bounces in a purchased or imported list come from addresses you've never mailed, so they never appear in your bounce history. A verifier is meant to predict those.
Also check how each platform labels results. "Invalid" in one tool might mean "hard bounce predicted," and in another "failed syntax only." Platform documentation often doesn't spell this out, so ask the vendor for the definition of each status before you trust it.
Bottom line: Built-in checks come in three forms, and bounce suppression is a record of past failures, not a prediction.
Why does it matter which tool checks my list?
It matters because a verification result is a prediction, and you may later have to defend it. A verifier estimates whether an address will produce a hard bounce, a permanent failure. The classic case is enhanced status code 5.1.1, defined in RFC 3463, which means the destination mailbox doesn't exist.
That's why the SMTP mailbox check matters more than syntax. A check that stops at syntax or domain can confirm that an address is well formed and that its domain has mail servers. It can't confirm that the mailbox exists.
Complaints are the second signal. Google's sender guidelines ask bulk senders to keep user-reported spam below 0.10% and to avoid rates of 0.30% or higher. Bounces and complaints are separate measures, but a stale list tends to raise both.
Our working ceiling is 2% total bounces, with under 1% as the target for re-entry sends. That's our recommendation, not a platform rule. Platforms set their own thresholds, and you can't see all of them in advance.
The practical point is that the check matters less than what you can prove afterwards. A dashboard reading "91% valid" won't help if a reviewer asks how many addresses were invalid, why, and when that run happened. You need a dated, exportable breakdown.
Bottom line: Verification is a prediction you can defend, not a green badge. The output has to be detailed and exportable.
When is built-in verification good enough?
Built-in verification is good enough when the job is narrow, you collected the addresses recently, and the result can be exported. Answer five questions before you decide:
- Name the job. Stopping typos at signup is different from cleaning a list you're about to mail.
- Check the output shape. A pass or fail can't tell you which addresses are risky. You need a middle category.
- Check whether you can export it. Without a dated copy, you have nothing to show a reviewer.
- Run a miss-rate test on addresses with known outcomes (covered below).
- Price it at your real volume, as cost per 1,000 addresses actually checked.
| Option | Typical output | Catch-all, disposable and role handling | Exportable record | Best use |
|---|---|---|---|---|
| Built-in signup check | Pass/fail, or syntax and domain only | Not always shown | Rarely | Blocking typos at entry |
| Built-in bulk check in an ESP or sales tool | Varies by platform | Varies, so check yours | Varies | Routine hygiene, if it passes your test |
| Dedicated bulk verifier, such as Unlimited Verifier | Valid, Risky or Invalid | Catch-all detected; disposable and role addresses flagged | CSV, Excel or JSON export; results kept 24 hours on Free, 30 days on Pro | Full-list audits, imported lists, appeals |
| Free single-email checker | One result per address | Check the tool's output | One address per check | Spot-checking a single contact |
If you're shortlisting dedicated tools, the guide to the best email verification tools is a useful starting point. Which email verifier features actually matter explains what to weigh.
Three gaps rarely close inside built-in tools:
- Catch-all domains accept every address sent to them, so a "valid" result there can't confirm a real mailbox. Hold these back until they're checked. The catch-all email verification page covers this case in more detail.
- International domains differ in how reliably they respond to checks. Ask any vendor for its results on non-English domains. Our international domain guide covers what to test.
- Results retention is often unstated. If a dashboard deletes results after a short window, you can't prove what you cleaned last quarter.
Bottom line: Built-in verification is usually good enough at the door and often not enough for a whole list.
How do you test whether a built-in verifier is accurate enough?
Build a 150-address test set with known outcomes, run it through the built-in tool, and score the miss rate on the known bounces. The headline valid rate is the number to trust least.
Use five groups of 30:
- Recent clean sends: should come back Valid.
- Known hard bounces: should come back Invalid.
- Role addresses such as
info@orsales@: should be Risky, not Valid. - Disposable-domain addresses: should be flagged, not Valid.
- Catch-all addresses on domains you already know accept everything: should be Risky, not Valid.
Role, disposable and catch-all addresses aren't necessarily invalid. But a "valid" result on any of them tells you nothing about the mailbox, so count it as a miss. Here's a hypothetical run, shown to illustrate how to read the results rather than as a measured outcome:
| Group (30 each) | Marked valid | Marked invalid | Right answer |
|---|---|---|---|
| Recent clean sends | 29 | 1 | Valid |
| Known hard bounces | 18 | 12 | Invalid |
| Role addresses | 30 | 0 | Risky |
| Disposable addresses | 27 | 3 | Flagged |
| Catch-all addresses | 30 | 0 | Risky |
The total is 134 of 150 (89%) marked valid, which looks healthy. But the tool caught only 12 of 30 known bounces, a 60% miss rate, and it marked every role and catch-all address as valid.
Here's why the miss rate matters more. Suppose a 50,000-address list contains 1,200 addresses that will bounce (a hypothetical figure). If the tool misses 60% of them, 720 bad addresses still go out: 720 ÷ 50,000 = 1.44% bounce rate. That's above the under-1% re-entry target before you've counted any other problem.
Before you run the test, ask the vendor the questions to ask before buying an email verifier, so you know what each status actually means.
Bottom line: Score the tool on the known-bounce group. If it misses more than 1 in 10 known bounces, don't use it as your only bulk check.
How do I run the head-to-head test in an afternoon?
Set aside about an hour. The result is a go or no-go decision on whether the built-in tool stays in your bulk workflow.
- Export 150 addresses from your ESP. Take 30 recent engaged contacts and 30 from your bounce report. Take the other 90 from role, disposable and catch-all addresses you've already identified.
- Label every row. Add a
known_statuscolumn with values such as Good, Bounce, Role, Disposable or CatchAll. - Run the built-in check on all 150 addresses. Export the results and save the file with today's date.
- Sign up for a free account. The Free plan allows 25 lists a month of up to 150 emails each, so the 150-row test fits in one list.
- Upload your test file as CSV or Excel, up to 10MB. The email column is detected automatically.
- Download the results right away as CSV. Free plan results are kept for 24 hours, so save your own copy.
- Place both results side by side in a spreadsheet. Use COUNTIFS to count how many Bounce rows each tool marked Invalid, and how many Role, Disposable and CatchAll rows it marked Valid.
- Check the disagreements. For any address where the tools differ, run it through the free single-email checker and see which result holds up.
- Decide. If the built-in tool misses more than 1 in 10 known bounces, keep it for signup and move bulk work to a dedicated tool.
For a larger sample, run 500 addresses as four lists of 125. That stays within the Free plan's 25-lists-a-month cap.
Bottom line: The dedicated half of this test runs on the Free plan at $0, and it gives you evidence from your own data that no product page can.
What does built-in verification cost compared with a dedicated tool?
Compare cost per 1,000 addresses actually checked, and only after confirming both tools return the categories you need. A cheap check that returns only pass or fail can cost more in the end, because you'll run a second tool anyway.
Start by converting the unit. Email verification pricing may be quoted per check, per credit or per monthly allowance, so put everything on a per-1,000 basis.
- Built-in (hypothetical): suppose your platform charges $4 per 1,000 checks. That's an illustrative rate, not any vendor's price. A 50,000-address list costs 50 × $4 = $200 per run.
- Unlimited Verifier Pro: $29 a month, or $25 a month billed annually. Standard verification is unlimited on every plan, and Pro includes 25,000 deep verifications a month. If you use all 25,000, that's $29 ÷ 25 = $1.16 per 1,000 deep checks ($1.00 billed annually).
Now apply Pro's limits to a 50,000-address list. Pro lists are capped at 25,000 emails each, so split the file into two lists. Deep verification is capped at 25,000 a month, so deep-check the 25,000 riskiest addresses first (often the imported ones) and run standard verification on the rest. That costs $29 for the month, or $0.58 per 1,000 addresses ($29 ÷ 50), or $0.50 billed annually.
If you need deep checks on all 50,000, you'll need two months of Pro: $58 in total, which works out to the same $1.16 per 1,000 deep checks.
On a per-check model, re-running the same list adds cost each time. On a monthly plan, the question is whether the allowance covers your volume.
Bottom line: At your volume, the unit cost matters less than whether the check gives you the categories and export you need.
Which teams should keep built-in checks, and which need more?
Keep built-in checks where the data is fresh and self-collected. Bring in a dedicated tool wherever the list came from somewhere else. Email verification for ecommerce and SaaS usually falls into three situations:
- Organic signup forms with clean data: keep the built-in check on the form and run a dedicated bulk verification each quarter. The weekly newsletter guide covers cadence.
- Imported, purchased or migrated lists: use a dedicated tool before the first send. Bounce risk concentrates here, and one-time cleanup versus ongoing hygiene call for different workflows.
- Cold outreach and sales prospecting: a built-in check alone is rarely enough, because prospect lists come from many sources. Read the sales prospecting guide, and see how cold email agencies verify their lists.
If your enrichment tool bundles verification, such as the checks inside Apollo's data, judge those results on their own terms. Our review of Apollo's built-in verification walks through what to test.
Bottom line: Where a list came from decides the right tool more than the list's size does.
Does built-in verification satisfy compliance?
No. Verification estimates whether an address can receive mail. It doesn't show that the person agreed to receive it. That gap is the core of email verification compliance and hygiene.
The FTC's CAN-SPAM compliance guide sets the US baseline, including honouring opt-out requests and identifying the sender. A tool that marks an address valid doesn't address either duty. Other regions set their own rules, and Yahoo publishes its own sender requirements for bulk senders.
Keep consent records separately, with the source and date of each opt-in. If a reviewer asks for proof of permission, those records answer the question. A verification report doesn't.
Bottom line: Verification protects deliverability. Consent protects you legally, and only your own records can show it.
How should you combine built-in and dedicated verification?
Use the built-in check at the door and a dedicated bulk verifier before every large send or import. That way you aren't paying twice for the same check on the same address.
- At signup: keep the built-in check, or add real-time email validation to block bad entries before they're saved.
- Before every large send or import: run the full list through a dedicated bulk verifier.
- For automation: see email verification API and automation, then generate a key for the email verification API.
Unlimited Verifier's REST API uses API keys. It supports single-email checks and bulk batches of up to 10,000 emails per request, and Pro includes 100,000 API emails a month. The Free plan doesn't include API access.
Unlimited Verifier has no native ESP, CRM or Zapier integration. Your workflow is either to export a CSV, verify it and re-import it, or to call the API from your own scripts. The list maintenance guide sets out a schedule for doing this.
If you're considering two verifiers on one list, read whether to double-verify with two tools before you commit to the cost.
Bottom line: Check at the door, verify before every big send, and automate only what you can audit.
What mistakes should you avoid?
- Trusting the headline valid rate. A high percentage can hide a poor miss rate on known bounces.
- Testing with only clean addresses. A test set of recent, engaged contacts will always look good. Include known bounces, role, disposable and catch-all addresses.
- Treating "valid" as deliverable on catch-all domains. Those addresses need separate handling.
- Skipping the export. If results disappear after a retention window, you can't prove your cleanup later.
- Treating ESP suppression as verification. Suppression only covers addresses you've already mailed.
- Running the same list through several tools with no reason. Compare two tools on a sample first, and don't pay twice on the full file.
- Accepting a vendor's demo as your evidence. Demo lists are chosen by the vendor. Test on your own list, and check the red flags when choosing an email verification service before you commit.
- Losing suppression history when you switch platforms. Export it first. The switching guide covers the steps.
- Confusing verification with consent. A valid address can still be one you have no permission to email.
- Assuming a clean list stays clean. Last year's results don't describe today's list, so schedule re-checks.
Bottom line: Most of these mistakes come from reading one number as if it answered every question.
How we compared (and limitations)
This article is based on public documentation: RFC 3463 for enhanced status codes, Google's published sender guidance, Yahoo's sender requirements, and the FTC's CAN-SPAM guide. We haven't run controlled tests of any ESP's built-in verifier, and we haven't benchmarked one against Unlimited Verifier. The 150-address matrix and the 50,000-address examples are hypothetical, built to show how to read results and do the arithmetic. The $4 per 1,000 rate is illustrative, not a quoted price.
Unlimited Verifier figures come from the company's published plan details. The company states 99.5% accuracy for deep verification. That is the company's own figure, not an independent benchmark.
Platform features, pricing and retention windows change without notice, so check each vendor's current pages before you decide. Your own miss-rate test on your own data is the most reliable evidence you'll get.
Miss-rate test before you trust the ESP
- Gather 100 addresses you know are bad (past hard bounces, closed mailboxes).
- Run them through your ESP's bulk or inline check.
- Count how many are marked Valid or Deliverable.
- Miss rate = missed / 100.
- Above 10 percent: use a dedicated bulk verifier for full-list audits.
- At or below 10 percent: the ESP check may suit low-stakes lists, but still re-test periodically.
| Result | Action |
|---|---|
| Miss rate above 10% | Bulk-verify with a dedicated tool |
| Miss rate 10% or below | Keep ESP check for signup and low-risk lists |
| No Risky category | Treat as weaker evidence |
Frequently asked questions
Is my ESP's email verification accurate?
Accuracy varies by platform and is not usually published in detail. The reliable way to judge it is to test the tool against a set of addresses you already know are bad, such as past hard bounces, and measure how many it marks as valid.
What is a good miss rate for an email verifier?
This article uses a practical threshold: if a tool misses more than 1 in 10 known bad addresses, it is not strong enough for full-list cleanup. Your own risk tolerance may be stricter, especially for purchased lists.
Does bounce suppression replace email verification?
No. Bounce suppression only records addresses you have already mailed and failed to reach. Verification aims to predict failures in addresses you have never sent to, which is where most surprise bounces come from.
What does a catch-all domain mean?
A catch-all domain accepts mail for any address at that domain, so a server response of accepted does not prove the specific mailbox exists. Good verifiers flag these as Risky rather than Valid.
Why do disposable and role addresses matter?
Disposable addresses are temporary and often abandoned, while role addresses like info@ or sales@ are shared and rarely belong to a single engaged person. Both can hurt engagement even when they technically deliver.
Should I verify addresses at signup?
Yes, inline checks are useful for catching typos and obviously invalid entries before they are saved. They are a quick filter, not a full audit.
What status labels should a verifier return?
Look for at least Valid, Risky and Invalid, plus flags for catch-all and disposable addresses. Ask the vendor to define each label, because one tool's Invalid may mean predicted hard bounce while another's means syntax failure only.
Can I export results from built-in tools?
Many platforms allow limited exports, but you should confirm you can keep per-address results in CSV or similar format. You need that record if you later must justify a cleanup or appeal a suspension.
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.