MX
Where inbound email should be routed. An MX record does not prove mail delivery.
KEVRIQO · Domain tools
Inspect MX, SPF, DKIM and DMARC records for a domain in one clear report.
Public DNS lookup. DNS queries run through a single public resolver with timeouts and shared server-side limits. No direct connection to the target website is made.
MX specifies mail-routing servers. SPF publishes sending rules, DKIM publishes selector-specific public keys, and DMARC announces a domain’s preferred treatment of failed authentication.
Where inbound email should be routed. An MX record does not prove mail delivery.
Which senders a domain declares eligible. Includes and nested DNS lookups are not fully evaluated.
Look up a public signing key when you supply the correct selector. No actual message is verified.
Read p=none, quarantine or reject. A published policy alone cannot prove spoofing is impossible.
Use the domain after @ in your email address, such as example.com — not your full email address.
If known, enter the selector configured by your email provider. Other checks do not need it.
Check the published MX targets, SPF text, DKIM key and DMARC policy. Resolve warnings in your mail provider’s DNS setup.
MX (Mail Exchange): lists servers that receive mail for your domain. In a standard MX record, a smaller priority number is preferred. A record such as 10 mail.example.com. tells senders where to route mail; it does not prove successful delivery.
SPF (Sender Policy Framework): is a TXT record beginning with v=spf1. An example is v=spf1 include:_spf.example.net -all. Our checker looks for basic problems like multiple SPF records, but does not recursively resolve every include or evaluate an actual sending IP.
DKIM (DomainKeys Identified Mail): exposes a public key at a name chosen by your mail provider. A DNS key alone cannot tell us whether an individual outbound message was signed correctly. For that, inspect the authentication results of a received message.
DMARC: publishes a policy at _dmarc.example.com. A p=none monitoring policy is not the same as p=reject. Our checker reads the exact domain’s published record; organizational-domain inheritance and per-message alignment are not evaluated.
Compare the record name and value with the setup instructions from your actual mail hosting provider. Change records only in the authoritative DNS control panel for your domain, then allow for DNS caching. A missing DKIM selector may simply be the wrong selector; a warning is not proof that email is being rejected.
For the full address, nameserver and TXT picture, use the DNS Checker. When you need domain registration dates rather than email configuration, use the Domain Registration & DNS Checker.
Enter the domain and choose Check email DNS. MX and TXT-based SPF/DMARC checks run automatically. For DKIM, enter the selector supplied by your mail service, such as selector1; without a selector, the DKIM result is Not checked.
DKIM keys are normally published under selector._domainkey.example.com. A selector is required. If the key is missing, confirm the selector and DNS name with your mail provider. Some providers use a CNAME at the selector name; check its CNAME separately when troubleshooting.
No. SPF publishes sending authorization, but full evaluation includes nested DNS mechanisms and the actual connecting sender IP. The tool does not run an SMTP session, verify a real message, or fully evaluate included SPF policies.
p=none requests monitoring without asking receivers to block failed mail. p=quarantine and p=reject ask receivers to apply stronger handling to failing messages. Actual enforcement depends on message authentication, alignment and receiving mail systems.
The resolver returned no MX record at the entered name. Some mail delivery can fall back to address records, but that is not a recommended substitute for clearly configured MX. A special Null MX (0 .) indicates that a domain does not accept mail.
No. It makes public DNS lookups only. It cannot confirm that a particular message was signed correctly, inbox placement, whether your SMTP server is reachable, or whether recipients accept your mail.
Technical references: SPF (RFC 7208), DKIM (RFC 6376) and DMARC (RFC 7489).
Explore related tools
DNS Propagation Checker is planned separately. Checking a single resolver cannot confirm whether a recent DNS change has propagated across different networks.