Account

What new tool do you want?

Developer Tools

DMARC, SPF & DKIM Checker

Check a domain's email authentication: SPF with its 10-lookup limit and every include, DMARC under the current RFC 9989 rules, and DKIM key strength, plus Gmail's sender requirements. Runs in your browser.

How to use

  1. 1Enter your domain or any email address at it.
  2. 2If you know your DKIM selector (the s= value in a message's DKIM-Signature header), add it; or paste a message's headers to find it. Common selectors are tried anyway.
  3. 3Press Check to see the SPF include tree and lookup count, the DMARC policy and tags, each DKIM key's size, and what to fix.

How it's calculated

SPF is evaluated like a receiver would (RFC 7208): every include, a, mx, ptr, exists and redirect costs one DNS lookup, with at most 10 in total and at most 2 that return nothing. DMARC policy discovery uses the DNS tree walk of RFC 9989, and external report addresses are checked for the authorisation record RFC 9990 requires. DKIM key sizes are read from the public key in the DNS record (RFC 6376, RFC 8301).

Frequently asked questions

What does "too many DNS lookups" mean for SPF?

Receivers stop evaluating SPF after 10 lookups and treat the result as a permanent error, so SPF fails for all your mail, not just some. Each include (Google Workspace, Microsoft 365, a newsletter service…) costs at least one lookup, plus whatever it includes. Remove services you no longer use, or ask a provider for a smaller include.

Should my SPF end with ~all or -all?

Both protect you. -all (fail) tells receivers that no other server may send for you; ~all (softfail) says other servers are probably not allowed. With DMARC in place, receivers act on the DMARC policy either way. Never use +all, which authorises every server on the internet.

Which DMARC policy should I use?

Start with p=none and an rua address to collect reports for a few weeks. When the reports show all your real mail passes, move to p=quarantine and then p=reject. Gmail requires DMARC from senders of more than 5,000 messages a day and accepts p=none.

What changed in DMARC in 2026?

RFC 9989 (May 2026) replaced RFC 7489. It retired the pct, ri and rf tags, added t=y for testing a policy, made np (the policy for non-existent subdomains) part of the standard, and replaced the public suffix list with a DNS tree walk to find the organisational domain. Old records keep working; the removed tags are just ignored.

Why wasn't my DKIM key found?

A DKIM key sits at <selector>._domainkey.<your domain>, and the selector is chosen by your mail service. This tool tries 27 common ones; if yours is different, open a message you sent, find the DKIM-Signature header and use its s= value.

Is anything stored?

No. Your browser asks public DNS-over-HTTPS resolvers (Google, then Cloudflare) directly.

Sources

Example: an SPF record that silently broke

A company lists seven services: include:_spf.google.com include:spf.protection.outlook.com include:servers.mcsv.net include:sendgrid.net include:mail.zendesk.com include:_spf.salesforce.com include:mailgun.org. Checked in November 2026, those cost 1, 1, 1, 2, 1, 2 and 5 lookups: 13 in all. Receivers give up after 10, so SPF fails for every message, including the ones from Google. Removing the Microsoft 365 include left over from a migration (1) and Mailgun, no longer used (5), brings it to 7 and SPF passes again. Providers change their records, so check the include tree here rather than relying on these numbers.

Example: reports that never arrive

A domain publishes rua=mailto:[email protected] but receives nothing. DMARC reports to another organisation's domain are only sent if that domain publishes a record named yourdomain._report._dmarc.dmarc-vendor.example. Reporting services normally set this up when you sign up; the check here shows whether it exists.

What DNS can't tell you

DMARC passes only if SPF or DKIM passes and is aligned with the From address. Alignment depends on the actual message, for example whether your newsletter service signs with your domain or its own. Send yourself a message through each service and look at the Authentication-Results header: dmarc=pass with the right header.from is what counts.

Related tools

More: Developer Tools