Check a Domain's SPF, DKIM and DMARC Records

Looks up SPF, DMARC and DKIM records, MX hosts, DNSSEC signing and CAA restrictions for a domain, and explains what each gap lets an attacker do.

Public hosts only. About a handful of requests, usually finished in under 15 seconds. How we scan · Acceptable use

Illustration of the email security checker (spf, dkim, dmarc) in use

How it works

  1. Enter the domain

    We resolve the registrable domain (example.co.uk, not mail.example.co.uk).

  2. DNS lookups only

    SPF and DMARC are parsed; 40 common DKIM selectors are probed; DS records reveal DNSSEC.

  3. Move to enforcement

    The report tells you whether DMARC is actually rejecting spoofed mail or only watching it.

What this tool checks

8 checks across 1 areas. Each links to its reference page with the test, the risk and the fix.

Full reference

DNS and email authentication

8 checks

The ones that most often decide the grade:

Guides for this tool

Background reading written to go with these results.

Frequently asked questions

My domain sends no email. Do I still need SPF and DMARC?

Yes. A domain with no records can be spoofed freely. Publish v=spf1 -all and a DMARC record with p=reject.

Why can't you find my DKIM record?

DKIM lives under a selector name only you and your mail provider know. We try 40 common ones; a custom selector will not be found, which does not mean it is missing.

What is the difference between p=none and p=reject?

p=none asks receivers to report failures and deliver anyway. p=reject asks them to refuse the message. Only reject and quarantine actually stop spoofing.

How many DNS lookups can SPF use?

Ten, per RFC 7208. More than that and receivers return a permanent error, which is treated like no SPF at all.