DMARC, SPF & DKIM checker

Enter a domain to read its SPF, DKIM and DMARC records, count SPF lookups, check DKIM key sizes and get a plain-language verdict with the fixes in the right order. Free, no sign-up.

DKIM selector (optional)

The selector is shown in your provider's DKIM settings, or in the s= tag of the DKIM-Signature header of a message you sent. Separate several with commas. Without it, 76 common selectors are tried.

DNS queries are sent to Cloudflare's and Google's public resolvers over HTTPS. Nothing else leaves your browser and no result is stored.

What the checker looks at

SPF

  • Exactly one v=spf1 record
  • Syntax of every mechanism and modifier
  • DNS lookups counted through every include and redirect (limit 10)
  • Void lookups (limit 2), include loops, missing includes
  • The final all qualifier and terms placed after it

DKIM

  • Common selectors of Google, Microsoft, Zoho, Proton, Mailchimp, SendGrid and others, plus any selector you enter
  • RSA key length read from the public key (1024 vs 2048 bits)
  • Revoked keys, testing mode (t=y), hash restrictions
  • CNAME selectors that point to nothing (half-finished Microsoft 365 setups)

DMARC

  • Exactly one valid v=DMARC1 record at _dmarc
  • Policy strength: p=, sp=, pct=
  • Reporting addresses and the authorisation record required when reports go to another domain
  • Alignment modes and unknown tags
  • Policy inherited from the organisational domain on subdomains

How to read the grade

GradeMeaning
AValid SPF, enforced DMARC (quarantine or reject), DKIM healthy or not verifiable without your selector.
BEssentials in place with a few warnings, such as a 1024-bit DKIM key or a partial pct.
CDMARC in monitoring mode (p=none) or significant SPF warnings.
DSPF exists but no enforced DMARC policy, or broken records.
FNo SPF and no DMARC. The domain can be spoofed freely.

The grade is a reading aid, not a certification. Receivers combine authentication with reputation, content and engagement signals.

Fix it with a step-by-step guide

Google Workspace

Set up SPF, DKIM and DMARC in the Admin console and your DNS.

Read the guide →

Microsoft 365

SPF include, the two DKIM CNAMEs and DMARC for Exchange Online.

Read the guide →

Reading a DMARC report

Decode the XML aggregate reports receivers send you.

Read the guide →

From p=none to p=reject

Enforce your policy without losing legitimate mail.

Read the guide →

Frequently asked questions

What does DMARC do?

DMARC (Domain-based Message Authentication, Reporting and Conformance) is a DNS record that tells receiving mail servers what to do with messages that claim to come from your domain but fail SPF and DKIM alignment: do nothing (p=none), send them to spam (p=quarantine) or refuse them (p=reject). It also asks receivers to send you reports about who is sending mail in your name.

Why does DKIM show "Not verified"?

DKIM keys are published under a selector name chosen by each sending service (for example google._domainkey or selector1._domainkey). There is no way to list every selector of a domain, so this checker tries the most common ones. If yours is not among them, enter it in the DKIM selector field: you will find it in your provider’s DKIM settings or in the s= tag of a DKIM-Signature header.

Does p=none protect my domain?

No. With p=none receivers still deliver mail that fails authentication; they only send you reports. It is the right first step to discover every legitimate sender, but protection only starts with p=quarantine and is complete with p=reject.

Why does my SPF record fail with "too many DNS lookups"?

RFC 7208 limits SPF evaluation to 10 DNS lookups. Every include:, a, mx, ptr, exists: and redirect= counts, including the ones nested inside your providers’ includes. Past 10, receivers return a permanent error and your SPF fails for everyone. The lookup tree in the SPF card shows exactly where the lookups come from.

How long do DNS changes take to show up?

Usually a few minutes, but up to the TTL of the old record (often one hour, sometimes 24 hours or more). This checker queries public resolvers, which may still cache your previous record for that long.

Is anything stored when I run a check?

No. The checker runs in your browser and sends only DNS queries to Cloudflare’s and Google’s public resolvers over HTTPS. There is no server-side log, no account and no cookie.