SPF & DMARC checker

Look up MX records, parse the SPF policy (including DNS lookup count and the all qualifier) and read the DMARC policy for a public domain.

Enter a public domain name. Private, loopback and local addresses are not allowed.

How to read the result

Enter a public domain. This server looks up MX records, the SPF TXT record (v=spf1) and the DMARC record at _dmarc.<domain>. It does not send test mail and it does not validate DKIM signatures.

Only public domain names are accepted. Private, loopback and local names are blocked. Related tools: DNS lookup for raw records, and uptime monitors if you want this watched on a schedule.

Frequently asked questions

What is an SPF record?

SPF (Sender Policy Framework) is a TXT record on your domain that lists which mail servers may send email as that domain. Receiving servers look it up when a message arrives and can treat unauthorized senders as fail, softfail or neutral, depending on how the record ends.

What does the 10 DNS lookup limit mean?

When a receiver evaluates SPF, some terms cause extra DNS queries: include, a, mx, ptr, exists, and redirect. RFC 7208 limits those to 10 in total, including nested includes. This checker counts them the same way and flags a policy that goes over the limit, which receivers may treat as a permanent error.

What is the difference between -all and ~all?

Both come at the end of an SPF record and apply to senders that did not match an earlier term. -all is fail: the message is not authorized. ~all is softfail: the message is suspicious but many inboxes still accept it. +all (or a bare all) allows any host and should be avoided. A missing all, and no redirect, is treated as neutral.

What is a DMARC record?

DMARC is a TXT record at _dmarc.yourdomain that tells receivers what to do when a message fails SPF or DKIM alignment. The p= tag is the policy: none (monitor only), quarantine, or reject. rua= is where aggregate reports should be sent. If there is no record at the exact hostname, receivers may use the organizational domain’s policy.

Why is p=none not enough on its own?

p=none is useful while you watch reports, but it does not ask receivers to quarantine or reject unauthorized mail. Moving to quarantine or reject, with a working rua= address, is what actually protects the domain from spoofing.