Inbox placement: does your mail land in Inbox or Spam?

SPF, DKIM, and DMARC all answer the same basic question: can this mailbox provider verify your mail is really yours? Inbox placement asks something different, and in a lot of ways more important: even once a message is verified as legitimately yours, does it land in the Inbox — or does the receiving provider's own spam filter quietly route it to the Spam folder anyway? Authentication and inbox placement are two separate gates. Passing one says nothing about the other.

There's really only one reliable way to answer "where does my mail actually land": send real test messages to real mailboxes at the major providers, and go look at which folder each one arrives in. This is typically done using a panel of "seed" mailboxes spread across providers like Gmail, Outlook, and Yahoo — a small, controlled sample that mirrors where real recipients actually are.

It's not a one-time check either. A domain's placement can shift week to week as its reputation, sending patterns, and content change, which is why deliverability-conscious senders treat this as something to monitor continuously rather than check once and forget.

Whatever a receiving server decides about SPF, DKIM, and DMARC gets written into the message itself, in a standardized header called Authentication-Results (RFC 8601). It's added by the receiving side, not the sender, which is exactly what makes it useful for testing — pulling this header out of a delivered test message shows the actual pass/fail verdict a real mailbox provider computed, rather than a separate tool's own guess at what the provider would decide.

A typical entry reads something like spf=pass smtp.mailfrom=example.com; dkim=pass header.d=example.com; dmarc=pass header.from=example.com — one clause per protocol, each naming the exact domain it evaluated.

Placement isn't decided by any single factor — it's the combined result of everything a spam filter can observe about a sender and a message.

• Sender reputation — the accumulated trust (or distrust) a mailbox provider has built up about a domain and its sending IP over time.
• Content patterns — wording, formatting, and structure that resemble known spam templates, even when the message itself is completely legitimate.
• Engagement history — whether people who've received mail from this sender before tend to open, reply, delete, or mark it as spam.
• List quality — how many recipients are real, valid, and actually opted to hear from this sender.
• Authentication status — whether SPF, DKIM, and DMARC all check out cleanly.
• Sending consistency — steady, predictable volume tends to be trusted more than sudden spikes.

Gmail, Outlook, and Yahoo each run their own independent spam-filtering systems, built on different data and different rules. It's entirely normal — and common — for a single email to land in the primary inbox at one provider while getting filtered to spam at another. That's exactly why placement testing checks multiple providers at once instead of assuming one result applies everywhere.