Verifyre

Email verification for cold outreach and B2B prospecting

Cold lists are guessed, scraped and aged, so they bounce more. How to verify before every sequence, handle catch-all domains, stay under 1% bounces and keep the programme compliant.

Email verification for cold outreach means checking every prospect address before it enters a sequence, so that bounces stay under the 2% line that gets a cold domain throttled or blocked. Cold lists bounce far more than opt-in lists because the addresses were guessed, scraped or bought rather than given, and a single bad batch can burn a sending domain in an afternoon. Verifying first keeps the domain alive; handling catch-alls carefully and honouring opt-outs keeps the programme compliant.

Why do cold lists bounce so much more than opt-in lists?

An opt-in list was typed by its owners. A cold list was assembled, and every step of assembly introduces dead addresses:

  • Guessed patterns. Tools that turn "Priya Shah at example.com" into priya.shah@example.com are right perhaps 60% to 80% of the time at companies with a consistent pattern, and far less at companies that use initials, nicknames or several patterns at once.
  • Scraped and purchased data. A data vendor's record may have been true when it was collected. Around 22% of addresses go bad every year through job changes alone, so a two-year-old database has lost roughly 40% of its accuracy before you touch it.
  • Job changes. The person who moved on is exactly the person a prospecting tool still lists, because their old profile is still indexed.

Put together, raw cold lists typically run 10% to 30% invalid, against 1% to 3% for a maintained opt-in list.

What does a 5% bounce rate do to a cold domain?

Suppose a new domain sends 200 cold emails a day and 5% bounce. That is 10 hard bounces a day, every day. Mailbox providers read bounce rate as a direct measure of list quality, and a cold domain has no history to offset it. The usual sequence is:

  1. Within a few days, messages to the provider that saw the bounces start landing in spam.
  2. Within a week or two, the provider starts deferring connections with 4xx replies, so even deliverable addresses go unanswered.
  3. If it continues, the domain is blocked outright and the IP it sends from may be listed, which affects every other domain on that IP.

Recovery takes weeks of warm-up at low volume. Verification before sending cuts the 5% to well under 1%, and a 1% bounce rate on 200 a day is 2 bounces, which most providers tolerate from a warming domain. The bulk list cleaning page covers what a full clean removes.

How should you handle catch-all domains in outreach?

This is the hardest question in cold email. Many of the companies you most want to reach, especially mid-size and enterprise, run catch-all mail servers that accept every address, so a verifier cannot confirm a specific mailbox and returns risky. Catch-all domains explained covers why.

Dropping every catch-all throws away a large slice of the list. Sending to all of them reintroduces the bounces you were trying to avoid, because a wrong guess at a catch-all domain bounces late or vanishes after acceptance. The workable middle:

  • Send catch-all addresses in small batches, no more than 10% to 20% of a day's volume, from a secondary domain.
  • Watch the bounce rate on those batches separately. A pattern that comes back clean for one person at a domain is probably right for their colleagues.
  • Prefer addresses with other evidence: a past reply, a signature in a thread, a pattern confirmed elsewhere.
  • Accept that some risk is the price of reaching those companies, and keep it where it cannot hurt the primary domain.

When should you verify a cold list?

Before every sequence, not just once at import. A list verified in January and sent in May has lost several percent in between. The practical rule is a fresh check on any address older than 30 days, and the 24-hour cache means re-verifying a list you ran yesterday costs nothing. Upload through the dashboard or push through POST /api/v1/bulk with up to 50,000 addresses per job and a callback_url to notify your sequencer when results are ready.

What should each verdict mean for your sequence?

VerdictScoreOutreach action
Deliverable90 to 100Add to the main sequence
Risky, catch-all60 to 89Small batches from a secondary domain, watch bounces
Risky, role address60 to 89Usually skip; info@ rarely replies and complains more
Unknown30 to 59Recheck in 48 hours, send only if it clears
Undeliverable0 to 29Remove, and fix the pattern that produced it
Free provider (gmail.com and similar)AnyRoute separately, see below

The free flag deserves its own rule. A B2B prospect using a Gmail address is either a sole trader or a stale record, and the two deserve different messaging. The free email detector flags them in bulk, and free providers vs business domains goes into how to route them.

Is cold email compliant, in plain terms?

This is general information, not legal advice; the rules differ by country and the detail matters.

  • GDPR (EU and UK). B2B cold email usually relies on legitimate interest rather than consent. That means a genuine business reason, a message relevant to the person's role, a clear opt-out in every email that is honoured promptly, and a record of where the address came from. Verification itself is processing of personal data and needs the same care; see GDPR and email verification.
  • PECR (UK). The UK's electronic marketing rules treat corporate subscribers (addresses at a company domain) differently from individual ones, which is one reason B2B senders separate free-provider addresses from business addresses. Sole traders and partnerships count as individuals.
  • CAN-SPAM (US). No consent requirement, but every message needs an accurate sender, a physical postal address and a clear opt-out, and opt-outs must be processed within 10 business days.

None of these laws is satisfied by verification alone. Verification keeps your bounces down; your process has to keep the opt-outs honoured and the sourcing documented.

How do warm-up and volume fit in?

A new sending domain should start at 20 to 50 messages a day and roughly double weekly as long as bounces stay under 1% and complaints near zero. Cold programmes typically cap a domain at 200 to 500 a day even when warm, and split volume across several domains. Keep cold sending on domains separate from the one your company uses for customers and transactional mail, so that a bad week in prospecting can never take down invoices and password resets. Verification is what makes the warm-up curve hold: one unverified import can undo a month of reputation.

Key takeaways

  • Cold lists are guessed, scraped and aged, so raw invalid rates of 10% to 30% are typical.
  • A 5% bounce rate on a cold domain leads to spam placement, then deferrals, then a block, within weeks.
  • Verify before every sequence; rechecks within 24 hours are free.
  • Send catch-all addresses in small batches from a secondary domain and watch their bounces separately.
  • Verification keeps bounces down; opt-outs, sourcing records and a lawful basis keep the programme compliant.

Frequently asked questions

Should I send to catch-all addresses at all?

Yes, but in controlled batches from a secondary domain, and only when there is some other evidence the address is right. Never mix them into the primary domain's volume.

How often should I re-verify a prospect list?

Before every sequence, and at least every 30 days for anything still in rotation. Rechecks of the same address within 24 hours are free.

Does verification make a purchased list lawful?

No. It tells you which addresses can receive mail, not whether you have a lawful basis to contact them. Sourcing, relevance and a working opt-out are separate requirements.

What bounce rate should a cold campaign aim for?

Under 1% hard bounces. Anything approaching 2% on a cold domain will show up as throttling within days.

Put it into practice.

100 free verifications on signup. Clean a list, add the widget, or call the API.

Start free See pricing