Free tool · No email address required
Is your email domain set up correctly?
Check the public records behind your business email. Get clear findings for incoming mail, authorised senders and domain protection.
Your results
A record found is not an email delivery guarantee. These are public DNS configuration checks. They cannot confirm that every sender is authorised, that outgoing messages are signed, or that an email reaches an inbox. “Not confirmed” can mean a lookup problem or that more information is needed.
1. Enter your domain
No mailbox access or password is required. The checker reads public DNS records only.
2. Understand the findings
See what was found, what needs review and what could not be confirmed. Expand the DNS details if your provider needs them.
3. Get help if you need it
We can review the findings alongside your sending services and actual email delivery evidence.
Need help making sense of the results?
StormDotCom can review your email configuration, investigate missing messages and plan improvements with you. Mention your domain and the findings when you get in touch.
Request an Email Delivery ReviewWhat this check tells you
What are MX, SPF, DKIM and DMARC?
MX points to incoming mail servers. SPF publishes authorised senders for an envelope domain. DKIM uses a signing key to verify signed parts of a message. DMARC links authentication to the visible From domain and publishes handling preferences. Read our practical email delivery guide.
Why is DKIM not checked automatically?
Every sending service chooses its own selectors. Without the correct selector, a domain-only lookup cannot reliably establish whether DKIM is configured. Even a valid public key does not prove messages are being signed.
Will this change my email settings?
No. This tool reads public records. It does not change DNS, send email or log in to your account. Review all legitimate sending services before changing SPF or enforcing DMARC.
Can I use a subdomain?
Yes. Enter the exact domain you want to inspect. SPF is checked at that name. DMARC discovery uses the DNS tree walk in RFC 9989 and identifies the policy location; older receivers may handle inherited policies differently.
Why can a result differ from another checker?
DNS caches, recent record changes, resolver failures and different DMARC discovery implementations can produce different answers. These checks do not test SMTP connections, blocklists, SPF against a sender IP, report delivery, or a real message’s signatures and alignment.
Technical references: SPF, DKIM, DMARC. Checker released October 2026.
Investigating a particular email?
Read the authentication results and relay timestamps reported in its headers. Processing stays in your browser.