Article
How to Verify Leads Instantly Before Launching: A Practical Pre-Send Workflow
By Unlimited Verifier Team ·

Summary
To verify leads instantly before launching, upload your list to a bulk verifier, delete every Invalid address, and hold Risky addresses back until a small test confirms them. Aim for hard bounces under 2% on a cold launch and under 1% for the first wave. The check fits between list building and sending, so you have a categorized file to act on before any email goes out.To verify leads instantly before launching, upload the list to a bulk verifier, delete every Invalid address, and hold back Risky ones until a small test proves they are safe, keeping hard bounces under 2%. This is the launch step of email verification for sales prospecting. "Instantly" does not mean one click. It means the check fits between building the list and pressing send, so you have a categorized file to act on before any email goes out.
Quick answer
- Verify the full segment shortly before every launch. A list that was clean last quarter can decay as people change jobs.
- Sort every lead into Valid, Risky or Invalid. Delete Invalid, send Valid first, and hold Risky back.
- Target under 2% hard bounces on a cold launch, with under 1% for the first wave.
- Test on Free, launch on Pro. Free covers lists of up to 150 emails; Pro covers lists of up to 25,000 at $29 a month, or $25 a month billed annually.
- Export results the same day on Free. Free results are kept for 24 hours; Pro results are kept for 30 days.
What does "verify leads instantly before launching" actually involve?
It means running a pre-send check on the full segment and getting a per-address verdict early enough to edit the list before anything is mailed. The check covers whether the address is well-formed, whether its domain can receive mail, whether the mail server exists, and whether the mailbox appears to accept mail.
There are three practical modes:
- Single-address check for one lead, such as a form fill or a VIP contact.
- Bulk file check for a prospecting list you are about to launch.
- API check for automated pipelines, where enrichment output flows straight into verification.
In practice, the slow part is usually the export-and-import loop, not the check. Mangled CSV columns, duplicate rows and results that never reach the sending tool cause more launch problems than verification does. Design the loop before you design the check.
Bottom line: Instant verification is a workflow. Plan the export, check and re-import steps before you plan the check itself.
Why do leads bounce even when they came from a paid database?
Leads bounce for four main reasons: people change jobs, enrichment tools guess addresses, some domains accept any address, and data gets typed in by hand. Each produces a different failure pattern, so each needs a different check.
- Job changes. B2B contact data decays steadily. A mailbox that was active when the record was created may be closed months later.
- Pattern-guessed addresses. Some tools build addresses like
first.last@company.comfrom a name and domain. A guess can look right in a spreadsheet and still fail at the server. Our guide to Apollo verified vs guessed email status explains how to read those labels, and email finder vs email verifier explains why a finder's output still needs checking. - Catch-all domains. Some mail servers accept mail for any address, so a bounce cannot be ruled out in advance.
- Typos and manual entry. A missing dot or a mistyped domain fails the same way a closed mailbox does.
A hard bounce is a permanent failure. The classic case is SMTP enhanced status code 5.1.1, meaning the destination mailbox does not exist, as defined in RFC 3463. Each hard bounce tells the receiving provider that you mailed an address that never agreed to hear from you.
A "verified" label from a data source only shows that the source checked something at some point. It does not show what the address looks like today.
Bottom line: A database export is a snapshot of a list that is already decaying. Verify it at the point of sending.
What bounce rate should a pre-launch list hit?
Aim for a total bounce rate of 2% or less, and under 1% for the first wave of a new list. Sources disagree on exact thresholds, so use one conservative number and build the process around it.
- Amazon SES describes review at a 5% bounce rate and possible pausing at 10%, in its documentation.
- Google's sender guidelines ask bulk senders to keep the user-reported spam rate below 0.3%. That is a complaint metric, not a bounce metric, but a poor list usually produces both.
- Yahoo's sender requirements describe similar expectations for bulk senders. Check the page for current figures.
Platforms do not publish how they weigh bounces against complaints, and a launch can attract review well before any published limit. Our recommendation is a 2% ceiling. On a 6,000-lead launch, that means no more than 120 bounces; a 1% target means 60. For context on what cold senders typically see, read our average cold email bounce rate benchmarks.
Bottom line: Treat 2% as the ceiling and 1% as the goal for the first wave. Do not plan around the platform's limit.
Which verification method fits your launch?
Use a bulk upload for a prospecting list, a single-address check for one high-value lead, and the API for leads that arrive automatically.
| Method | Best for | Turnaround | What you get back | Main limitation |
|---|---|---|---|---|
| Free email checker | Spot-checking one VIP or ambiguous address | Immediate, one address at a time | One verdict | Not built for lists |
| Bulk CSV or Excel upload | Pre-launch prospecting lists | Depends on list size | Valid, Risky or Invalid per row; export as CSV, Excel or JSON | Results are a snapshot, so re-run before reusing the file |
| Single-email API check | Form fills and inbound leads | Real-time, per request | One verdict your system can act on | Requires API access, which is a Pro feature |
| API batch (up to 10,000 per request) | Enrichment output and automated pipelines | Per request | Batch verdicts you parse in code | Needs developer time to build and maintain |
| Built-in check in a cold-email platform | Teams that want one tool for everything | Varies by platform | Platform-specific status labels | Categories and export options vary, so confirm you can export raw results |
For a comparison of platform checks, see best cold email tools with built-in verification. For the wider market, see the best email verification tools.
Bottom line: Pick the method by how the lead arrives. Lists get bulk checks, single leads get single checks, and automated flows get the API.
How do you verify a lead list before launching?
Use a seven-step framework: freeze the segment, clean the file, verify in one pass, sort the results, set a written Risky policy, check freshness, and launch in waves. Each step produces evidence you can review before sending.
- Freeze the segment. Name the file with the campaign and date, such as
saas-cfo-uk-2025-03-12.csv. If you edit the file after verifying it, the results may no longer match the rows you send to. - Clean the file. Trim spaces, lowercase addresses, and remove exact duplicates. Remove unsubscribes, past complaints and anyone who should not receive cold outreach. Duplicates inflate list size and can make one bad address count twice.
- Verify in one pass. Keep each file within your plan's per-list limit: 150 emails on Free, 25,000 on Pro. Split larger lists first.
- Sort into three buckets. Valid is ready. Invalid is removed and suppressed. Risky is held for a decision.
- Write a Risky policy before you see results. Decide who gets Risky addresses, when, and what bounce rate ends the test. Deciding after the results arrive invites bias.
- Check freshness. If a verified file is older than about 30 days, re-verify it before sending. This is a practical rule of thumb, not an industry standard.
- Launch in waves and read each one. Send to your most engaged Valid contacts first, and check the bounce rate before releasing the next wave.
Each step prevents a specific failure. Skipping suppression means mailing people who already opted out. Skipping the Risky policy means deciding under pressure. Skipping waves means discovering a problem only after the full list has gone out.
Bottom line: Verify once, sort the results, and release the list in waves under a written rule for Risky addresses.
What should each verdict trigger?
Each verdict needs a different action. The table below sets out what to do with each one before launch.
| Verdict | What it usually means | Action before launch | Why |
|---|---|---|---|
| Valid | The address passed the checks and appears to accept mail | Send in waves, most engaged contacts first | Lowest bounce risk, so it builds early delivery evidence |
| Risky | Catch-all, disposable, role-based, or inconclusive | Hold back; test a small sample; release only if the test is clean | The verdict cannot confirm that this specific mailbox exists |
| Invalid | The address failed a syntax, domain, MX or mailbox check | Remove it and add it to your suppression list | Mailing it is a known bounce that damages your sender reputation |
Bottom line: Valid goes out first, Risky waits for a test, and Invalid never gets sent.
How do you verify leads in Unlimited Verifier?
Export the list as a CSV, upload it, read the three buckets, export the results, and re-import only the Valid contacts. Run time depends on list size, so test a sample first to see how long a full file takes.
- Export the list as a CSV. Include the email column and one identifier, such as company or name, so you can recognize rows later. Keep your own copy of the original file.
- Clean the file first. Trim spaces, lowercase addresses and remove duplicates. Clean input makes the report easier to act on.
- Sign up for a free account. The Free plan allows 25 lists a month of up to 150 emails each, plus 750 deep verifications a month. Start with a sample of your list.
- Upload and verify a list. CSV and Excel files up to 10MB are accepted, and the email column is detected automatically. Confirm that the detected column is the right one.
- Wait for the run to finish, then read the counts. Each address is checked for syntax, domain, MX records and the SMTP mailbox. Catch-all domains are detected, and disposable and role-based addresses are flagged.
- Export the results immediately. Export as CSV, Excel or JSON. Free results are kept for 24 hours and Pro results for 30 days, so download on the same day if you are on Free.
- Build your send files. Put Valid contacts into the launch file. Add Invalid addresses to your sending platform's suppression list. Place Risky addresses in a separate held segment.
- Re-import only the Valid file. Unlimited Verifier has no native integrations with ESPs, CRMs or Zapier, so the re-import is manual, or you can call the API from your own scripts.
- Handle single leads and automation separately. Use the free email checker for one-off checks. For automated flows, the Email verification API is available on Pro, with batches of up to 10,000 emails per request and 100,000 API emails a month.
Bottom line: Test a 150-row sample on Free, then run the full list on Pro. Export your results before the retention window closes.
How much does pre-launch verification cost per 1,000 leads?
Cost per 1,000 depends on how many leads you verify in a month, because the Pro plan is a flat monthly fee. Standard verification is unlimited on every plan, and deep verifications are capped at 750 a month on Free and 25,000 on Pro. Check the current documentation to see which checks fall under standard and which under deep verification.
- Free: $0. The maximum is 25 lists of 150 emails, or 3,750 emails a month.
- Pro, monthly billing: $29 a month. Verifying 6,000 leads costs $29 ÷ 6,000 × 1,000 = $4.83 per 1,000. Verifying 25,000 costs $29 ÷ 25,000 × 1,000 = $1.16 per 1,000.
- Pro, annual billing: $25 a month, or $300 a year. Using it for one 6,000-lead launch gives $25 ÷ 6,000 × 1,000 = $4.17 per 1,000, but you pay for the full year upfront.
For a team with one launch a month, the monthly plan usually makes more sense. You can read more about cost structures in email verification pricing.
Bottom line: A single launch of a few thousand leads costs a few dollars per 1,000 on Pro. Cost per 1,000 falls as you verify more leads in the same month.
What does a real pre-launch verification look like?
Here is a worked example using hypothetical results. The arithmetic and plan limits are real.
A SaaS team has 6,000 leads from a prospecting tool and wants to launch this week.
Step 1: Check the plan fit.
- On Free, 6,000 emails would need 40 lists of 150 (6,000 ÷ 150 = 40). Free allows 25 lists a month, which is 25 × 150 = 3,750 emails. That is not enough.
- On Pro, the whole list fits in one list, since the per-list cap is 25,000. The cost is $29 for the month, or $4.83 per 1,000 leads.
Step 2: Run the check and read the counts (illustrative).
- Valid: 4,620 (4,620 ÷ 6,000 = 77%)
- Risky: 900 (900 ÷ 6,000 = 15%)
- Invalid: 480 (480 ÷ 6,000 = 8%)
Step 3: Estimate what skipping the check would have cost.
If the team had sent to all 6,000 leads, the 480 Invalid addresses alone would put hard bounces near 8%. That is four times the 2% ceiling, before any Risky address bounced. Removing Invalid addresses before sending brings that known source of bounces to zero.
Step 4: Release in waves.
- Wave 1: 1,500 of the most engaged Valid contacts. Pause and review if bounces exceed 15 (1%).
- Wave 2: the remaining 3,120 Valid contacts (4,620 − 1,500), released only if wave 1 stayed under the threshold.
- Risky test: send to 100 randomly selected Risky addresses. If more than 2 bounce (2%), hold the other 800 (900 − 100) for this campaign. If the test is clean, release them in small batches.
A note on the Risky test: with 100 addresses, one or two bounces is more noise than signal. Use the test to catch a segment that is badly broken, not to measure its exact bounce rate.
Bottom line: The check removed 480 addresses that would have pushed the send far above the 2% ceiling. The wave plan turns the 900 Risky leads into a measured decision instead of a gamble.
How should you handle Risky and catch-all leads?
Hold Risky leads back, test a small batch, and release them only if the test is clean. Catch-all addresses are the most common Risky result, and verification alone cannot fully settle them.
A catch-all domain accepts mail for any address, so the server cannot confirm that a specific mailbox exists. A Risky catch-all verdict means uncertainty, not failure. The catch-all email verification page explains how these results are categorized.
Other Risky types need different handling:
- Role addresses such as
info@orsales@are shared inboxes. They tend to get low engagement, and people who do not recognize the sender may complain. Keep them out of personal cold sequences. - Disposable addresses come from temporary inbox services. Exclude them from any campaign that depends on a real relationship.
Bottom line: Risky is a decision point, not a pass or a fail. Test a small sample before releasing it to the full segment.
What can email verification not tell you?
Verification tells you whether an address looks deliverable right now. It cannot prove that the person agreed to hear from you, still works at the company, or is not a trap address.
- Consent is not verified. An address can be valid and still belong to someone who never opted in. In the US, the FTC's CAN-SPAM compliance guide sets requirements for commercial email, including opt-out handling and a valid postal address. The UK and EU apply different consent rules. Verification supports your email verification compliance and hygiene process but does not replace it.
- Mail-server behavior varies. Some servers do not confirm whether a mailbox exists, which is why catch-all and Risky categories exist. Results for those addresses are probabilistic.
- Vendor accuracy claims are not independent. Unlimited Verifier states 99.5% accuracy for its deep verification. That is the company's own figure, not an independent benchmark.
Bottom line: Verification reduces bounces. It does not make a list permission-based. Keep your consent records in order.
Should you verify inside your sending platform or outside it?
Verify outside the platform when you need raw verdicts and one standard applied across every tool. Use a platform's built-in check when convenience matters more than control over the results. Instantly lead verification vs an external verifier covers this decision in more depth.
Ask three questions of any built-in check:
- Does it separate catch-all and role addresses from Valid ones?
- Can you export the raw verdicts, or only a pass-or-fail flag?
- Does it apply the same rules to leads imported from other tools?
If the platform cannot answer these, an external check gives you a file you can audit. For LinkedIn-sourced lists, see how to verify LinkedIn Sales Navigator leads. For enrichment workflows, see how to verify emails in Clay tables.
Bottom line: Use a built-in check for convenience, but keep an external audit trail for lists that matter.
What are the most common mistakes before a launch?
The most common mistakes are verifying too late, deleting only the addresses that already bounced, and sending Risky leads first. Each causes a predictable problem.
- Verifying after sending. A check run after the launch cannot prevent the bounces it was meant to stop.
- Removing only past bounces. The rest of the list is still untested. Verify the whole file.
- Sending Risky leads at the start. Put them at the end, after data from the Valid waves.
- Losing suppression history during export. When you move lists between tools, keep your own copy of the suppression file.
- Choosing the wrong plan for the list size. A 6,000-lead file cannot run on Free without splitting it into 40 lists, which exceeds the 25-list monthly allowance.
- Missing the export window. Free results are kept for 24 hours. Download them before that window closes.
- Treating Valid as permission. Valid means the address appears deliverable. It does not mean the person agreed to hear from you.
- Reusing an old verified file. Re-verify if the file is older than about 30 days.
Bottom line: Most launch failures come from timing and process, not the verifier. Verify the whole list, release it in waves, and keep the audit trail.
How do you keep leads clean for future launches?
Verify at capture, verify at import, and re-verify on a schedule. A list checked once will decay again.
- At capture: Use real-time email validation on forms so bad addresses never enter your system.
- At import: Run every new file through verification before it reaches your sending tool.
- On a schedule: Re-verify active lists monthly or quarterly. Our email list maintenance best practices guide covers the cadence in detail.
When you choose a verifier, check three things: how results are categorized, whether you can export raw data, and whether the API fits your pipeline. The how to choose an email verifier guide covers these questions in depth. Teams running email verification for ecommerce and SaaS face the same questions with higher lead volume and faster churn. For pipelines that need checks without manual uploads, see the email verification API and automation options. For a broader view of tooling, read the best B2B sales prospecting tools for 2026.
Bottom line: Verification works best as a habit at three points: capture, import and scheduled re-checks.
How we compared (and limitations)
This guide draws on public documentation: Amazon SES's published thresholds, Google and Yahoo's sender guidelines, RFC 3463 for SMTP status codes, and the FTC's CAN-SPAM guide. We have not run controlled tests against competing vendors or any ESP's review team. Thresholds and workflows change without notice, so check current documentation before you launch.
Unlimited Verifier details come from the company's published plan facts. Its 99.5% deep-verification accuracy is the company's stated figure. The 6,000-lead example uses hypothetical results, while the plan arithmetic and per-list limits are real.
Bottom line: Treat the thresholds as starting points, check current documentation for your platform, and use the worked example as a template for your own counts.
Pre-launch verification steps
- Freeze the segment: export the final list you plan to send, with one email per row and no duplicates.
- Verify in bulk: upload the CSV and wait for per-address results.
- Delete Invalid: remove every address marked Invalid from the sending file.
- Test Risky: send a small first wave of Risky addresses and watch hard bounces.
- Launch Valid: send to verified addresses first, then expand if bounces stay under 1-2%.
- Re-import clean results: update your sending tool with only the cleaned list and archive the verdicts.
Frequently asked questions
How do I verify leads before sending a campaign?
Export your final segment to a CSV, upload it to a bulk email verifier, and wait for the categorized results. Delete Invalid addresses, send to Valid addresses first, and hold Risky addresses for a small test. Re-import only the cleaned list into your sending tool so nothing stale slips through.
What does a Risky email result mean?
A Risky result means the verifier could not confirm the mailbox either way. Common causes are catch-all domains that accept any address, or servers that block verification probes. Treat Risky addresses as unproven and send them only after a small test wave shows acceptable bounce rates.
What is an acceptable bounce rate for a cold email launch?
Many senders aim for hard bounces under 2% on a cold launch and under 1% for the first wave. Higher rates can damage sender reputation and hurt deliverability for future campaigns. If bounces climb, pause the send and re-verify the affected segment.
Should I verify leads again right before sending?
Yes, if the list was verified some time ago. B2B contact data decays as people change jobs and mailboxes close. Re-verifying the full segment shortly before each launch is the safest habit, and it costs little compared with a damaged sender reputation.
What is the difference between a hard bounce and a soft bounce?
A hard bounce is a permanent failure, such as a nonexistent mailbox, and should be removed from the list immediately. A soft bounce is temporary, such as a full inbox or a server outage. Soft bounces can be retried, but repeated soft bounces usually mean the address should be removed.
Can a verifier guarantee that an email will be delivered?
No. A verifier estimates deliverability by checking syntax, domain, mail server and mailbox signals. It cannot guarantee delivery, especially for catch-all domains, which accept mail for any address. Verification reduces bounces substantially, but a small test wave still gives the most reliable signal.
What is a catch-all domain?
A catch-all domain is a mail server configured to accept mail sent to any address on that domain, whether or not the mailbox exists. Because the server always says yes, verifiers cannot confirm individual mailboxes, so these addresses are usually marked Risky.
Do I need to verify leads from a paid database?
Yes. Paid databases can still contain outdated records, guessed addresses and domains that accept any address. Verification is cheap insurance, and it is most useful right before launch when the data is about to be used.
What does SMTP code 5.1.1 mean?
SMTP enhanced status code 5.1.1 indicates that the destination mailbox does not exist. It is a hard bounce, defined in RFC 3463, and the address should be removed from your list before any further sends.
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.