SecurityEdge resolution

Email Health

Comprehensive diagnostic of your SPF, DKIM, and DMARC configurations.

Quick presets
🩺

Email Security Diagnostic Suite

Enter a domain above to test SPF authorization, DMARC enforcement, and DKIM selector presence.

Technical specification & engineering details

What this tool does

Runs SPF, DKIM, and DMARC checks together and reports what's configured for each — the three mechanisms are related, so evaluating them as a set catches gaps that checking just one in isolation would miss.

How the three mechanisms work together

SPF publishes which servers are authorized to send mail for your domain. DKIM cryptographically signs outgoing mail so receivers can verify it wasn't altered in transit. DMARC ties the two together, telling receiving servers what to do when a message fails SPF or DKIM alignment, and where to send reports about it. A domain with only one or two of the three configured has a real gap a spoofer can exploit.

About the DKIM check specifically

Unlike SPF and DMARC, which live at fixed, predictable DNS locations, a DKIM record's location depends on the selector your mail provider chose — there's no way to discover it directly from DNS alone. This check tests a handful of common selector names real-world providers default to; a "not found" result means DKIM wasn't found under those common names specifically, not that it's definitely unconfigured under a custom one.

When you'd use this

Before switching email providers, after setting up a new sending domain, or when troubleshooting why legitimate mail is intermittently landing in recipients' spam folders.

Frequently asked questions

It says DKIM is missing but I know it's configured — why?

The DKIM check only tests common selector names (default, google, selector1, etc.). If your provider uses a custom selector, this check won't find it even though DKIM is genuinely configured — check your mail provider's admin panel for the exact selector to verify directly.

What does an SPF 'too many lookups' error mean?

SPF records are capped at 10 DNS lookups during evaluation. If your record includes several third-party senders (each an `include:` that costs a lookup), you can exceed that limit — receiving servers may then treat the whole SPF record as failed, not just skip the excess entries.

My DMARC policy shows p=none — is that a problem?

It's monitoring-only: DMARC is active and collecting reports, but it isn't yet telling receiving servers to quarantine or reject spoofed mail. It's the right starting point, but worth moving to p=quarantine once you've confirmed legitimate mail is passing SPF/DKIM cleanly.