How this checker works
- Your browser asks public DNS for three things: your mail servers (MX), your SPF record and your DMARC record. It also follows every include in your SPF record to count the lookups.
- Each record is read against the current standards (RFC 7208 for SPF, RFC 9989 for DMARC). Every finding comes in plain English, with the technical detail one click away.
- If a lookup fails, we say so instead of guessing. DKIM can't be checked without its selector name, so we ask for it rather than calling it missing.
How an SPF record works, and the 10-lookup limit
An SPF record is one TXT record at your domain that starts with v=spf1 and lists every service allowed to send email as you, for example v=spf1 include:_spf.google.com include:mailgun.org ~all. The ending says what happens to everyone else: ~all marks them as suspicious and -all fails them.
- You can have only one SPF record. Two make SPF fail for every email.
- Each include, a, mx, exists and redirect costs a DNS lookup, and so do the includes inside them. Over 10 lookups and SPF fails (RFC 7208). The checker above counts them for you.
- Keep all at the very end: anything after it is ignored. Never use +all, which lets anyone send as you.
How to check a DMARC or SPF record yourself
On macOS or Linux, run dig +short TXT _dmarc.yourbusiness.com for DMARC and dig +short TXT yourbusiness.com for SPF. On Windows, use nslookup -type=TXT _dmarc.yourbusiness.com. You'll see the raw record; the checker above also explains it and counts the SPF lookups.