SPF, DKIM and DMARC checker

Free SPF, DKIM and DMARC checker: test a domain’s email authentication records, count SPF lookups against the limit of 10, and get plain-English fixes.

Laptop showing code next to a coffee mug

Enter the domain you send email from. The checker reads its MX, SPF, DKIM and DMARC records and tells you, in plain English, what is set up correctly and what to fix. These three records are what Gmail, Outlook and Yahoo use to decide whether your mail is genuine or spam.

What each check means

RecordWhat it doesWhat the checker looks for
MXSays which servers receive your mailAt least one, or a deliberate “null MX”
SPFLists the servers allowed to send as your domainExactly one record, ending in ~all or -all, with 10 or fewer DNS lookups
DKIMSigns each message so receivers can check it was not alteredA published key of at least 1024 bits, ideally 2048
DMARCTells receivers what to do when SPF and DKIM fail, and where to send reportsOne record with a valid p= policy and a rua= report address

Finding your DKIM selector

DKIM keys are published at selector._domainkey.yourdomain, and only your email provider knows the selector. The checker tries the common ones, such as google, selector1 and selector2. If it finds nothing, open a message you sent, show its original headers, and find the line starting DKIM-Signature. The value after s= is your selector; enter it in the optional box.

ProviderUsual selector
Google Workspacegoogle
Microsoft 365selector1 and selector2
Zoho Mailzmail or a custom name
cPanel hostingdefault

The SPF 10-lookup limit

Each include:, a, mx, exists: and redirect= in an SPF record makes the receiver do a DNS lookup, and so do the includes inside those includes. Receivers stop at 10. Above that, SPF fails for every message, even legitimate ones. The checker follows every include and gives you the real total. To get under the limit, remove services you no longer send through, and replace includes with fixed ip4: ranges only where a provider publishes them.

A sensible starting setup

For a domain that sends through one provider, the records usually look like this:

example.com.         TXT  "v=spf1 include:_spf.google.com ~all"
_dmarc.example.com.  TXT  "v=DMARC1; p=none; rua=mailto:dmarc@example.com"

Add the DKIM key your provider gives you, wait a week or two, read the DMARC reports, then move the policy to p=quarantine and later p=reject. The full walkthrough is in how to set up SPF, DKIM and DMARC.

Domains that never send email

Protect them from spoofing with a record that allows no senders at all:

example.com.         TXT  "v=spf1 -all"
_dmarc.example.com.  TXT  "v=DMARC1; p=reject;"

Questions people ask

Why does my email still go to spam when all checks pass?

Authentication proves mail is really from you; it does not prove it is wanted. Sending reputation, content, complaint rates and a missing unsubscribe link all matter too. See why emails go to spam.

Do Gmail and Yahoo require DMARC?

Yes, for bulk senders. Since 2024 both require SPF, DKIM and a DMARC record from anyone sending large volumes to their users, and recommend them for everyone.

Can I have two SPF records?

No. A domain must have exactly one SPF record. With two, SPF returns a permanent error and every message fails. Merge them into a single record with all the includes.

Want this fixed rather than explained? Email authentication is one of the jobs we take on. Tell us the domain and we will tell you what is wrong with it.