No Signup Unlimited Usage Real Data 100% Free Privacy First Fast Results Export Reports Mobile Friendly

SPF, DKIM & DMARC Checker

Check a domain’s email authentication from live DNS: the SPF record with a recursive count of its 10 DNS lookups and the all qualifier, duplicate SPF records, DMARC policy (p=, rua=, pct=) and DKIM keys found on common selectors with their key length.

Fetching live data…

Quick answer

The SPF, DKIM & DMARC Checker reads a domain's email authentication records from live DNS and tells you whether they work. It counts the SPF record's DNS lookups recursively against the limit of 10, checks the all qualifier, looks for DKIM keys on common selectors and measures their length, and explains the DMARC policy, with a score and concrete fixes.

How it works

  1. Enter a domain such as example.com. You can paste a URL or an email address too; the tool keeps only the domain. If you know your DKIM selector, add it (several can be separated by commas).
  2. The tool reads the MX records and recognises the mail provider (Google Workspace, Microsoft 365, Zoho, Proton and others).
  3. It fetches the SPF record and follows every include: and redirect=, counting each DNS lookup the way receiving servers do.
  4. It reads DMARC at _dmarc. plus your domain, and falls back to the organizational domain for subdomains.
  5. It tries your selector and about 35 common ones at selector._domainkey. plus your domain, then reads each key's type and bit length.
  6. You get a score out of 100, prioritised issues with fixes, the raw records, an expandable include tree and copyable starter records.

What it checks

  • SPF record — exactly one TXT record starting with v=spf1. Two records cause a permanent error, so neither one is used.
  • 10-lookup limit — include, a, mx, ptr, exists and redirect each cost one DNS lookup, and nested includes add up. More than 10 means SPF fails at the receiver.
  • Void lookups and loops — terms pointing at names with no records (more than two is an error), includes that point back to themselves, includes without an SPF record, and mx terms with more than 10 hosts.
  • The all qualifier — -all (fail) and ~all (softfail) are fine; ?all is neutral and weak; +all lets anyone send as you. The deprecated ptr mechanism is flagged.
  • DKIM keys — key type (RSA or Ed25519), RSA length read from the public key, revoked keys (empty p=), test mode and the provider behind a CNAME. 1024-bit keys are marked weak, 2048-bit and longer good.
  • DMARC policy — p= (none, quarantine, reject), sp=, pct=, reporting addresses (rua=, ruf=), alignment modes and whether an external report address is authorised.
  • Extras — MX records, MTA-STS, TLS-RPT and BIMI, shown for information.

Why it matters

Email authentication decides whether your messages reach the inbox and whether others can send mail pretending to be you. Since February 2024 Google and Yahoo ask everyone who sends to their users to authenticate mail, and bulk senders to publish SPF, DKIM and a DMARC record (see the Google email sender guidelines). The rules themselves are written down in RFC 7208 (SPF) and RFC 7489 (DMARC). Most problems are quiet ones: an SPF record that grew past 10 lookups when a new tool was added, a second SPF record created by a hosting panel, or a DMARC policy left on p=none for years. None of them show up until mail starts going missing. Email is not a Google ranking factor, but password resets, order confirmations and newsletters that land in spam cost you customers all the same.

How to fix the most common problems

  1. Merge duplicate SPF records into one: a single v=spf1, all the include and ip4 terms together, and one ~all or -all at the end.
  2. Get under 10 lookups: remove includes for services you no longer use, replace a and mx with ip4: ranges where possible, or flatten includes and keep the list updated. The include tree shows which branch costs the most.
  3. Find your DKIM selector: open a message you sent, show the original headers and look for DKIM-Signature: … s=selector; d=yourdomain. Enter that selector here. If there is no signature, turn on DKIM in your mail provider and publish the record it gives you.
  4. Move DMARC step by step: start with v=DMARC1; p=none; rua=mailto:dmarc@yourdomain, read the reports for a few weeks, fix legitimate senders, then switch to p=quarantine and finally p=reject.
  5. Check the result again after the DNS change has propagated, and look up the other records with the DNS Records Lookup if something does not match.

Email records are one part of a domain's health. The Website Security Checker covers HTTP security headers, the SSL Certificate Checker checks the certificate, and the WHOIS Lookup shows who controls the domain.

Frequently asked questions

The tool found no DKIM key. Does that mean DKIM is off?

Not necessarily. DNS cannot list every selector a domain uses, so the tool can only try known names. Providers often use custom selectors. Look for the s= value in a sent message's DKIM-Signature header and enter it in the form to check that key.

Is ~all or -all better?

Both are acceptable. -all tells receivers to reject unlisted servers, while ~all marks them as suspicious. With an enforcing DMARC policy the difference is small, and ~all is safer while you are still finding all your senders. ?all and +all give little or no protection.

How are the 10 SPF lookups counted?

Every include, a, mx, ptr, exists and redirect costs one lookup, including those inside included records. ip4, ip6 and all cost nothing. The tool follows the whole chain and shows the count for each branch of the include tree.

Why does a subdomain show my main domain's DMARC record?

If a subdomain has no DMARC record of its own, receivers use the policy of the organizational domain (the sp= tag if present, otherwise p=). The tool does the same lookup and tells you which record applies.

Learn & Resources

Guides, tips and tutorials hand-picked for this tool — go from running a check to actually fixing it.