Email DNS Health
Check MX, SPF, DMARC, and an optional DKIM selector.
Read the guideRun the tool
JVR Software’s server processes the public target you enter. The diagnostic is rate-limited. Use a system you own or are authorised to check.
More information
Back to the toolWhat it is and when to use it
Email DNS Health puts the public MX, SPF, DMARC and optional DKIM records in one report. Use it when setting up a domain for email, diagnosing a domain alignment issue, or checking whether the advertised records match the instructions from your mail provider.
How it works
MX tells sending systems where to deliver incoming mail. SPF describes sources allowed to send for the envelope domain. DKIM provides a public key for a message signature under a specific selector. DMARC publishes a policy and uses alignment between the visible From domain and authenticated SPF or DKIM identities.
How to use it
- Enter your mail domain.
- If you know a DKIM selector from your mail provider or the s= tag of a test message, enter that selector alone.
- Run the tool and compare every returned record with the provider's settings for that domain.
Worked example
If a test message shows d=example.com and s=mail2026 in DKIM-Signature, enter example.com with selector mail2026. If your provider rotates selectors, the key for a previous message may be under a different name.
Reading the result
An empty section indicates no answer for that particular query. If you omitted the selector, DKIM is simply unchecked. Compare SPF, DKIM and DMARC with the actual domain used by the messages. A company's website domain and the domain shown by a bulk mail service can differ.
Check a genuine message sent through the system you are configuring as a separate step. Its authentication results can show which domain passed SPF, whether a DKIM signature verified and which identifiers aligned with the address shown to the recipient. Published records alone cannot prove that a particular message used them.
Common mistakes and limits
The tool does not send a test email, check mailbox credentials, validate a received signature, expand every SPF include, or certify delivery. Read the Authentication-Results header of an authorised test message to confirm which checks passed in practice. Never paste a DKIM private key into a lookup.
