Check the most important email DNS records (MX, SPF, DMARC, DKIM) for a domain in one place.
Email DNS configuration is a common source of delivery problems. This use case combines MX, SPF, DMARC, and DKIM checks so you can verify all critical records in one place. A valid MX ensures mail delivery, SPF defines sending policy, DMARC enforces alignment, and DKIM provides cryptographic signatures. Checking them together reduces the chance of a partially configured setup.
A typical failure pattern is that MX is correct but SPF is missing or too permissive, or DMARC is published at the wrong hostname. DKIM failures often come from using the wrong selector or publishing the key at the wrong subdomain. Use this checklist approach to validate the entire email stack before sending large campaigns or onboarding a new provider.
If you need related checks, try MX record validator and Check TXT record online.
Start with MX to ensure delivery, then SPF to authorize senders, then DKIM for signing, and finally DMARC for enforcement and reporting.
SPF can fail if you have multiple SPF records or too many DNS lookups from include mechanisms. Keep it to a single record and under lookup limits.
DMARC must be published as a TXT record at _dmarc.yourdomain. Publishing it at the apex will not work.
It is a label that identifies which DKIM key to use. The DNS record is published at selector._domainkey.domain.
DMARC alignment requires that the visible From domain aligns with SPF or DKIM domains. Check your mail provider settings and DNS records together.
DNS changes follow TTLs, so allow for caching. During setup, use lower TTLs to speed up validation.