✓OutboundAuth
← All guides
Guide · Deliverability testing

How to test your deliverability before you send

Sending a campaign without testing it first is like posting a letter without checking the address. A quick deliverability test shows you where your mail actually lands — inbox, spam, or nowhere at all — before your real recipients ever see it.

What does a deliverability test actually check?

Four things decide where your email lands, and a good test covers all of them:

  • Authentication — do your SPF, DKIM and DMARC records pass?
  • Inbox placement — does the message reach the inbox, the spam folder, or the Promotions tab at each provider?
  • Content — does anything in the subject line, body or links look like spam to the filters?
  • Reputation — is your domain or sending IP on a blocklist, or carrying a poor sender reputation?

Testing takes ten minutes. Fixing a campaign that already landed in spam takes days — and the damage to your reputation is hard to undo.

Start with the free checks — they take two minutes

Before any test send, run your domain through the free checker tools: the SPF checker, the DKIM checker and the DMARC audit. They tell you in seconds whether your records exist, are formatted correctly, and actually pass. Fix authentication first — no amount of clever subject lines can rescue mail that fails SPF or DKIM.

Also run a quick blocklist check on your sending IP. If you are listed, that is the first problem to solve, not your email copy. The cold email deliverability checklist covers all of these checks in one place.

What is a seed test?

A seed test is the most honest check you can run. A seed list is a small set of test inboxes you control — one Gmail, one Outlook or Hotmail, one Yahoo, and an Apple Mail address if your audience uses iPhones. You send your real campaign email to the seeds first, then open each inbox and note where it landed.

The point is to see your email the way each provider sees it. Gmail and Outlook run different filters, so a message can land in the inbox at one and in spam at the other. A seed test shows you that difference before your prospects do.

How do you run a seed test?

  1. Build your seed list. At least one address at Gmail, Outlook, and Yahoo. Add a second Gmail if you can — one personal, one Workspace — since they can behave differently.
  2. Send the exact campaign. Same subject line, same body, same links, same sending domain and same sending tool. A test sent from a different domain or a different tool tells you nothing about the real campaign.
  3. Wait 5–10 minutes. Filters take time to process a message. Checking instantly can give you a false result.
  4. Check every seed inbox. Inbox, spam or junk, Promotions tab, or missing entirely — write down the result for each provider.
  5. Open the message and check the headers. In Gmail, open the message, click the three dots, then "Show original". You want to see passes across the board:
    Authentication-Results: mx.google.com; spf=pass; dkim=pass; dmarc=pass
    If any of the three shows fail, fix that record before sending anything else. The email headers guide explains how to read the rest of the verdict.

How do you read the results?

  • Inbox everywhere — good to send. Keep the volume ramp sensible and you are in good shape.
  • Inbox at Gmail, spam at Outlook (or the reverse) — a provider-specific problem. Check that provider's sender tools (for example, Microsoft's SNDS for Outlook), your IP reputation, and whether your content trips that provider's filters.
  • Spam everywhere — stop. Check authentication first, then content: link-heavy emails, image-only emails and classic spam trigger words are the usual suspects. Then check your list — stale or purchased addresses drag down engagement, and low engagement pushes mail to spam.
  • Missing entirely — the message was probably blocked or rejected outright. Check your bounces and your blocklist status before you send again. The bounce codes guide explains what each rejection means.

What about spam-score checkers?

Spam-score tools scan your email and flag risky words, too many links, broken images and similar problems. They are useful for cleaning up your content — but treat the score as a hint, not a verdict. A "perfect" score can still land in spam if your domain reputation is weak, and a mediocre score can still reach the inbox from a trusted domain. Use these tools to tidy your copy, not as a pass or fail test.

How often should you test?

A one-off pass is not a permanent clean bill of health. Test again whenever something changes:

  • Before every new campaign template or a big change to your copy.
  • After any change to your domain, DNS records, or sending tool.
  • When you move to a new sending IP, a new provider, or a new domain.
  • Monthly, as a routine check — reputation drifts quietly, and a monthly seed test catches it early.

And test again after a bad result. Fix one thing, re-test, and confirm the fix worked before you send to real people. Guessing wastes more time than testing.

What do you do if the test fails?

Fix in this order: authentication first (SPF, DKIM, DMARC), then content, then list hygiene (remove stale and bouncing addresses), then volume (slow the send down and warm up longer). Most failed tests are fixed at step one. If you have worked through all four and the test still fails, the problem is usually reputation — and that is fixed by weeks of clean, consistent sending, not by a settings tweak. The why emails go to spam guide walks through each cause in more detail.

Want a second pair of eyes before your campaign goes out?

I check authentication, inbox placement and sender reputation for cold emailers and businesses — and fix what the test finds.

WhatsApp Saqib See packages