Deliverability Quick-Check
By Carlos Gil, Founder & Editor, The Best Network · Updated
You can write the best email of your life and still send it from a domain Gmail can’t verify. Since February 2024, Google has required senders to authenticate, and bulk senders without SPF, DKIM and DMARC are the first to find out what that means.
Enter your sending domain. Add the DKIM selector from your email platform’s domain settings if you want the DKIM key checked as well. It takes a few seconds and tells you what each record does, not just whether it exists.
Key takeaways
- Google requires every sender to Gmail to use SPF or DKIM, and senders of more than 5,000 messages a day to use SPF, DKIM and DMARC (rules in force since February 1, 2024).
- DMARC p=none is valid and meets the Google and Yahoo requirement, but it only monitors; it does not stop spoofing.
- Two SPF records, or more than 10 DNS lookups, make SPF fail for every message (RFC 7208).
- A record that exists can still be wrong for your platform, so confirm the exact values in its authentication settings.
What each result means
SPF lists the servers allowed to send for the domain. The checker reads the ending: -all rejects unlisted servers, ~all marks them suspicious, and a missing or duplicate record is a failure.
DMARC tells receivers what to do when mail claiming your domain fails authentication. p=none monitors, p=quarantine sends failures to spam, p=reject blocks them. Monitoring is a fine start and a poor place to stay.
DKIM is checked only when you give a selector, because each platform publishes its key under its own name (for example selector._domainkey.yourdomain.com).
BIMI is optional. It lets supporting inboxes show your logo, and it requires DMARC at enforcement to work.
Which result should you fix first?
Read the icons before the details. Green means the record exists and does its job. Amber means it’s valid but weak. Red means it’s missing or broken, so receivers will treat your mail as unauthenticated. Gray is information, such as DMARC in monitoring mode or a check you skipped.
Then work in this order:
- Red SPF. A missing record, two records or +all. Google requires SPF or DKIM from every sender, and +all lets anyone send as you.
- Red DKIM. A missing or revoked key. Senders of 5,000 or more messages a day to Gmail need SPF and DKIM together.
- Red DMARC. No record at _dmarc. Publish p=none today; it meets the Google and Yahoo bulk-sender rule.
- Amber SPF. End the record in ~all or -all instead of ?all or nothing.
- Gray DMARC p=none. Read the reports, fix any sender that fails, then move to quarantine.
- BIMI. Last, and only after DMARC is enforced.
After you change a record, give it time. Google says SPF can take up to 48 hours to start working, so run the check again before you assume the fix failed.
What it can’t tell you
DNS records are the entry ticket, not the inbox. This checker doesn’t send mail, so it can’t see alignment on real messages, your spam complaint rate or how Gmail ranks your reputation. For those, send a test to a Gmail address, open Show original and look for PASS next to your own domain, and set up Google Postmaster Tools.
How this tool works
Lookups go from your browser to Google Public DNS (dns.google). Nothing is stored. A record that exists can still be misconfigured for a particular email platform, so confirm the exact values in that platform’s authentication settings.
Sources
Checked October 19, 2026.
What to do next
Anything red gets fixed before your next campaign. If SPF and DKIM pass and DMARC sits at p=none, read your aggregate reports for a few weeks, fix the senders that fail, and move to quarantine.
Authentication won’t make people want your email. Without it, they never get the chance to decide.
FAQ
Is DMARC p=none a failure?
No. p=none is a valid DMARC policy and satisfies the Google and Yahoo bulk-sender requirement to publish DMARC. It only monitors: spoofed mail is still delivered. Move to quarantine or reject once your reports show legitimate mail passing.
What's the difference between SPF ~all and -all?
~all (softfail) tells receivers that unlisted servers are probably not allowed, so the mail is usually accepted but treated as suspicious. -all (fail) says they are not allowed, so it may be rejected. Both are acceptable; -all is stricter.
Why does the DKIM check need a selector?
DKIM keys are published at selector._domainkey.yourdomain, and each email platform picks its own selector name. Without it there is no single place to look, so find the selector in your platform's domain authentication settings.