All tools

SPF & DMARC Checker

Network

Look up a domain's SPF and DMARC records, explain every term, count SPF DNS lookups against the limit of 10, and flag common mistakes

Loading tool…
Was this tool helpful?
spfdmarcemaildnsdeliverabilitytxtlookupemail-security

About SPF & DMARC Checker

Enter a domain and see its SPF record at the root and its DMARC record at _dmarc.<domain>, with every mechanism and tag explained in plain English. The SPF check follows each include and redirect to total the DNS lookups a receiver would make, because going over 10 makes SPF return permerror and quietly fail for all of your mail, which is the most common way a record that looks fine breaks. It also flags +all and ?all, a missing all, duplicate SPF records, includes that point at domains with no SPF record, p=none, a pct below 100, sp=none and a missing rua address. You can also paste records you are about to publish and check them before they go live.

How to use SPF & DMARC Checker

  • 1.Enter a domain (a URL or an email address works too) and press Check to fetch and analyze its live SPF and DMARC records, including the full include tree and the total lookup count.
  • 2.Switch to Paste records to check an SPF or DMARC record you are drafting, before you add it to DNS.
  • 3.Fix the errors first (they make SPF or DMARC fail outright), then work through the warnings, such as moving from p=none to quarantine once your aggregate reports look clean.

Frequently asked questions

Why does the 10 DNS lookup limit matter?
RFC 7208 caps an SPF check at 10 terms that need a DNS query (include, a, mx, ptr, exists and redirect, counted across every nested include). Past that, receivers return permerror and SPF fails for every message, so a record that grew one include too many can break delivery for the whole domain.
Does it check DKIM too?
No. A DKIM key lives at <selector>._domainkey.<domain>, and the selector name is chosen by each sending service and is not discoverable from DNS, so a checker can only test DKIM if you already know the selector. Use the Email Header Analyzer on a received message to see DKIM results.
Where does the lookup run?
In the browser, the domain's TXT records are fetched from Cloudflare's public DNS-over-HTTPS resolver, so results can lag a recent DNS change by up to the record's TTL. Pasted records are checked locally and never leave the page. The REST API does the same lookup server-side, while the SDKs and MCP tool only check record text you pass in.
Is ~all or -all better?
-all (fail) is the strictest, but most domains use ~all (softfail) with DMARC at quarantine or reject, since DMARC decides what happens to failing mail. The checker treats both as fine and flags +all, ?all or a missing all.

Use via API, SDK, or MCP

cURL# Free: 1,000 req/day · Pro: 10,000 req/day
curl -X POST https://api.utilix.tech/v1/tools/spf-dmarc-checker \
  -H "Authorization: Bearer utx_live_..." \
  -H "Content-Type: application/json" \
  -d '{"domain":"github.com","spf":"v=spf1 ip4:192.0.2.0/24 include:_spf.google.com ~all","dmarc":"v=DMARC1; p=quarantine; rua=mailto:dmarc@example.com"}'

Get an API key from your dashboard · Full API docs →