TROUBLESHOOTING GUIDE
SPF, DKIM and DMARC explained: check your email security records
SPF, DKIM and DMARC are DNS records that let receiving mail servers check that an email really came from the domain it claims. They are public, so anyone can look them up. Our email security check reads them for any domain in a few seconds.
Reviewed
Likely causes
SPF lists the servers allowed to send email for a domain. DKIM adds a cryptographic signature that receivers verify against a public key published in DNS. DMARC tells receivers what to do when an email fails both checks, and where to send reports. A missing or broken record makes spoofing easier and can send genuine email to spam, especially at large mailbox providers that now require authentication.
Steps for visitors
Change one thing at a time. Keep certificate warnings, firewalls and other security protections in place. Ask your administrator before changing a managed network.
Check the domain’s records
Enter the domain on our email security check. It looks up the MX, SPF and DMARC records and tries common DKIM selectors.
What the result means: A pass for SPF and DMARC with at least one DKIM key found is a good baseline. A missing record is the first thing to fix.
Make sure there is exactly one SPF record
The domain must publish a single TXT record starting v=spf1. Merge several records into one, and end it with ~all or -all.
What the result means: Two SPF records make SPF fail for every email. More than 10 DNS lookups inside the record also causes a failure.
Find the DKIM selector
Open the headers of an email sent from the domain and look for DKIM-Signature. The s= value is the selector. Enter it in our check if the common selectors were not found.
What the result means: If a key is found, receivers can verify signatures. If none is found, turn on DKIM signing in your email provider’s settings.
Start DMARC in monitoring mode
Publish a TXT record at _dmarc.yourdomain with v=DMARC1; p=none and a rua address for reports. Review the reports for a few weeks.
What the result means: Monitoring shows which services send email for you. Once they all pass, move to p=quarantine and then p=reject to stop spoofing.
Re-check after DNS changes
DNS changes can take time to spread, depending on the record’s time to live. Run the check again later.
What the result means: If the old record still shows, wait and try again. Our check uses our server’s DNS resolver, which may cache answers briefly.
Check a domain’s email records
Our email security check reads public DNS records only. It does not send any email or store the domains you check.
If you own the website
Make one person responsible for every service that sends email for the domain, such as your mailbox provider, newsletter tool and website contact forms. Add each to SPF or have it sign with DKIM for your domain. Keep DMARC reports going to a monitored mailbox, and tighten the policy only when legitimate senders pass.
Who to contact
Your email provider’s help pages give the exact SPF include and DKIM records to publish. Your domain registrar or DNS host makes the changes. If someone is spoofing your domain, a DMARC policy of quarantine or reject is the main defence.
Sources and further reading
These provider documents support the technical explanations. The comparisons above narrow the investigation; they cannot diagnose every network or service.