Free bulk-sender compliance check
Would this domain meet Gmail and Yahoo's sender rules?
Since 2024, Gmail and Yahoo require DMARC, SPF, and valid reverse DNS from anyone sending meaningful volume. We check the DNS-verifiable parts of those rules.
Why this only covers part of the rules
Gmail's and Yahoo's bulk-sender requirements are a mix of two very different kinds of rules: things you can check from DNS right now (DMARC, SPF, reverse DNS) and things that depend on your actual sending behavior over time (spam complaint rate, unsubscribe handling). This tool only checks the first kind, because the second kind requires visibility into your sending history that no public tool can see from the outside.
Passing every check here means the technical foundation is solid. It doesn't guarantee inbox placement — reputation, engagement, and content still matter — but it removes the most common DNS-level reasons mail gets rejected outright before reputation is even considered.
Common questions
What are the Gmail and Yahoo bulk-sender requirements?+
Since February 2024, Gmail and Yahoo require anyone sending significant volume to their users to have a valid SPF and DKIM setup, a published DMARC record, valid forward-confirmed reverse DNS on the sending IP, and a spam complaint rate that stays under a low threshold. Senders who don't meet these get their mail rejected or heavily filtered.
What does this tool actually check?+
Only the parts that are verifiable from public DNS: whether a DMARC record exists and is enforcing, whether SPF exists and is under the 10-lookup limit, whether MX records are valid, and whether the sending IP has forward-confirmed reverse DNS. It cannot check your spam complaint rate or whether your marketing email has a one-click unsubscribe link — those require sending history and message content, not DNS.
What is forward-confirmed reverse DNS (FCrDNS)?+
It's a check that your sending IP's reverse DNS (PTR) record points to a hostname, and that hostname's own DNS record points back to the same IP. It's a basic sanity check that receiving servers use to filter out obviously spoofed or throwaway sending infrastructure.
Do these rules apply to me if I only send a few emails a day?+
The strictest requirements (spam-rate threshold, one-click unsubscribe) are aimed at bulk senders, roughly 5,000+ messages a day to Gmail addresses. But DMARC, SPF, and DKIM are good practice — and increasingly checked informally — regardless of volume, so it's worth passing these checks either way.
I passed everything here but my mail still goes to spam. Why?+
These checks confirm technical compliance, not sender reputation. A domain can be perfectly configured and still get filtered because of low engagement, spam complaints, or a new/unestablished sending history. Compliance is necessary but not sufficient — it removes the technical reasons mail gets blocked, not the reputation-based ones.
More free checks