Is your domain ready to send?
Check MX, SPF, DKIM and DMARC in a few seconds. No signup, no email required. We do not store the domains people check.
No signup. Nothing stored. Checks public DNS only.
What this checks, and why each one matters
| Check | What a failure means |
|---|---|
| MX | No mail server. The domain cannot receive mail at all. |
| SPF | Receivers cannot confirm your servers are allowed to send. Two records, or more than 10 DNS lookups, break it silently. |
| DKIM | No cryptographic proof the message is unaltered and from you. |
| DMARC | No published policy for what to do when a message fails, and no reporting. |
Authentication gets you to the starting line, not the finish. A perfectly configured domain still lands in spam if you send unverified lists at high volume. Records first, then behaviour: see the full SPF, DKIM and DMARC guide and safe sending volume.
- One SPF record per domain, maximum 10 DNS lookups. Both limits fail silently when exceeded.
- DKIM selectors cannot be listed from outside a domain, so any external checker can only probe common names.
- DMARC at p=none publishes a policy of "do nothing". Tighten to quarantine, then reject.
- This tool queries public DNS from the edge and stores nothing.
Frequently asked questions
What does this domain checker test?
MX records, SPF (including whether you have more than one record and whether you exceed the 10 DNS lookup limit), DKIM at common selectors, and DMARC policy. These are the records inbox providers check before deciding where to put your mail.
Why does DKIM show as not found when I have it set up?
DKIM keys live at a selector name chosen by your provider, and there is no way to list them from outside. We probe the common selectors. If yours uses a custom name, check a real message header for DKIM=pass instead.
Do you store the domains people check?
No. The check runs at the edge, queries public DNS, and returns the result. Nothing is stored or logged.