What MX does
MX records list the mail servers that accept email for your domain, in priority order.
MX records decide which servers receive email for your domain. Make sure they point where you expect.
Free for AwareX client employees and anyone who needs a quick check. No sign-up required.
How to check, verify, and actDNS queried via Cloudflare. We don’t store your input.
See which servers receive email for a domain. This reviews mail routing, not whether a message or sender is trustworthy.
Enter the domain you want to review, such as example.com, without a page path.
Select Check records. The tool requests the public DNS records through Cloudflare.
Review the MX entries with your DNS or email administrator before making changes.
Enter the domain after the @ in your work address.
Ask IT to compare the returned server names and priorities with your organization's approved email provider.
Check the result again after any recent mail change before treating it as a problem.
If routing looks unfamiliar or mail is failing, send the domain and records to IT. Do not edit mail routing yourself.
A returned record is not a security verdict. Missing records can reflect configuration, propagation, or a lookup issue.
MX records identify incoming mail servers and their preferences. Compare them with your provider's setup instructions; this lookup does not test delivery, mailbox availability, or email authentication.
MX records list the mail servers that accept email for your domain, in priority order.
Lower preference numbers are tried first. Compare unfamiliar hosts with your provider's published settings before treating them as a problem.
Changed email providers? Confirm old MX entries are gone so mail flows only to the new service.
These SMTP specification facts explain how published mail routes are used. They are routing rules, not security statistics or a test of whether your mail service works.
MX preference values are ranked from lower to higher. A value of 0 is preferred over 10; preference is not a trust score.
IETF · RFC 5321, section 5.1An MX target must resolve to at least one address record for its mail server. Publishing an MX entry does not check that server's availability.
IETF · RFC 5321, section 5.1SMTP defines an implicit mail route to the host when no MX records exist. A missing MX result alone does not prove that delivery is impossible.
IETF · RFC 5321, section 5.1MX records describe mail routing, not phishing protection. A correctly routed inbox can still receive a convincing lure. AwareX is a separate training platform for the decisions employees make after a message arrives.
Confirm the listed hosts and preferences with your mail provider. MX records do not authenticate senders or determine whether a message is safe.
Lookalike addresses, compromised accounts, SMS, calls, and deepfakes can reach employees regardless of the records returned by this check.
Separately, AwareX provides contextual simulations and learning that help teams pause, verify, and report. This lookup does not run or validate those activities.
AwareX is AI-powered human risk testing: it learns your business, runs realistic simulations across email, SMS, voice, QR codes, and deepfakes, and adapts learning to how your people respond.
See AwareX in Action - Book a demoThis free tool shows one signal. AwareX is a New Age Human Risk Management platform: five AI agents work together to test your people the way attackers would, and to turn every response into learning.
Learns your business from public context: departments, products, and tone, so every test is grounded in how your organization actually works.
Drafts and scores attack scenarios against your scope, the way a real attacker would plan them.
Writes on-brand emails, messages, and calls with realistic signatures and sender identities, ready for your review.
Compares predicted risk with how people actually respond, so the picture gets sharper after every wave.
Decides who needs practice next and routes learning to the people and teams that need it most.
A MX Record Checker result is one piece of the picture. Explore how AwareX connects realistic simulations, learning, and reporting for your organization.

MX records decide which servers receive email for your domain. Make sure they point where you expect. This tool queries public DNS through Cloudflare and displays the MX records returned for your domain. Use the results to review your configuration; finding a record does not by itself confirm that your domain is secure.
Where we test
Identify, Measure, Prioritize, Reduce, Optimize, Validate, and Evaluate. AI connects business context, employee responses, and targeted learning to inform each next test.

A free check tells you where you stand today. A partnership with AwareX turns that snapshot into a continuous, AI-powered program.
Simulations are written from your sector, your roles, and current events, so every test feels real to the person receiving it.
Every response informs the next test and the lesson that follows it, so training adapts as your risk changes.
Dashboards, records, and compliance alignment give leadership and auditors a clear picture of progress.
Setup, campaign planning, and ongoing optimization from a team that runs these programs every day.
Free access, safe follow-up, and answers specific to this checker.
Yes. Every AwareX free tool is free to use, and you can run as many checks as you need.
No. There is no account, no sign-up, and nothing to install. Open the page, run the check, and read the result.
Share the result with your DNS or email administrator, close any gaps they identify against your provider’s recommended setup, and re-run the check to confirm the change.
MX records identify the mail servers responsible for receiving email for a domain. They describe incoming delivery, not the servers authorized to send email.
It is the preference value. Senders generally try lower numbers first. Higher numbers often identify backup servers; equal values allow delivery attempts across multiple servers.
No. This is a domain-level DNS lookup. It does not connect to the mail server or confirm that an individual email address can receive messages.
Cached DNS records may remain until their time-to-live expires. If old entries persist, check the authoritative DNS settings and compare them with the records required by your current provider.