All posts

Instantly Lead Finder Emails Bouncing? Why 'Verified' Leads Still Bounce

··6 min read

"Verified" leads from Instantly's lead database or a done-for-you list bounce because the label is a snapshot. The check happened before you pulled the list, some of the people have since left, and catch-all domains let guessed addresses pass as verified. The fix is a fresh mailbox check on the day you upload: send to the addresses that come back valid, isolate catch-all and risky addresses in their own small campaign, and drop the invalid ones before Instantly ever sees them.

The complaint, in the words people use

Posts on r/coldemail keep describing the same thing: a pull from Instantly's lead database (now called SuperSearch, earlier Lead Finder), from Apollo, or a done-for-you list bought from a freelancer, every lead marked verified, and a first send that bounces far beyond what "verified" suggests. Some threads report bounce rates of a quarter or more. We can't check those numbers, but the pattern behind them is consistent and easy to test on your own list.

None of this is unique to Instantly. Every B2B database has the same three gaps. The Apollo version of this problem works the same way, and so does any list that someone else verified for you.

Why a verified label doesn't mean deliverable today

1. The check is old

A database verifies an address once, or on a schedule, and stores the result. The label you see is the stored result. In the time since:

  • people change jobs, and their old mailbox is closed or bounces;
  • companies rename, merge or move to a new domain;
  • some mailboxes are disabled by IT after a leaver policy.

None of those changes reach the database until it re-checks that record. If you pull leads in a niche with high job churn, more of the labels are out of date. See why a valid email can belong to someone who left.

2. Catch-all domains say yes to everything

Some domains accept mail for any address at the SMTP stage, then bounce or discard it later. A verifier talking to such a server hears "accepted" for john@, j.smith@ and xyz123@ alike. A database that counts "accepted" as verified will mark guessed addresses on those domains as verified, even though nobody confirmed the person exists. Many small and mid-size company domains, and many domains behind security gateways, behave this way. More on that in catch-all leads in sequences.

3. Some addresses were guessed from a pattern

Lead databases fill gaps by building an address from the person's name and the company's known format, then testing it. When the test is inconclusive, some sources still show the address with a confidence score or a softer label. When you export, those addresses sit in the same column as the confirmed ones, and they look identical in a CSV.

Why it hurts more in Instantly than you'd expect

Instantly pauses a campaign for bounces at 5% by default, but its help centre says the check only runs once a campaign has sent at least 200 emails, and after you resume it won't auto-pause again for 7 days. We worked through what that means in keeping an Instantly bounce rate under control. The short version: a list a few percent invalid never trips the pause, and still does damage on new domains and new inboxes. A list that does trip it has already bounced on your sender reputation.

How to measure the real quality of a pull

Don't guess, and don't trust a single headline number from anyone, including us. Measure each pull:

  1. Export the pull to CSV with the email column and whatever source fields Instantly gives you. If you can, keep a column for when you pulled it.
  2. Take a sample. A few hundred rows chosen at random is enough to see the shape. The email list sampler does this without spreadsheet tricks.
  3. Verify the sample on the verify page. Each address gets a live SMTP mailbox check. Results come back as valid, invalid, risky or catch-all, and catch-all addresses are graded as risky, never guessed valid (how catch-all scoring works).
  4. Read the split. Invalid tells you how many would hard-bounce. Catch-all tells you how many are unknowable at SMTP. Risky covers the rest of the uncertain cases.
  5. Decide the whole pull. If the sample is mostly valid, verify the full file. If invalid is high, clean the full file before sending anything, and ask the source why.

The bounce rate by source tool helps when you mix pulls from several places and want to see which one causes the bounces. If a campaign has already bounced, find which list source caused the bounces walks through the same idea after the fact.

The pre-send routine

Step What to do Why
Dedupe Remove duplicates across pulls with remove duplicate emails Avoid paying to check, and send to, the same person twice
Strip obvious junk Role addresses (info@, sales@) into their own list with the role-based email filter Shared inboxes complain more and rarely reply to cold email
Verify on the day Full list through /verify or the Instantly integration The label from the database is old; yours is from today
Split by result Valid into the main campaign; catch-all and risky into a separate small campaign; invalid removed Keeps the main campaign's bounce rate close to zero
Ramp slowly New domains and inboxes start low and grow Instantly's own guidance is 30 cold emails per account per day as a safe limit

If you'd rather not export at all, verify Instantly leads without exporting covers the connected route.

What to do with the catch-all leads

Catch-all leads aren't all bad. Many belong to real people at real companies. The risk is that you can't tell which ones before sending. A sensible pattern:

  • keep them in their own campaign with a lower daily cap;
  • send from inboxes you can afford to rest;
  • watch that campaign's bounces separately, and stop it if it climbs;
  • prefer leads where you have another signal, such as the person appearing on the company's website or a recent LinkedIn role.

Asking the source the right questions

Whether the list came from a database, a freelancer or a done-for-you service, you can ask:

  • When was each address last verified, and with what?
  • Are catch-all addresses included in "verified"?
  • Were any addresses built from a pattern rather than found?
  • Do you credit back bounced leads? Some providers do; see lead data bounce credit refunds.

A good source will answer plainly. Either way, your own check on the day of sending is the one that counts.

What it costs

  • Pro, $39 a month: Unlimited email verification.* Includes the email finder, an API with 10,000 calls a month and the MCP server.
  • Starter, $9 a month: 2,500 emails a month.
  • Free: 100 checks with a Google sign-in, no card.

*Fair use: the first 100,000 checks a month at full speed, then slower, never cut off. API calls, phone lookups and the finder are not part of Unlimited.

If you pull a few thousand leads a week from Instantly, re-verifying every pull on a flat monthly price costs less than burning a domain. Use the Instantly verification cost calculator to compare with credits, then see pricing.

More reading: verified emails still bouncing, Instantly and Smartlead list hygiene checklist, pause a campaign after a bounce spike.

Common questions

Why do Instantly SuperSearch leads bounce if they say verified?

Because the verification happened earlier, against whatever the mail server said at the time. Since then some people have left, some mailboxes have been closed, and some addresses were on catch-all domains where the server accepted anything. A fresh check on the day you send catches most of the first two and labels the third as risky.

What bounce rate is normal from a lead database?

It depends on the source, the industry and how old the records are, so there is no honest universal number. Measure your own: verify a sample of each pull and count invalid and catch-all results. If a sample comes back with more than a few percent invalid, the full pull needs cleaning before it goes near a campaign.

Should I use Instantly's own verification or a separate verifier?

Either is fine as long as the check runs right before sending. Instantly charges credits for verification and leads marked Invalid or Risky are skipped unless you enable risky emails. A separate verifier is useful when you pull leads from several sources, want catch-all results graded rather than lumped together, or want one result file for every platform you use.

Are done-for-you lead lists safe to send to?

Treat them exactly like a database pull. Ask when the list was verified and with what, then run your own check before upload. A done-for-you list that was verified a month ago is a month-old list.

Check your list before you send

Real mailbox checks over SMTP, and nothing is sent to the address. Sign in with Google and your first 100 email checks are free, no card. Plans for bigger lists are on the pricing page.