Article

Instantly Lead Verification vs External Verifier: When to Use Each

By Unlimited Verifier Team ·

Flow diagram showing an external email verifier sorting a raw lead list into Valid, Risky and Invalid files before an Instantly campaign launch.

Summary

An external verifier checks your full list before upload and sorts addresses into Valid, Risky or Invalid, while Instantly's built-in checks run on leads already inside the platform. For cold email, running an external pass before launch helps keep your first send near a 2% bounce planning ceiling.

An external verifier checks your whole list before upload and sorts every address into Valid, Risky or Invalid, while Instantly's built-in checks run on leads already inside the platform. For cold email, running the external pass before launch is what keeps your first send near the 2% bounce ceiling we recommend.

Quick answer

What is the difference between Instantly lead verification and an external verifier?

Instantly is a cold email platform that also offers lead-related features, and its verification runs where your leads already live. An external verifier is a standalone service that checks a file you own, whatever its origin. Both can indicate whether an address looks deliverable. The practical differences are when the check runs, what you keep afterward, and whether you can prove the result later.

The two answer different questions. A built-in check asks, "Can I send to this lead in this campaign?" An external pass asks, "Is this list healthy enough to be the database I build on?" Teams that treat those as one question often launch a clean campaign on a list that is quietly decaying. If you're still deciding where verification fits, start with email verification for sales prospecting. For the difference between finding an address and checking one, read email finder vs email verifier.

Instantly's labels, credit use and plan-level behaviour change over time, so this article doesn't assume a fixed feature set. Confirm them in Instantly's current help documentation before you build a process around them.

Bottom line: An in-platform check is a launch-time filter. An external verifier gives you an audit you can keep and move between tools.

Why does the timing of verification matter more than the tool?

Verification does the most good before the first sequence step can fire, because a hard bounce on step one hits your sending reputation immediately. Once invalid addresses are attached to an active campaign, checking and sending run in the same loop, and you lose the chance to decide what to do first.

Do the arithmetic. A 5,000-lead campaign with 4% invalid addresses produces about 200 hard bounces on the first send. A 2% ceiling across 5,000 leads allows 100, so you have overshot before any follow-up step runs. RFC 3463 defines the enhanced status codes behind these failures. Code 5.1.1, for example, means the destination mailbox does not exist.

Sources disagree on the exact threshold. Amazon SES's documentation describes a 5% bounce rate as the point where accounts are placed under review. Other platforms act well below that, especially on a first send to an unproven list. Google's sender guidelines ask bulk senders to keep spam reports below 0.3%, which is a complaint limit rather than a bounce limit, but a list full of dead or unwilling recipients usually breaks both. Our recommendation is to plan for 2% total bounces and aim for under 1% on the first send. Treat that as a planning target, not a platform rule.

Bottom line: Sources disagree on the threshold, so plan for 2% and verify before the first step fires.

How do the two approaches compare side by side?

The in-platform check wins on convenience at launch. The external file wins on evidence and control. Where the Instantly column depends on your plan, we say so rather than guess.

Instantly built-in verification External verifier (Unlimited Verifier)
When it runs Inside the platform, around import or launch (confirm for your plan) On demand, before anything is uploaded to a sending tool
Scope Leads attached to the sending account Any CSV or Excel file, whatever its origin
Output categories Platform status labels; check your account for the exact set Valid, Risky and Invalid, plus catch-all, disposable and role flags
Catch-all handling Confirm how the platform labels accept-all domains Flagged as catch-all, so you can route them to a capped test
Evidence you keep Depends on what the platform lets you export CSV, Excel or JSON export. Free results are kept 24 hours and Pro results 30 days, so save your own files
Cost model Metered against your Instantly plan; check current rates Unlimited standard verification on every plan, with no per-email fee. Deep verifications are capped at 750 a month on Free and 25,000 on Pro
Automation Native to the platform REST API with keys on Pro (100,000 emails a month). No native Instantly integration, so export, verify and re-import, or call the API
Best for Quick checks on small batches at launch Full-list audits and documentation before large sends

The row that matters most is evidence. A status you can't export is one you can't defend in a client review or an ESP appeal. A status that lives only inside one tool can also be hard to carry into the next one.

Bottom line: The platform is convenient at launch. The external file is what you can audit, store and move.

Which leads should you verify where?

Decide by source first. A scraped or purchased list carries far more risk than a list of customers who opted in, so the source determines how much checking it needs. The tool follows from that.

Lead source Recommended first check Why
Purchased or scraped CSV Full external verification, then deep checks on Risky No consent history and no engagement signal, so the risk of dead mailboxes and spam traps is highest
Apollo, Sales Navigator or Clay exports External verification on the exported file A vendor's status label is a starting point, not a bounce guarantee. See how to verify Apollo email lists before sending, Apollo's verified vs guessed statuses, verifying Sales Navigator leads and verifying emails in Clay tables
Leads sourced inside the sending platform In-platform check for small batches, external for large ones Fast to run, but a large batch benefits from a file you can keep
Your own opted-in contacts Periodic external hygiene pass Engagement history lowers risk, so the main job is catching decay
Revived old lists Full external verification plus a capped test Older addresses decay, and some may have been recycled into spam traps

Ecommerce and SaaS teams often mix all five sources in one growth stack, which is why email verification for ecommerce and SaaS works best as a per-source policy rather than a single setting.

Bottom line: Set the policy per source. A list with no consent history needs a full external pass, whichever tool sourced it.

What do Valid, Risky and Invalid mean, and what do you do with each?

Valid means the verifier found evidence the address can receive mail. Invalid means it found evidence the address cannot. Risky means the verifier could not confirm either way. Most of your judgement calls happen in the Risky bucket.

The mailbox check works by starting a mail transaction and asking the receiving server whether it will accept a recipient. That is the RCPT TO step described in RFC 5321. Servers respond differently to these probes. Some accept every address, and some throttle or block verification attempts. That is why results are probabilistic, and why catch-all gets its own flag.

Risky is not one category. Each sub-type calls for a different action:

Risky sub-type What it means What to do
Catch-all The domain accepts every address, so the mailbox can't be confirmed Test in a capped segment, grouped by domain
Disposable Throwaway provider, often a dead end for B2B outreach Exclude from B2B campaigns
Role address (info@, sales@) Usually real but shared, with lower engagement Test separately and expect lower replies
Unresolved The verifier couldn't reach a verdict Deep-verify, then decide

Group catch-all addresses by domain. Catch-all is a property of the domain, so 40 contacts at one company share one decision, not 40. Grouping turns a long Risky file into a short list of company-level choices. Deleting the whole Risky bucket is simpler, but it can remove real buyers. Our catch-all email verification page explains how these results are handled.

Bottom line: Valid and Invalid are decisions. Risky is a set of segments to test, grouped by domain.

What should you do when the two checks disagree?

Treat the stricter result as the one that governs the send, because a bounce on a first send costs more than a missed lead. Disagreements also tell you something: each tool has a different miss rate and false-removal rate.

Bottom line: The stricter result governs the send, and the pattern of disagreements shows which source needs work.

How do you test whether a verifier is accurate for your list?

Test with a sample from your own history, not with a headline accuracy figure. Build a sample where you already know the outcome, verify it with each tool, and measure how each one sorts it. This is the step most teams skip, and it is the only reliable way to compare the best email verification tools on your data. Our buyer's guide to choosing an email verifier lists the questions to ask before you run the test.

  1. Pull 400 known-bad addresses from past campaigns that hard-bounced.
  2. Pull 400 known-good addresses that replied or clicked in the last six months.
  3. Add 200 unknown addresses from a source you have never sent to.
  4. Verify all 1,000 with each tool and record the bucket for every address. Verification doesn't send mail, so this step is safe.
  5. Calculate two numbers. Catch rate is known-bad addresses marked Invalid, divided by 400. False removal rate is known-good addresses marked Invalid, divided by 400.

Suppose, hypothetically, that Tool A marks 340 of the 400 bounced addresses as Invalid. That is an 85% catch rate. It also marks 12 known-good addresses as Invalid, a 3% false removal rate. Tool B marks 310 bad addresses as Invalid, a 77.5% catch rate, and removes 2 good addresses, a 0.5% false removal rate. Tool B protects more of your good leads, while Tool A catches more bad ones. Which trade-off you accept depends on whether a missed bounce or a lost buyer costs you more.

Unlimited Verifier states 99.5% accuracy for its deep verification. That is the company's own figure, not an independent benchmark, so run the sample test before you rely on it. Ask any vendor, including Instantly, how it measures accuracy and on what data.

Bottom line: The right verifier is the one that catches your known bounces with the fewest false removals on your own data.

Worked example: a 12,000-lead cold email list

This scenario is illustrative, and the verification percentages are hypothetical. The limits and prices are real.

An agency exports 12,000 leads for a client and wants three campaigns live next week.

  1. Choose the plan. Free would need 80 lists of 150 emails (12,000 ÷ 150 = 80), but it allows 25 lists a month, or 3,750 emails. Pro's per-list cap of 25,000 lets the whole file go up as one list.
  2. Run standard verification. It is unlimited on every plan, with no per-email fee.
  3. Read the buckets (hypothetical): Valid 8,400 (70.0%), Risky 2,700 (22.5%), Invalid 900 (7.5%). The buckets sum to 12,000.
  4. Project the risk. If the 900 invalid addresses went out unfiltered, they would produce roughly 900 bounces on the first send. That is 7.5% of 12,000, nearly four times the 2% ceiling.
  5. Filter before the sequence. Remove the 900 Invalid addresses before any step is live. The main campaign goes to the 8,400 Valid addresses. At a 2% ceiling, that send can absorb at most 168 bounces (2% of 8,400).
  6. Deep-verify the Risky segment. Checking all 2,700 Risky addresses uses 10.8% of Pro's 25,000 monthly deep verifications (2,700 ÷ 25,000). That leaves 22,300 for other lists that month.
  7. Hold Risky for a capped test. Keep the 2,700 Risky addresses in a separate list. Once the main campaign shows bounces under 1%, send a test to the best-engaged 300, then widen if the rate holds.

Cost. Pro is $29 a month, or $25 a month billed annually. On this one list, the monthly plan works out to about $2.42 per 1,000 addresses (29 ÷ 12,000 × 1,000). If the same plan verifies three similar lists in one month, the cost falls to about $0.81 per 1,000 (29 ÷ 36,000 × 1,000). Three sets of 2,700 Risky addresses (8,100 deep checks) still fit inside the 25,000 cap. The annual rate lowers both figures by roughly 14%. For broader context on email verification pricing, compare cost per 1,000 addresses rather than the monthly fee.

Bottom line: The arithmetic shows why the filter belongs before launch. Standard verification is included, so the real cost is deep checks on the uncertain segment.

How do you run an external verification step by step?

Work through these seven steps in order. Each one produces a decision you can later explain.

  1. Inventory your sources. Label every list by origin, age and how it was collected. If you're choosing where leads come from, the best B2B sales prospecting tools for 2026 comparison is a useful starting point.
  2. Set a launch gate. No list attaches to an active sequence until it has been verified and its Invalid addresses removed.
  3. Run standard verification on the full list. Check syntax, domain, MX records and the SMTP mailbox for every address.
  4. Split the results into three files. Save Valid, Risky and Invalid separately, with the date and source in each filename.
  5. Deep-verify Risky selectively. Spend deep verifications where the decision depends on them, not on every address.
  6. Import Valid only, then test Risky in a capped segment. Watch bounces on every send, and pause if the rate moves toward your ceiling.
  7. Re-verify on a schedule. Verify new sources on arrival and re-check older lists monthly or quarterly. Our email list maintenance best practices guide covers cadence. For batch jobs, see email verification API and automation.

For verification at the point of capture, real-time email validation is the natural next step.

Bottom line: A gate, a three-way split and a capped test turn verification into a repeatable process.

Hands-on tutorial: from a CSV export to a clean re-import

  1. Export the lead list as a CSV from your source. Include the email column and any fields you'll need later, such as company, source tag or last-engaged date. Confirm the export steps for your Instantly plan in its documentation, because they vary. The Instantly pre-launch verification guide covers the launch side.
  2. Clean the obvious problems. Remove blank rows and exact duplicates. Keep the file under 10MB, and split it if it exceeds 25,000 rows, since that is Pro's per-list cap.
  3. Create an account. Create a free account for lists of up to 150 emails each. Use Pro for larger lists, up to 25,000 emails each.
  4. Upload the file. Upload and verify a list by selecting your CSV or Excel file. The email column is detected automatically, so check that it was picked up correctly.
  5. Run standard verification and wait for the job to finish.
  6. Review the three buckets. Open the Risky list and check which flags appear: catch-all, disposable or role-based.
  7. Export all three files as CSV, Excel or JSON, and store them somewhere permanent. Free results are kept for 24 hours and Pro results for 30 days.
  8. Import the Valid file into Instantly as a new lead list. Confirm the imported count matches the Valid count before you attach any sequence.
  9. Suppress the Invalid addresses with whatever suppression or block-list feature your Instantly plan provides, so they can't re-enter through a later import.
  10. Optional: automate. If you need recurring batches, create a key on the Email verification API page. Pro includes API access, and requests can carry single checks or batches of up to 10,000 emails.
  11. Spot-check single addresses with the free email checker, such as a VIP contact that came back Risky.

Bottom line: Export, verify, save the three files, and re-import only the Valid list.

Common mistakes

Bottom line: Most of these mistakes come from sending before verifying, or from losing the evidence afterward.

Can verification tell you whether someone agreed to receive your email?

No. Verification tells you whether an address looks deliverable. It does not tell you whether the person agreed to hear from you. Under US law, the FTC's CAN-SPAM compliance guide sets requirements for commercial email, including accurate headers, a working opt-out and a valid physical postal address. A clean list does not meet those requirements on its own.

Consent also affects deliverability. A list full of people who don't remember opting in will generate complaints even when every address is valid. M3AAWG publishes sender best practices that cover consent and list hygiene together, and they are worth reading alongside your verification workflow.

Keep opt-in records with each list. Email verification compliance and hygiene works only when you can also show where each address came from.

Bottom line: Verification protects deliverability. Consent protects you legally and keeps complaints down, and you need both.

How we compared (and limitations)

This article is based on public documentation: Instantly's general product positioning, Amazon SES's published guidance, Google's sender guidelines, the IETF RFCs cited above, the FTC's CAN-SPAM guide and M3AAWG's best practices. We have not run controlled tests against Instantly's verification or its credit system. Its features, labels and pricing change without notice, so confirm them in its current documentation.

Unlimited Verifier's plan limits, retention windows and export formats come from its published product details. The 99.5% accuracy figure is the company's own stated number for deep verification, not an independent benchmark, which is why the sample test above matters. The worked example's percentages are hypothetical and illustrate the arithmetic, not real results. Verification results vary with list source, age and the mail servers each domain runs, so treat every figure here as a starting point to test against your own data.

Bottom line: Use the frameworks and arithmetic here, then measure with your own list.

Bounce budget worked example

Scenario Leads Invalid rate Hard bounces on first send Within 2% ceiling?
No pre-launch verification 5,000 4% about 200 No (limit 100)
External pass before upload 5,000 0.5% after removing Invalid about 25 Yes

Worked calculation: 5,000 x 4% = 200 bounces, which is double the 100 allowed by a 2% ceiling. Removing Invalid addresses before launch brings the expected first-send bounces inside the limit.

Frequently asked questions

What is the main difference between Instantly lead verification and an external verifier?

Instantly's built-in checks run on leads already inside the platform and act as a launch-time filter. An external verifier checks a file you own before upload and gives you a retained audit of Valid, Risky and Invalid results. Use the external pass to build a clean database and the built-in check as a second look.

Should I verify leads before uploading them to Instantly?

Yes, where practical. Verifying before upload means invalid addresses never get attached to an active sequence, so a hard bounce cannot hit your sending reputation on step one. Keep the verification output as evidence of list quality.

What bounce rate should I aim for in cold email?

This article recommends 2% as a planning ceiling for cold email. Platforms and mailbox providers publish different thresholds, and some act well below high single-digit figures, especially on unproven lists. Treat 2% as a conservative internal target rather than an official limit.

What do Valid, Risky and Invalid mean in email verification?

Valid addresses are likely to accept mail, Invalid addresses are likely to hard bounce, and Risky addresses include catch-all, disposable or role-based addresses whose status cannot be confirmed. Send the main campaign only to Valid addresses and run Risky addresses through a capped test first.

What is a catch-all address and should I email it?

A catch-all domain accepts mail for any local part, so a verifier cannot confirm whether a specific mailbox exists. Hold these in the Risky file and send a small capped test before adding them to the main campaign, watching bounces closely.

Why does RFC 3463 matter for bounce handling?

RFC 3463 defines enhanced status codes such as 5.1.1, which means the destination mailbox does not exist. Reading these codes helps you tell hard bounces from temporary failures, so you can remove bad addresses and avoid repeat sends to them.

Can I rely only on Instantly's built-in verification?

You can use it as a filter, but relying only on it means checks happen at send time with less chance to decide what to do first. Pairing it with an external audit gives you a record you can keep and move between tools if your stack changes.

How often should I re-verify my lead list?

Re-verify whenever addresses are new, changed or sourced from a different place, and before reusing an older list. Email addresses decay over time as people change jobs, so a list that was clean months ago may not be clean now.

Do verification credits in Instantly cost extra?

Credit use and plan-level behaviour change over time. Check Instantly's current help documentation for how verification is billed and limited before building a process around it, since this article does not assume a fixed feature set.

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.