MX
MX receiving route
Identifies receiving mail servers and their priority. A domain without MX usually cannot receive mail reliably.
MX, SPF, DKIM & DMARC Checker
MX, SPF, DKIM & DMARC Checker
Check email DNS configuration and find receiving, sending and authentication issues.
Example: Choose a common selector or type the value supplied by your email provider.
Email DNS check result
No check started
Enter a domain, choose or type a DKIM selector, then click Run check.
Email DNS
What is an email DNS check?
An email DNS check reviews the public receiving and authentication records published for a domain. It does not send email or change DNS; it reads MX and TXT records and evaluates whether the configuration is complete.
MX routes incoming mail, SPF authorizes senders, DKIM publishes the key used to verify signatures, and DMARC tells receivers how to handle messages that fail aligned SPF or DKIM checks.
Four essential record types
SPF
SPF sender authorization
Lists systems allowed to send for the domain, reducing spoofing and delivery failures.
DKIM
DKIM message signing
Publishes the public key used to verify a signature. The checker needs the selector supplied by your mail provider.
DMARC
DMARC enforcement policy
Requires SPF or DKIM alignment and defines reporting, quarantine, or rejection behavior.
Why check email DNS?
A working website does not mean its email configuration is correct. Email DNS problems are often discovered only after a migration, DNS change, or delivery failure.
Improve deliverability
Find missing, duplicate, or malformed authentication records before mail is rejected or sent to spam.
Reduce domain spoofing
Confirm that SPF, DKIM, and DMARC form a complete authentication chain that limits unauthorized sending.
Verify migrations
Check public records after changing business email, delivery platforms, or DNS providers.
How does the checker work?
The check reads only public DNS data and normally completes within a few seconds.
- 01
Normalize the target
Extract a valid domain and validate the DKIM selector format.
- 02
Query DNS in parallel
Request MX, root TXT, selector._domainkey, and _dmarc records together.
- 03
Interpret the configuration
Parse SPF mechanisms, DKIM tags, and DMARC policy while separating missing records from query failures.
- 04
Display the current result
Show the findings and recommendations on the current page without writing a database snapshot or creating a result URL.
How to read the results
A missing record and a failed DNS query are different conditions. The checker does not treat a network error as proof that a record is absent.
Pass
The record was found and the essential fields for this check were recognized.
Review
The record exists but is weak, duplicated, or still uses a monitoring-only policy.
Not found
Authoritative DNS responded normally but did not return the required record.
Query failed
DNS timed out or was temporarily unavailable. Retry later before drawing a configuration conclusion.
Email DNS checker FAQ
What is a DKIM selector and where do I find it?
A selector is part of the DKIM public-key hostname, such as default in default._domainkey.example.com. Your business email or sending provider supplies it. Common examples include default, google, selector1, selector2, and k1.
Why can the checker not discover every DKIM selector automatically?
DKIM selectors have no public directory or fixed list of possible values. Blind enumeration would still be incomplete and would create many meaningless DNS requests, so use the selector configured by your provider.
Can a domain publish multiple SPF records?
It should not. SPF policy for one domain should be combined into a single v=spf1 record. Multiple SPF records can cause PermError and prevent receiving systems from evaluating authorized senders.
Does DMARC p=none mean the configuration is wrong?
No. p=none is a valid monitoring policy that does not quarantine or reject authentication failures. New deployments can collect rua reports first, then move toward quarantine or reject after authorized senders are confirmed.
Why can MX be missing while the website works?
Web traffic uses A, AAAA, or CNAME records, while incoming email primarily uses MX. These configurations are independent, so a working website does not prove that email receiving is configured.
Will this check send email or change my DNS?
No. The tool only reads publicly available DNS records. It does not send mail, sign in to a mailbox, change records, or require domain ownership verification.
How often are results updated?
Every run performs fresh DNS queries. Results remain only in the current page session and no database snapshot is stored. Provider caches and TTL values can delay the global visibility of a recent DNS change.
Related webmaster tools
Continue checking DNS, registration data, reputation, and availability.
DNS lookupCheck A, AAAA, CNAME, MX, and TXT resolution from distributed locations.Whois lookupReview registrar, registration date, and expiration details.Blacklist checkCheck whether a domain or IP appears on common reputation blocklists.Website monitoringContinuously monitor website availability and response time.