Free tool

SPF, DKIM & DMARC Checker

Enter a domain to check its email authentication setup — see what's passing, what's missing, and how to fix it.

Free, no sign-up. Lookups run via public DNS-over-HTTPS — your domain isn't stored anywhere.

Short answer: This tool checks whether your domain has valid SPF (authorized senders), DKIM (signed mail), DMARC (enforcement policy), and MX (mail routing) records — the four DNS records that prove your email is legitimate.

What each record does

RecordPurposeLives at
SPFAuthorizes which servers can send for your domainTXT on the domain itself
DKIMSigns each message to prove it wasn't alteredTXT at <selector>._domainkey.domain
DMARCPolicy for what to do on SPF/DKIM failureTXT at _dmarc.domain
MXWhere incoming mail for your domain is routedMX on the domain itself

Fixing what the checker flags

MailPilot

Passing auth isn't the whole picture

Correct SPF/DKIM/DMARC stops spoofing — but sender reputation still decides inbox vs. spam. MailPilot warms up your mailbox to build that trust automatically.

Start free warmup

SPF, DKIM & DMARC checker — FAQ

What do SPF, DKIM, and DMARC do?

SPF lists which mail servers are allowed to send email for your domain. DKIM cryptographically signs each message so receivers can verify it wasn't altered. DMARC tells receiving servers what to do when SPF or DKIM fail, and lets you monitor who's sending as you. Together they prove your mail is legitimate — missing any one makes providers treat your mail as unverified.

Why did my DKIM check come back missing?

DKIM records live at a selector-specific subdomain, like google._domainkey.yourdomain.com — if you pick the wrong selector for your provider, the record won't be found even though it exists. Try your provider's default: Google Workspace usually uses “google”, Microsoft 365 uses “selector1” or “selector2”. Check your provider's admin panel for the exact selector if none of the presets match.

What does p=none mean in my DMARC record?

p=none is monitor-only mode — DMARC reports are generated, but no enforcement happens: mail that fails SPF/DKIM still gets delivered normally. It's the right starting point while you verify your setup, but you should move to p=quarantine and then p=reject once you confirm legitimate mail isn't failing, or you get no real protection against spoofing.

Do I need all three records, or is one enough?

You need all three for full protection. SPF alone can be bypassed by forwarding. DKIM alone doesn't tell receivers what to do on failure. DMARC ties SPF and DKIM together and enforces a policy — but DMARC only works if at least one of SPF or DKIM is set up correctly underneath it.

Is this checker free and does it store my domain?

Yes, completely free with no sign-up. Lookups run through public DNS-over-HTTPS resolvers directly from your browser — we don't store, log, or see the domains you check.