How well is your domain’s email protected?
SPF, DKIM, DMARC, MX, MTA-STS and BIMI of any domain, read from public DNS, with a plain-language fix for each problem.
Your input is sent to our server to run the check. We don't log it. Public check targets and results may be cached temporarily to avoid repeating checks.
For example example.com, without https:// or a path.
More options
The s= value of a DKIM-Signature header, such as selector1. Leave empty to try the common ones.
Email protection
Ready to check
Enter an address and press Check.
- Who may send (SPF)
- Signatures (DKIM)
- What to do with fakes (DMARC)
- Receives mail (MX)
SPF, DKIM, DMARC, MX, MTA-STS and BIMI of any domain, read from public DNS, with a plain-language fix for each problem.
How to use
- Type the domain you send email from, such as example.com, without https:// or a path.
- If you know your DKIM selector (your mail provider lists it), enter it. Otherwise leave it empty and the common ones are tried.
- Press Check. The verdict and each check appear with what to fix; the records found are listed below.
How it works
Anyone can write any address in the From line of an email. Three records in the domain's DNS let receiving mail servers tell real mail from fake: SPF lists the servers allowed to send for the domain, DKIM publishes the key that checks a digital signature on each message, and DMARC says what to do with mail that fails, and where to send reports. MX records say where mail for the domain is received. MTA-STS (encrypted delivery) and BIMI (a logo next to your messages) are optional extras.
SPF allows at most 10 terms that cause a DNS lookup (include, a, mx, ptr, exists, redirect); above that receivers treat the record as broken. A record such as v=spf1 include:_spf.example.net -all has 1 of 10, and ends in -all, so unlisted senders fail. DMARC then turns the results into action: p=none only reports, p=quarantine sends fakes to spam and p=reject refuses them. Sources: RFC 7208 (SPF), RFC 6376 (DKIM), RFC 9989 (DMARC), RFC 8461 (MTA-STS), RFC 7505 (null MX).
The check reads public DNS only. A DKIM key lives under a selector name the sender chooses, so only the selectors tried can be found: a missing key may just have another name. Lookups inside included SPF records are not counted, a subdomain does not inherit its parent's DMARC policy here, and the MTA-STS policy file is not fetched.
Sources
- IETF RFC 6376: DomainKeys Identified Mail (DKIM) SignaturesUsed for: definitions
- IETF RFC 7208: Sender Policy Framework (SPF)Used for: definitions, limits and cut-offs
- IETF RFC 7505: A "Null MX" No Service Resource RecordUsed for: definitions
- IETF RFC 8461: SMTP MTA Strict Transport Security (MTA-STS)Used for: definitions
- IETF RFC 9989: Domain-Based Message Authentication, Reporting, and Conformance (DMARC)Used for: definitions
Frequently asked questions
Why does my email go to spam?
Missing or broken SPF, DKIM and DMARC are a common reason, and large mailbox providers require all three from bulk senders. Fix the failing checks first; content and sending reputation matter too.
What is a DKIM selector?
A name that tells receivers where to find the key: selector._domainkey.yourdomain. Your mail provider chooses it; it appears as s= in the DKIM-Signature header of a message you sent.
Why does it say DKIM not found when I use DKIM?
Only a few common selectors are tried. Enter the selector from your provider or from a message header to check it.
Which DMARC policy should I use?
Start with p=none and a report address, read the reports until all your real senders pass, then move to quarantine and reject.
Why is a domain that sends no mail still worth protecting?
Attackers forge unused domains too. Publish v=spf1 -all and a DMARC record with p=reject so receivers refuse mail claiming to come from it.
Do I need MTA-STS or BIMI?
No. MTA-STS makes other servers deliver to you over verified encryption; BIMI shows your logo in some inboxes, and needs an enforced DMARC policy. Both are optional.





