How can you safely test deliverability to specific ISPs?

You've set up your authentication, your content looks clean, and your list is in good shape. But you still don't actually know where your emails are landing until you check. That's what ISP-specific deliverability testing is for.

The core idea is straightforward. You send a real email to real accounts you control at each major provider, then you log in and see exactly where it ended up. Inbox, spam, Promotions tab, or nowhere at all. Each result tells you something different about how that provider's filters see you.

Start with seed accounts

A seed account is just a real mailbox you control at a specific provider, used only for testing. You want at least one at each of the major four: Gmail, Outlook, Yahoo Mail, and iCloud Mail. These cover the bulk of consumer inboxes in most English-speaking markets.

Keep these accounts clean. Don't use them for personal email, sign them up for newsletters, or let them accumulate unread messages. A seed account that looks like an abandoned inbox isn't a reliable testing signal. Treat it like a controlled lab environment.

What to actually send

Send your real campaign content, not a stripped-down placeholder. Spam filters evaluate exactly what they receive, so testing with a blank email or a one-liner tells you almost nothing about how your actual sends will perform.

Send from the same domain and IP you use for production. If your real campaigns go out via a specific subdomain or dedicated IP, test from that. Testing from a different sending configuration is like checking road conditions on a different road.

Keep the test volume small. Sending 4 or 5 emails to seed accounts doesn't risk triggering rate limits or raising flags. You're not warming up a list here. You're just checking placement.

What to check once it arrives

At Gmail, note which tab it lands in (Primary, Promotions, or Updates), and whether it hits spam. A Promotions placement is not a failure for marketing email. Spam is. If you're hitting Promotions and want to understand why, your content and engagement history matter more than any technical tweak.

At Outlook, check both the Inbox and the Focused Inbox view. Outlook's filter is different from consumer providers and tends to rely more heavily on engagement history and sending reputation from its own database. If it's going to Junk, look at your Microsoft SNDS data for more context.

At Yahoo and iCloud, you're looking at a simpler binary: inbox or spam. Both providers are less transparent about filtering reasons, which is exactly why manual checking matters.

How often to run this

Before any major campaign, test. Before you change your sending template, test again. If you're warming up a new IP or domain, test every few days during the warmup period. Outside of those events, a weekly or biweekly check gives you a useful baseline so you notice when something shifts.

Consistency is what makes this useful. A single result tells you very little. A pattern of results tells you whether you have a provider-specific problem or something broader.

When to go beyond manual testing

Doing this by hand works fine for smaller senders. If you're sending at significant scale or across many domains, seed list services like SparkPost (now Bird) offer automated inbox placement monitoring across hundreds of addresses. They're not free, but they save a lot of manual checking and catch placement changes faster than any human can.

Still one thing to check before you test anything: make sure your SPF, DKIM, and DMARC are all passing. If your authentication is broken, your test results will reflect that problem, not your content or reputation. You'd be fixing the wrong thing. You can run a quick check on your setup with our free Email Header Analyzer once your test email arrives.