Google / Yahoo Compliance
Check bulk-sender requirements (SPF, DKIM, DMARC, PTR, TLS).
Enter a value above to run Google / Yahoo Compliance
e.g. example.com
Quick answer
This tool checks whether your sending domain meets Google and Yahoo bulk-sender rules by testing SPF, DKIM, DMARC, PTR (reverse DNS), and TLS. A green pass on all five means your mail is set up to reach Gmail and Yahoo inboxes; any failure shows the exact record you need to fix.
This tool checks whether a sending domain meets the bulk-sender requirements that Google and Yahoo enforced starting in 2024. It inspects five signals in one pass: SPF, DKIM, DMARC, reverse DNS (PTR), and TLS on the sending path. Senders who deliver more than 5,000 messages a day to Gmail or Yahoo addresses must satisfy all of these, or their mail gets rate-limited, spam-foldered, or rejected outright. The check gives you a single readout so you can see, before your next campaign, exactly which requirement is failing and needs attention.
How it works
You enter the domain you send from. The tool queries public DNS for the SPF TXT record, DMARC policy at _dmarc.yourdomain, and the DKIM selector when one is provided. It resolves the sending IP and checks that a PTR record exists with matching forward-confirmed DNS. TLS is verified by testing whether the receiving side negotiates an encrypted session. Each requirement is reported pass or fail with the record it found, so nothing depends on guesswork.
How to read the results
A green pass means that requirement is satisfied as Google and Yahoo define it. Watch the DMARC line most closely: a policy must exist and be at least p=none, and the record must be published at _dmarc, not the root. SPF must end in -all or ~all and stay under ten DNS lookups. DKIM must show a valid public key at your selector. A failed PTR usually points at your mail server's IP owner, not your domain's DNS.
Common problems & fixes
The most frequent failure is a missing DMARC record, since SPF and DKIM often predate the 2024 rules. Publish a TXT record at _dmarc with at least v=DMARC1; p=none. SPF that exceeds ten lookups fails silently; flatten includes or remove unused vendors. DKIM breaks when the selector is wrong or the key was rotated without updating DNS. PTR issues are fixed by your hosting or ESP, since they control the IP's reverse zone.
Frequently asked questions
- Do these requirements apply to me if I send low volume?
- The strict 5,000-per-day threshold triggers the full checklist, including DMARC and one-click unsubscribe. But smaller senders still benefit: Gmail and Yahoo now expect valid SPF and DKIM, a matching PTR record, and TLS from everyone. Passing all five signals improves inbox placement regardless of volume, so treating the checklist as a baseline is a safe practice.
- Why do I pass SPF and DKIM but still land in spam?
- Alignment is the usual culprit. DMARC requires that the domain in SPF or DKIM matches the visible From address. You can have a valid SPF and DKIM that authenticate a different domain, which fails DMARC alignment even though each record looks correct on its own. Check that your From domain is the one being signed and authorized, not just any domain.
- What DMARC policy should I start with?
- Begin with p=none, which monitors without affecting delivery, and add a rua address to collect aggregate reports. Once reports confirm your legitimate mail passes alignment, move to p=quarantine and eventually p=reject. Google and Yahoo accept p=none as the minimum, but staying there long-term leaves your domain open to spoofing, so treat it as a starting point, not a destination.