Free tool
Check MX Record Online
Check MX records online and find the MX record of a domain. This free tool performs a live DNS lookup and shows whether the domain publishes mail exchange or fallback A records — and the records it finds.
No email is sent and nothing is probed on the receiving server — the query answers only. That claim is scoped to this lookup: the wider MultiValidator service keeps verification history for your dashboard and API use, as the privacy policy describes.
Enter a domain
Type the domain you want to check, such as example.com.
Look up DNS records
A live DNS query for the domain's MX records, with A records checked as a fallback.
Read the result
Records found — or none. With neither MX nor A, the pipeline stops with mx_not_found.
The lookup, drawn
One query, two possible outcomes: records found and the pipeline proceeds to the SMTP probe, or no records and the verdict stops with mx_not_found.
What is an MX record?
An MX (Mail Exchange) record is a DNS record that tells sending mail servers which mail servers are responsible for receiving email for a domain. It points email delivery toward the domain’s mail infrastructure, so a sending server knows where to hand a message addressed to that domain.
A domain can publish more than one MX record, each naming a different mail server and carrying a preference value. That is how a domain expresses which server should be tried first and which one takes over if the first is unavailable.
example.com → mail.example.com
the domain points mail delivery at the mail infrastructure it publishes — nothing more is implied by the record
What is an MX record lookup?
An MX record lookup queries the DNS system for the mail-exchange records published by a domain. The result shows whether the domain publishes MX records and, where it does, the mail servers those records name.
This MultiValidator tool performs that lookup live, against the domain’s own DNS, and returns either the records it finds or a no-records answer. It is a domain-level query: you type a domain, not a mailbox, and no part of the answer says anything about an individual address.
How MX record lookup works.
The three steps above, in the order the tool runs them. One DNS query produces one of two answers, and the decision tree drawn earlier is exactly this fork.
- records foundThe domain publishes mail-routing information. The email pipeline can move on to the mailbox-level checks.
- no recordsNo MX and no A record. The DNS stage fails and the pipeline stops with the reason mx_not_found.
Two answers, no third state. A domain that publishes a mail route gets records; a domain that publishes none gets the failed DNS stage and the reason string that goes with it.
What does an MX record lookup check?
Two record types are read, and only two. This page is an MX lookup, not a general DNS inspector.
MX records
The lookup asks DNS whether the domain publishes Mail Exchange records — the hosts a sending server should hand mail to — and returns the ones it finds, with their preference values.
- Whether the domain publishes MX records
- The mail server hostnames, in preference order
- The detected mail host when the MX matches a provider the engine knows
- A live query, answered by the domain's own DNS
A records — the fallback
The same stage also checks for A records. A domain with no explicit MX can still carry a mail route through its address record, so the DNS stage does not treat an absent MX record as an automatic stop on its own.
- Whether the domain resolves to an address
- Used as a mail-routing fallback signal
- Recorded alongside the MX answer
what this lookup does not read
No other record type is queried here. If you need one of these, it is a different tool — this page will not imply that it looked.
- AAAA
- TXT
- SPF
- DKIM
- DMARC
- NS
- CNAME
- SOA
- DNSSEC
MX record example.
Illustrative only — the shape of a DNS answer, not a result this tool returned. The hostnames are the conventional example names.
example.comMX 10 mail.example.comMX 20 backup.example.com
Illustrative records for example.com. Nothing here is a real lookup result.
- MX
- The record type: a mail exchange record, pointing mail at a host.
- 10 / 20
- The priority. The lower value is preferred, so 10 is tried before 20.
- mail.example.com
- The mail server hostname the record points to.
This tool lists the exchange hostnames in preference order rather than printing the priority numbers beside them.
What does MX priority mean?
MX records carry a preference value, and the lower number wins. A sending server generally attempts the lowest-preference host first and falls back to the next record when that one does not answer.
10 mail1.example.com → tried first
20 mail2.example.com → fallback
- Equal priorities are a valid configuration: the sending server may pick either, which is how load is shared across mail hosts.
- Priority orders the attempts. It says nothing about which host is healthier, or whether either will accept a particular message.
- This tool returns the exchange hostnames already sorted by that preference, from lowest priority to highest.
MX record vs. A record.
Two different DNS answers that a mail-routing check can both look at. The MX record is the explicit mail route; the A record is the address the domain resolves to.
MX record
Identifies the mail-exchange hosts for a domain — the servers it nominates to receive its mail, each with a preference value.
A record
Maps a hostname to an IPv4 address. It says where a host lives on the network, not that the host handles mail.
MultiValidator considers both because the two can disagree. A domain with no MX record but a live A record still carries a mail-routing signal, so the DNS stage reads the address record as a fallback rather than stopping. That fallback is not the same claim as an MX record: when a domain publishes mail-exchange hosts, those hosts are the route, and an A record alone does not tell you a server is willing to receive mail.
What does “no MX record” mean?
It means the domain publishes no mail-exchange records. It is a statement about DNS, and it is deliberately not a verdict about the domain.
Because the lookup also checks A records, a domain without an explicit MX record can still resolve to an address and carry a mail route. When neither record is present, the DNS stage fails and the email pipeline records the reason mx_not_found. In MultiValidator that reason means the domain published no MX or A records when it was asked — the resolution stage stopped there.
mx_not_found does not mean
- The domain is fake.
- The domain is malicious.
- The domain does not exist.
- The email is fraudulent.
- The mailbox is invalid.
It means the mail-routing question was answered with “nothing published”. Plenty of domains legitimately receive no mail, and a missing record is not evidence of bad intent.
Do MX records prove email deliverability?
No. Finding MX records indicates that the domain publishes mail-routing information. It does not prove any of the following.
- That a specific mailbox exists at the domain.
- That the mailbox accepts messages.
- That the recipient will receive the message.
- That the address belongs to a real person.
- That the recipient's server will accept a particular message.
Answering those questions needs a mailbox-level check. The email validation pipeline runs DNS and then a live SMTP probe, and even there the verdict describes the checks that ran rather than promising a send.
MX lookup vs. email verification.
One answer each, different sizes. An MX lookup answers a question about a domain; email verification answers a question about an address.
MX lookup — this page
Checks domain-level mail-routing information. It answers:
“Does this domain publish mail-routing records?”
- A live DNS query for MX records
- An A record checked as a fallback signal
- The records found, or none
- No account, no credits, no email sent
email verification — the pipeline
Runs several checks depending on the workflow, over a full address:
- Syntax and formatting
- DNS and MX resolution
- Disposable-domain detection
- A live SMTP mailbox probe
- Role-account detection
- Catch-all detection
- A verdict and a 0–100 score
MX lookup is one part of deeper email verification. This page runs the DNS stage and nothing else — no SMTP probe, no disposable or role detection, no verdict.
Need to verify an email address?
If the goal is to determine more than whether a domain has mail-routing records, use the full email validation workflow. It starts with the same DNS question and continues into the checks that a mail-routing record cannot answer.
use cases
MX record lookup use cases.
One DNS question, asked in the places where a domain's mail routing is the thing you need to know.
Email infrastructure checks
Check whether a domain publishes mail-routing records.
Domain configuration
Inspect DNS mail-routing configuration during setup or troubleshooting.
Email validation
Use MX information as one stage of a broader email verification workflow.
Lead data quality
Check domain-level mail infrastructure before deeper email validation.
Developer testing
Quickly inspect a domain's mail-routing records while building email-related applications.
Troubleshooting
Investigate whether expected mail-routing records are present.
An MX lookup on its own will not diagnose every delivery problem — it cannot see the mailbox, the message or the receiving server’s rules. It removes the domain-level question so the rest of the investigation starts from a known answer. The disposable email detector and the role-based email checker cover two later stages for a single address.
MX record lookup for developers.
Mail routing is a domain-level fact, so it belongs early in an email-related flow: check the domain once, and only spend a mailbox-level check on the addresses that could exist.
the flow
domain → MX / A lookup → structured records → deeper verification when required
- Treat the MX answer as domain-level context: it is the same for every address at that domain, so look it up once.
- Check the A record too — a domain with no explicit MX can still carry a mail route.
- Read the records in preference order instead of assuming a single mail host.
- Send only the domains that publish a mail route through to a mailbox-level probe, and treat a missing record as a domain fact rather than an address verdict.
The tool on this page is backed by an anonymous, rate-limited DNS query — there is no separate public MX-only endpoint to document here. For programmatic work, the DNS stage ships inside the verification pipeline: API documentation.
What an MX record lookup cannot tell you.
None of the following is decided by a mail-routing record, on this page or anywhere else. Each one needs a check that talks to something other than DNS.
- Whether a specific mailbox exists at the domain.
- Whether the recipient is active, or reads what arrives.
- Whether an address belongs to a person.
- Whether an SMTP server will accept a specific recipient.
- Whether a message will reach the inbox.
- Whether a message will avoid spam filtering.
- Whether a domain is trustworthy.
- Whether a domain is malicious.
- Whether an address is disposable.
DNS answers describe the domain’s configuration. Everything above — the mailbox, the recipient, the message and the receiving server’s judgment — is answered somewhere else, which is why the tool stops at the records it found.
MX record lookup FAQ.
What the free lookup answers, what a record does and does not prove, and where verification takes over.
An MX (Mail Exchange) record is a DNS record that tells sending mail servers which servers are responsible for receiving email for a domain. It points mail delivery at the domain's mail infrastructure.
Related free tools
Each tool checks one layer. To run the full pipeline — MX lookup, live SMTP probe and catch-all detection with a reason and a score — use the API.