Email security check
Email security check for your domain
Enter a domain and get a 0–100 score covering DMARC, SPF, DKIM, MX, blocklists and BIMI — with what each point means and what to fix first.
We check public DNS and public BIMI files over HTTPS. No email is sent.
Example result
Sample data, not a live check. Run the tool above to see your own result.
Result for
acme.example
Strong checked configuration
Each check below shows the points earned and a link to the detailed tool.
Details
- DMARC policy
- p=reject asks receivers to reject DMARC failures; local handling can differ. 30/30 Details →
- SPF record
- Valid record ending in -all. 25/25 Details →
- DKIM keys
- DKIM key of 2048 bits or Ed25519. 20/20 Details →
- MX records
- MX records resolve correctly. 10/10 Details →
- Blocklists
- Mail servers are not on the checked blocklists. 10/10 Details →
- BIMI logo
- BIMI record and logo look valid. 5/5 Details →
What to do with the result
The DMARC row says there is no record
The tool found no usable DMARC policy, the rule that tells receivers how to treat mail that fails authentication. A record with a missing or invalid p= value shows the same message, so look it up in the DMARC Checker first.
If nothing is there, publish one TXT record at _dmarc.example.com:
v=DMARC1; p=none; rua=mailto:dmarc@example.com
With p=none receivers handle mail as before, and rua names the mailbox for reports. Start here: under a stricter policy, mail from a forgotten sender could go to spam or be refused. Keep a single record, because receivers discard them all when they find two.
DMARC exists, but enforcement or reports are incomplete
With p=none you state no preference, so receivers treat spoofed mail as before. Without rua you get no aggregate reports, the XML summaries of who sends mail as your domain. Add that address first.
- Read the reports until every legitimate sender passes DMARC. This can take months.
- Move to
p=quarantine, then decide onp=reject. Mail from a sender you missed can land in spam or be refused.
RFC 9989 section 7.4 says domains at p=reject must sign with DKIM, and that domains whose users might post to mailing lists should not publish it. The same RFC removed pct, so do not use it to phase in a policy.
SPF is missing or returns an error
SPF lists the servers allowed to send for your domain. This row shows 0 of 25 without a record and 5 when the record is broken. Two common causes are a second SPF record and more than 10 DNS lookups. Each produces a permerror, a permanent error, so the message gets no SPF pass.
- Merge everything into one
v=spf1TXT record. Never add a second one for a new sender. - Remove
include:entries for services you stopped using. The SPF Flattening Tool can help if you are still over 10. - Before you publish
-all, confirm every sender is listed. Receivers may reject mail from unlisted servers.
DKIM shows zero or a short key
Zero means no key turned up under the selectors (key names) this scan tries. Check a real message: send one to a mailbox on another service and paste its headers into the Email Header Analyzer.
- No
DKIM-Signatureheader means signing is off. Turn it on in each sending service. s=is your selector. Test it in the DKIM Checker.- If
d=is outside your domain, that signature cannot count for DMARC.
A 1024-bit key scores 14 of 20. To reach 2048 bits, publish the new key under a new selector and switch signing only after it appears in DNS. Keep the old key until mail signed with it has arrived.
Your domain or server appears on a blocklist
This row tests up to three IP addresses, taken from your MX hosts and the domain itself, plus the domain name on domain lists. Those IPs may be your inbound or web servers instead of the one that sends your mail.
Open the Blacklist Check to see which list and target were hit, and test your real sending IP there too. You can read it in the Received headers of a message you sent. Fix the cause, then follow that list’s removal steps. Some lists cover whole networks: UCEPROTECT Level 3 lists every IP of an autonomous system (a provider’s network), so other customers can affect you.
Explained
What this score measures
The score combines six public configuration checks: DMARC (30), SPF (25), DKIM (20), MX (10), blocklists (10) and BIMI (5). It inspects DNS and public BIMI files over HTTPS. This snapshot is not a certification or proof that every message authenticates or reaches an inbox.
How to raise your score
- Inspect your existing DMARC record and preserve its policy. Add a reporting address to that record; start at
p=noneonly if no record exists. - Authorize services that use this domain as their SPF MAIL FROM domain, within the 10-term limit.
- Enable aligned DKIM signing in each sending service.
- Review reports and test legitimate mail before considering
p=quarantine. Assessp=rejectseparately: forwarding and mailing lists can break authentication.
Frequently asked questions
What is a good email security score?
Why is my DKIM score zero when I do use DKIM?
Is BIMI required?
Can I share my score?
How often should I check?
Keep it healthy
Know the moment something breaks
Point your DMARC reports to DMARC Pulse and see who sends email as your domain, what fails and why — with a calm alert when anything changes.
Free plan: 1 domain, no credit card.
Related tools