Email Tools

Email Security Summary

A combined overview of a domain's MX, SPF, DKIM, and DMARC configuration with an overall email security score.

Enter a domain for a combined overview of its MX, SPF, DKIM, and DMARC configuration, with an overall email security score.

More Email Tools

View all 8

Mail Server Lookup Email Header Analyzer SMTP Connectivity Checker DMARC Record Generator DMARC Checker SPF Checker DKIM Checker

JustChecker tracks your complete email security posture continuously and alerts you if anything regresses.

What Is the Email Security Summary?

It checks a domain's MX, SPF, DKIM and DMARC setup in one go and combines them into an overall email security score, with a list of what is missing.

When to Use It

As a quick health check of a domain's email setup.
When onboarding a client or auditing several domains.

How to Use It

Enter the domain.
Fix the missing or weak items first.

Understanding the Result

A strong setup has MX records, one valid SPF record, a published DKIM key and a DMARC policy of quarantine or reject.

Limitations

DKIM is only found under common selectors. The score reflects DNS configuration, not whether your emails actually reach inboxes, which also depends on content and sending reputation.

Frequently Asked Questions

It combines the presence and correct configuration of MX, SPF, DKIM, and DMARC into one overall picture - each missing or misconfigured piece reduces the score, since all four work together for genuinely secure, deliverable email.

Email authentication is inherently a combined system - SPF, DKIM, and DMARC specifically build on and reference each other, so a summary view surfaces gaps (like DMARC configured without underlying SPF/DKIM alignment) that checking each in isolation might miss.

Not necessarily - email can still function with an imperfect score, but each gap represents reduced protection against spoofing/phishing of your domain and, for some receiving servers, reduced deliverability confidence.

Missing or incomplete DMARC configuration is very common - many domains have basic SPF set up but never get around to adding DKIM and a DMARC policy, leaving meaningful gaps in their overall email authentication posture.

A sensible order is confirming MX works, then SPF, then DKIM, then DMARC last (since DMARC depends on the first two being correctly aligned) - trying to configure DMARC before SPF/DKIM are solid tends to cause more troubleshooting, not less.

No - it confirms your domain's authentication configuration is technically correct, but actual inbox placement also depends on sender reputation, content, and each receiving provider's own independent spam-filtering algorithms.