Free Email Security Checker (SPF, DKIM, DMARC)
Check your domain's email authentication · SPF, DKIM, and DMARC · and see if you're vulnerable to spoofing.
Free account required to run the check. What you type here is kept through sign-in.
How to use it
- Enter the domain you send email from, for example example.com.
- Run the check. SimplyScan looks up the domain's MX, SPF, DMARC and DKIM records in public DNS.
- Read the grade and the failed checks. Each one explains what is missing and how to fix it.
- Add or change the records at your DNS provider, wait for DNS to update, and run the check again.
Example
A domain that has SPF and DKIM but only monitors spoofed mail.
Input
example.com
Result
SPF v=spf1 include:_spf.google.com ~all DMARC v=DMARC1; p=none DKIM found on selector: google ✗ DMARC policy enforces (not p=none) ✗ DMARC aggregate reporting (rua): Not set ✓ MX records present · ✓ Exactly one SPF record · ✓ SPF ends with ~all
What each record does
- SPF
- A TXT record listing the servers allowed to send mail for your domain. You need exactly one, ending in -all (reject) or ~all (soft fail). +all lets anyone send as you.
- DKIM
- A public key in DNS that receivers use to check your mail's signature. The tool tries five common selectors: default, google, selector1, selector2 and k1. If your provider uses another selector, DKIM can be set up correctly and still show as not found.
- DMARC
- Tells receivers what to do with mail that fails SPF and DKIM. p=none only monitors it, while p=quarantine sends it to spam and p=reject blocks it. Without DMARC, receivers decide for themselves.
- rua reporting
- A rua=mailto: address in DMARC means receivers send you daily reports of who is sending mail as your domain. Read them before you move from p=none to enforcement.
- MX records
- Where mail to your domain is delivered. A sending-only domain can skip them, but most domains need them.
Records to publish
Change the include to match your email provider. Your provider's help pages give the exact SPF include and DKIM record.
SPF (TXT record on example.com)
v=spf1 include:_spf.google.com ~all
DMARC, starting point (TXT record on _dmarc.example.com)
v=DMARC1; p=none; rua=mailto:dmarc@example.com
Collect reports for a couple of weeks, check every real sender passes, then change p=none to p=quarantine and later p=reject.
DMARC, enforced
v=DMARC1; p=quarantine; rua=mailto:dmarc@example.com
Go deeper
Page updated
Frequently asked questions
Which DKIM selectors are checked?
The tool probes the five most common selectors: default, google, selector1, selector2, and k1. If your provider uses a different selector, no DKIM record will be reported.
What is a weak DMARC policy?
A DMARC record with p=none tells receivers to only monitor · not reject or quarantine · unauthorized mail. That leaves your domain effectively spoofable. Move to p=quarantine or p=reject.
Do I need this if I only send password resets?
Yes. Without DMARC enforcement, anyone can send mail that claims to come from your domain, including fake password-reset emails to your users.
Why does DKIM show as missing when my provider says it's on?
Your provider probably uses a selector outside the five this tool checks. Find the selector in your provider's DNS instructions or in an email header (the s= value in the DKIM-Signature line).
Can two SPF records cause problems?
Yes. Receivers treat more than one SPF record as an error, and SPF then fails for all your mail. Merge them into one record with several include: entries.
Want the full picture?
This tool covers one narrow check. A full SimplyScan runs 60 checks across 14 categories · exposed keys, RLS, XSS, auth, and speed · in 30 seconds.
Run a full security scanRelated tools
DNS Security Checker
Check whether a domain is protected by DNSSEC and restricts certificate issuance with CAA records · two defenses against DNS hijacking and rogue certificates.
DNS Lookup
Query any domain's DNS records live · A, AAAA, CNAME, MX, TXT, NS, and CAA · resolved over encrypted DNS-over-HTTPS.
security.txt Validator
Check whether a site publishes a valid security.txt · the RFC 9116 file that tells researchers how to responsibly report vulnerabilities.