SPF, DKIM, DMARC checker. Email shield triple.
Type a domain. The tool queries the three TXT records that authenticate your email — SPF (allowed senders), DMARC (policy), and DKIM (with selector). Inline validator covers all three.
Type a domain plus an optional DKIM selector. The tool queries SPF (TXT on root), DMARC (TXT on _dmarc.domain), and DKIM (TXT on selector._domainkey.domain) via Cloudflare DoH. Inline validator covers SPF lookup count, DMARC policy strictness, and DKIM presence.
Most common DKIM selectors: google (Google Workspace), selector1 + selector2 (Microsoft 365), k1 / k2 (Mailchimp).
// no query yet
Sources used by this checker
- RFC 7208 — SPF · RFC 6376 — DKIM · RFC 7489 — DMARC
- Gmail / Yahoo bulk-sender enforcement (Feb 2024)
- SPF 10-lookup limit triggers permerror — the most common email-auth bug.
Privacy: queries go to Cloudflare DoH; Digital Heroes doesn't log.
Six questions users ask.
What do SPF, DKIM, and DMARC do?
SPF lists allowed senders. DKIM cryptographically signs each email. DMARC tells receivers what to do on failure (none / quarantine / reject). All three required by Gmail + Yahoo as of February 2024.
What's the SPF lookup limit?
10 lookups max. Each include: counts as 1. Over the limit = permerror, mail rejected.
Why does DMARC need a DKIM selector?
DKIM keys are stored at selector._domainkey.yourdomain.com. Common selectors: 'google', 'selector1', 'k1'. Find yours in the email's DKIM-Signature header.
Should DMARC be 'reject' or 'quarantine'?
Aim for reject. Start at 'none' for monitoring, then 'quarantine', then 'reject' over 4-8 weeks.
What's pct= in DMARC?
pct=N controls what percent of failing mail gets the policy applied. pct=10 = only 10% policy-applied. Useful for gradual rollout.
Does this tool log my queries?
Digital Heroes doesn't log. Cloudflare DoH logs anonymized queries per their resolver privacy policy.