Instantly Email Verifier: How to Clean Lists Without Per-Email Costs

Instantly is built around one of the most effective cold-email features available: multi-inbox rotation at scale. Connect dozens of sending accounts, spread sends across them, and let Instantly manage the distribution — warming inboxes, pacing sends, rotating senders to avoid triggering spam filters.

The inbox rotation model is powerful. It also means that when a bad list enters the system, the bounce damage does not hit one inbox — it gets distributed across all of them.

That is the case for verifying before you import into Instantly. When your list is clean, inbox rotation amplifies deliverability. When the list has bad addresses, inbox rotation distributes the reputation damage across every account in the rotation.

What Instantly does not do

Instantly handles send scheduling, inbox rotation, reply detection, sequence management, and campaign analytics. It does not probe the addresses in your prospect list before the first email fires.

This is reasonable — verification is a different problem than sending. But the gap is real, and it shows up in bounce rates when unverified lists enter campaigns.

Instantly users commonly experience:

• Bounce spikes on new lists from sourcing tools that include stale or fabricated addresses
• Inbox rotation accounts getting flagged when bounces accumulate faster than the warmup reputation can absorb them
• Higher-than-expected hard bounce rates on B2B lists from address sources that include M365 domains (where raw SMTP probing does not catch non-existent mailboxes)

Verification before import is the fix for all three.

What email verification actually involves for cold outreach

Not all verifiers are equal. Here is what the layers mean for Instantly users specifically:

Syntax and MX checks

These catch obviously broken rows. Useful, not sufficient. A domain with valid MX records and a cleaned-out staff roster passes these checks. The individual mailboxes that no longer exist do not show up until an SMTP probe.

SMTP mailbox probing

MailCull opens a direct SMTP connection to the receiving mail server and issues RCPT TO for each specific address. The server responds with a clear verdict:

• 250 OK — the mailbox accepts mail. Deliverable.
• 550 5.1.1 (or similar) — user unknown. This is the hard bounce you are trying to avoid.
• 4xx — temporary deferral. Greylisting, rate-limiting. Inconclusive — treat as risky.

For cold outreach, every address that returns a 550 before import is a bounce event prevented. On a list of 2,000 addresses with 7% bounce risk, that is 140 prevented bounces — each of which would have been recorded against one of your Instantly sending accounts.

Microsoft 365 HTTP enumeration

This is the critical layer for B2B cold outreach, where a large share of target addresses are on M365.

Microsoft's EOP accepts RCPT TO for any address on a tenant — real or fabricated. A standard SMTP probe returns 250 OK for a non-existent address on an M365 tenant. Without additional checking, that address looks deliverable. It hard-bounces on actual send.

MailCull's HTTP cascade queries Microsoft's authentication APIs:

1. GetUserRealm — confirms M365 routing
2. GetCredentialType — checks whether the specific username has an active account
3. Autodiscover v1 — cross-references account existence

Addresses where the HTTP cascade says no active account but SMTP returns 250 OK (the classic M365 false-positive) are marked risky with a m365_smtp_disagreed reason. For an Instantly campaign targeting business prospects, removing these addresses prevents the most expensive type of bounce: the M365 corporate hard bounce that damages multiple inbox accounts simultaneously via rotation.

Catch-all domain detection

Some corporate domains accept all RCPT TO regardless of mailbox existence. MailCull probes with a random implausible address to detect this, then flags all individual addresses on catch-all domains as risky. Individual mailbox existence cannot be confirmed for these.

The workflow: MailCull + Instantly

Step 1: export your prospect list

Pull contacts from your sourcing stack — Clay, Apollo, Sales Navigator, Hunter, Phantombuster, manual research, or wherever. Get them into a CSV.

MailCull handles multi-column files. You do not need to strip out name, company, title, and other columns before uploading.

Step 2: verify in MailCull Verify List

Upload the CSV. Full check stack runs: syntax, MX, typo, disposable, SMTP probe, M365 HTTP cascade, catch-all detection.

Free: 1,000 rows/month (no credit card required) Pro: 100,000 rows/month at $9/month Scale: 500,000 rows/month at $49/month

Step 3: triage and export

Export the clean segment — preserving all original columns — and import into Instantly as normal.

Step 4: set Instantly bounce thresholds as backstop

Even with verification, configure Instantly's bounce-rate limit as a safety net. A 2-3% threshold is appropriate for a verified list. If you ever hit that threshold with a verified list, it is a signal that your sourcing tool has a quality problem — not a list-hygiene problem.

Per-email cost comparison

Many verifiers charge per-email credits. At scale, this adds up:

• ZeroBounce: ~$0.0008/email at high volume
• NeverBounce: ~$0.003/email
• Bouncer: ~$0.0045/email

For an Instantly user running 5,000+ verifications per month, the credit math matters. MailCull's Pro plan at $9/month covers 100,000 validation credits on one unified pool across single-email and list workflows.

If your monthly verification volume fits inside those limits, the subscription model is materially cheaper than paying per-email at any of those rates.

Inbox rotation and list quality

Instantly's inbox rotation works best when it is protecting good deliverability, not compensating for bad list quality. When you feed verified lists into rotation:

• Bounce rates stay low across all sending accounts
• Warmup reputation accumulates without disruption
• Reply rates are more representative (you're measuring on addresses that actually exist)
• Spam complaint risk is lower (role addresses and shared inboxes are removed)

Unverified lists force the rotation system to absorb bounce damage spread across every account. Verified lists let the rotation system do what it's designed for: optimising send timing and inbox placement across clean sends.

When to run verification

Before any new campaign list. Any list from a sourcing tool you haven't used before, or a list assembled from multiple sources, should be verified before the first step-1 email fires.

Before importing a purchased or aged list. These have the highest decay rates. Purchased lists especially — the addresses were valid when sold but may be months or years old.

After a notable sourcing tool update. If a tool you use regularly rolls out a data refresh or changes its data sources, run a spot-check on the next batch to see if quality has shifted.

Before a major outreach push. Any time you are loading a large campaign — hundreds or thousands of new prospects — verification before import is the right call.

---

You came here to protect your Instantly inboxes from bounce damage. MailCull does the SMTP verification and M365 enumeration that catches the addresses a simpler check would miss.

Verify your Instantly prospect list in MailCull — free up to 1,000 rows →