Email Domain Checker
Check the public DNS behind your email domain. See MX, SPF and DMARC records, and check a DKIM selector supplied by your email provider.
Free · No sign-up required
Public DNS only. No email is sent. DKIM requires a selector; DNS configuration alone cannot prove delivery, message authentication or inbox placement. Checks may reuse a result from the last five minutes. Free fair-use limits apply.
Check before your next email campaign
Use this tool when setting up a sending domain, adding an email provider or investigating a DNS configuration change. The report shows the records returned by Google Public DNS and separates missing records from lookups that could not finish.
SPF authorizes senders for the envelope-from domain. DKIM publishes a selector-specific signing key. DMARC describes how receiving systems should handle messages that fail aligned authentication. MX handles incoming mail, a separate job.
Use the evidence to choose the next step
Check that your actual sending providers are represented in one SPF record. For DKIM, copy the selector from your provider or the s= value in a message’s DKIM-Signature header. Review DMARC reports and legitimate sender alignment before tightening enforcement.
This is a DNS presence and policy check, not a full protocol validator. It does not execute SPF’s recursive lookup rules, verify a message signature, scan blocklists or test the receiving mailbox. Subdomains may inherit a parent DMARC policy.
Questions about email domain checker
How can I check SPF, DKIM and DMARC for free?
Enter your sending domain. SPF and the direct DMARC policy are checked through public DNS. Add your provider’s DKIM selector to check its published signing key. No account or test email is needed.
Why do I need a DKIM selector?
A domain can use multiple signing keys at different selector._domainkey names. There is no universal DNS query that lists every selector. Get the selector from your email provider or a DKIM-Signature header.
Does an MX record mean outgoing email is authenticated?
No. MX describes where incoming mail is received. SPF, DKIM and DMARC serve different roles in outgoing authentication. Some domains intentionally receive no mail.
Is p=none a broken DMARC policy?
No. It is a monitoring policy. Review reports and confirm alignment for legitimate senders before moving to quarantine or reject. The tool marks it for review rather than calling it invalid.
Does a passing result mean my email will reach the inbox?
No. Delivery also depends on the actual message authentication, sender reputation, recipients and content. A published DKIM key does not prove that the provider signs outgoing messages correctly.
Why does the report say unavailable or not checked?
Unavailable means the DNS lookup did not provide reliable evidence. Not checked means a DKIM selector was not supplied. Neither is silently treated as a failed authentication test.
Sources and methodology
The report distinguishes observed evidence from unknowns. This tool does not change your website, DNS or USPS rental.
Use the result, then verify
Confirm suggested changes with your sending provider. After updating DNS, allow propagation and run the check again. Validate actual messages separately.
Turn a checked domain into an email workflow
Use Omni Email to manage sending-domain setup, permission-based audiences and campaigns. The public checker does not send or change anything.
Explore Omni Email