Cold Email Deliverability Test: How to Check Before You Send

Most cold outreach fails before anyone reads it. The sequence is written, the list is clean, the sender hits launch, and half the emails land in spam or get dropped silently. A cold email deliverability test is cheap insurance against that: a short set of checks you run before a campaign to confirm your domain, your mailbox and your message can actually reach a primary inbox. This guide covers what to test, how to do it with free or low-cost tools, and how to read the results without guessing.

What a cold email deliverability test actually measures

Deliverability is not one number. When someone says "my emails aren't landing," they usually mean one of four different problems:

• Authentication. Does the receiving server trust that you are who you say you are? That is SPF, DKIM and DMARC.
• Reputation. Has your domain or sending IP been flagged by blacklists or by the mailbox providers' own filters?
• Placement. When mail is accepted, does it go to the primary inbox, promotions, or spam?
• Content and infrastructure signals. Tracking links, broken HTML, a missing opt-out line, or a brand-new domain with no history.

A proper test touches all four. Checking only one, usually a quick spam-score tool, gives a false sense of safety.

Step 1: Test the domain before you test the copy

Start with DNS, because nothing else matters if authentication fails. Pull up your sending domain and verify:

1. SPF exists, includes every tool that sends on your behalf, and stays under the 10-lookup limit. Exceeding it quietly breaks SPF.
2. DKIM is published for the exact selector your sending tool uses, with a 2048-bit key.
3. DMARC is published with at least p=none and a reporting address, so you receive aggregate reports. Move to p=quarantine once reports look clean.
4. Reverse DNS and MX resolve correctly, even for a secondary outreach domain.
5. A custom tracking domain is configured in your outreach tool, so clicks do not route through a shared domain used by thousands of other senders.

A common founder mistake: outreach runs from a secondary domain registered last week, with no website and no warm-up history. Mailbox providers treat that like a stranger knocking at 3 a.m. Give new domains at least two to three weeks of warm-up before any real volume.

Step 2: Run a seed inbox placement test

Passing authentication does not mean your mail lands in the inbox. The only honest way to know is a seed test: send your actual sequence email from the actual mailbox to a set of seed addresses across Gmail, Outlook, Yahoo and a couple of business-grade hosts, then record where each one lands.

You can do this manually with a dozen accounts you control, or with a placement testing service. Either way, follow the rules:

• Send the real email with merge fields filled in, links and signature. A stripped-down test version tells you nothing.
• Send from the same mailbox and the same tool you will use for the campaign.
• Test every sending mailbox separately. One flagged mailbox out of five drags the whole domain down.
• Repeat the test mid-campaign, not just before launch. Reputation shifts as replies, bounces and complaints accumulate.

Record the result as a simple split: inbox, promotions, spam, missing. Anything below roughly nine out of ten in the primary inbox for a B2B seed set means stop and fix before scaling.

The pre-send cold email deliverability test checklist

Run this before every new campaign and after any change to domains, tools or copy:

• [ ] SPF, DKIM and DMARC all pass on a test send (check the raw headers via "Show original" in Gmail).
• [ ] Sending domain and IP are clear on the major blacklists.
• [ ] Domain is over 30 days old and the mailbox has been warmed for at least two weeks.
• [ ] Daily volume per mailbox is capped, typically 30 to 50 cold sends for a new mailbox.
• [ ] List has been verified and the bounce rate on the last batch stayed under 2 percent.
• [ ] First-touch email is plain text, has no images and at most one link.
• [ ] An opt-out line is present and works.
• [ ] Custom tracking domain is live and resolves over HTTPS.
• [ ] Seed placement result is 90 percent primary inbox or better.
• [ ] Reply monitoring is on, so answers and complaints stop follow-ups automatically.

Reading the results: what to fix first

When a test fails, fix in order of repair cost:

1. Authentication failures are a DNS edit. Fix today.
2. Blacklist hits need a delisting request plus a root-cause fix, usually a bad list or a compromised mailbox.
3. Spam placement with clean auth is almost always reputation or content. Cut volume, remove links, rewrite the first email to read like a one-to-one note, and re-test in a week.
4. Promotions tab placement is tolerable for some audiences but a warning sign for cold B2B. Usually caused by HTML formatting, images or marketing-style phrasing.

Example: a founder sees healthy opens on Gmail but almost none on Outlook. The seed test shows Microsoft is quarantining. The typical cause is a missing DMARC record or too much volume from a single new mailbox. Fix DNS, split sends across mailboxes, re-test. No copy change needed.

Treat the test as a recurring control, not a launch ritual. Reputation decays faster than it builds.

How this runs inside AI CMO OS

In AI CMO OS this sits in the outreach module. Before a KOL, sponsor or listing campaign goes out, the operator runs the deliverability checks, confirms seed placement for each mailbox, and keeps the reply watcher on so every answer or complaint pauses the sequence. The same deliverability checks run on retention drips, so a warm list never gets burned by a cold-outreach mistake. One operator, agents doing the repetitive checking, and the test happens every time rather than only when someone remembers.