Cold Email Deliverability Test: How to Check Inbox Placement

You send controlled messages to inboxes you control, then you look at where they ended up. Primary, promotions, spam. That is the whole idea, and it is worth doing because every other number in a cold outreach dashboard quietly assumes the mail arrived in the first place. Open rate on mail that was never delivered is a very calm-looking zero.

What a Cold Email Deliverability Test Actually Measures

Two of the numbers you get back are the ones you expect: what reached the inbox and what got filtered to spam. The third one is the one I actually watch. Mail that shows up in neither folder, accepted by the receiving server and then dropped somewhere invisible, tells you the provider has already decided something about you and is not interested in arguing.

The report also tells you whether SPF, DKIM, and DMARC are aligned and passing. This is the boring half of deliverability, and it is boring right up until a DNS record gets edited during an unrelated migration and nobody notices for a fortnight.

Underneath that sit the signals providers use to sort you: how the sending IP has behaved, how old and how busy the domain is, your bounce rate, and whatever the content scanner thinks of your copy. Nobody outside Google or Microsoft knows how those are weighted against each other, and anyone who tells you the exact recipe is guessing. What a test gives you is the output, not the formula.

How to Check Sender Reputation Before You Send

Blocklists first. Run the domain and the sending IP against the public lists and the reputation scoring services before you spend an afternoon on placement testing, because a listing makes the placement numbers meaningless. Reputation is the main input inbox providers use when deciding what to deliver (their deliverability guide spells this out).

Several services will monitor the common lists for nothing. A clean result is not a gold star, it just means the domain is in decent enough shape that a test will tell you something real.

Then check that SPF, DKIM, and DMARC are actually published, not just written down in a setup doc somewhere. Google's bulk sender guidelines require SPF and DKIM, with DMARC enforcement once you cross into high-volume territory. A DNS lookup takes about a minute. I do this before every test now, mostly because I once spent two days blaming subject lines for a problem that turned out to be a DKIM record that had never propagated.

Run the Test: Step-by-Step Deliverability Check

Seed lists do the work. You send a campaign to a set of test inboxes spread across the major providers, then check which folder each message reached. Most tools hand you the addresses and produce the report, so the only real skill involved is reading it honestly.

A full run takes five steps:

1. Send a small batch of test emails (20 to 50 messages) to your seed list addresses.
2. Wait for the tool to collect results, which usually takes anywhere from 15 minutes to a few hours.
3. Open the deliverability report and review placement rates for each provider.
4. Check the spam score and content analysis for any detected spam triggers.
5. Review email headers and SMTP logs to confirm authentication passed.

Most people test once, with one template, and then draw conclusions from it. Send three or four variations instead. If one version gets filtered and another sails through on the same infrastructure, you are looking at a copy problem. If everything fails equally, look at the plumbing. The awkward middle case, where results are inconsistent across providers and across runs, is common and does not resolve into a neat answer, which is usually a sign the domain is still too new to be judged fairly.

Troubleshooting Email Inbox Placement and the Email Warmup Process

Bad placement usually sends you back to warmup, which means raising volume gradually from a new domain or IP so providers accumulate a record of you behaving reasonably.

Start low, increase in small steps, and make sure there is genuine engagement happening alongside the rising volume. Expect several weeks of it. I have yet to see a shortcut here that survives contact with a real Gmail filter, and I have watched a few people try.

If authentication passes and the mail still lands in spam, the problem is almost always the list. Low opens and a rising complaint rate are the usual pair (M3AAWG's guidance on handling complaints). Cut the contacts who have never once responded to anything, even though cutting them feels like throwing away money.

Sending from your own Gmail or Outlook mailbox is a different game from sending through a bulk provider. You stay inside the per-day limits, and you keep the reply rate at something a human correspondence would plausibly produce, which in practice caps how far you can push volume no matter how clean the setup is.

One caveat that costs people money: a test email can land in spam because the seed address itself has almost no engagement history, not because anything is wrong on your end. Run the test twice against different seed lists before you start rebuilding infrastructure.

Test after any infrastructure change, when you switch providers, and every so often as volume grows. Reputation rarely collapses in a way you can point to. It slides, and you notice through replies drying up rather than through a bounce message, which is the whole argument for checking on a schedule instead of when something feels wrong.

---

Deliverability needs both the right process and the right infrastructure. SEMAOS from DevilDog Lab handles the technical side: DKIM and DMARC configured out of the box, a built-in 21-day domain warmup on paid plans, and nightly 0-100 engagement scoring per contact so you can see which recipients are actually interested. Start a free trial and run your first deliverability test.

FAQ