Table of Contents
An MX record is a DNS entry that tells the internet which mail server handles email for a domain. Email verifiers read it first: no valid entry means the domain cannot receive mail, so any address there is invalid. This guide explains what this DNS record does, how it routes email, and the role it plays when a verifier checks whether an address is real.
Verify an email free — MX check included.
Verify an Email Free →Free plan included · No credit card · MX and SMTP checked
What Is an MX Record?
An MX record, or mail exchange record, is a DNS entry that names the mail server responsible for receiving email on behalf of a domain. When a message is sent, the sending server looks up this entry to learn where to deliver it. Without a valid mail exchange record, a domain has no route for inbound mail and cannot accept email at all.
- DNS entry: An MX record lives in a domain’s DNS zone alongside its other records, published so any sending server worldwide can query it. That public lookup is how mail finds its destination without the sender knowing the recipient’s server in advance.
- Names the mail server: The entry points to the hostname of the server that accepts mail for the domain, not to an IP address directly. That hostname then resolves to the machine receiving messages, separating mail routing from where a website is hosted.
- Priority values: Each mail exchange record carries a preference number, and a lower value means higher priority. Sending servers try the lowest-numbered server first, falling back to higher numbers, which lets a domain list backup mail servers for redundancy.
- Separate from web hosting: This DNS record routes mail independently of where a website lives, so a domain can change mail providers without touching its site. That separation is why email and web addresses on the same domain can point to entirely different machines.
- Required for inbound mail: A domain needs at least one valid mail server pointer before any sender can deliver to it, making the record the minimum condition for receiving email. Remove it and the domain goes dark for inbound messages everywhere at once.
This DNS entry is the signpost that tells the internet where a domain’s email should be delivered, and its presence is the baseline condition for receiving any mail.
How Does an MX Record Work?
When an email is sent, the sending server queries DNS for the recipient domain’s MX record, reads back the mail server hostname and its priority value, then connects to the highest-priority server to deliver the message. Multiple entries provide backups if the first is unreachable. This lookup happens before any message content is transferred.
- DNS query: The sending server asks DNS for the recipient domain’s MX records, the same way a browser asks for a website address. This query returns the list of mail servers authorised to receive email for that domain.
- Return server and priority: DNS responds with one or more mail server hostnames, each tagged with a preference number. The sending server sorts them, treating the lowest number as the preferred destination and the rest as fallbacks for redundancy.
- Connect to deliver: The sending server opens a connection to the highest-priority mail server and begins the SMTP exchange. If that server refuses or fails to answer, delivery retries the next server on the list in priority order.
- Fall back if needed: When the preferred server is unreachable, the sender moves down the priority list to the next mail server, which is why domains publish multiple MX records. This fallback keeps mail flowing during maintenance or an outage on the main server.
- Cache the result: Resolvers cache the lookup response for the record’s time to live, so repeated sends to the same domain skip a fresh lookup. This caching speeds bulk delivery and reduces load on the DNS that publishes the record.
Every delivery starts with a mail exchange lookup. It routes mail to the right server, in priority order, before any content is ever sent.
How an MX Lookup Routes Mail
Why Do MX Records Matter for Email Verification?
MX records are the first deliverability gate a verifier checks. If a domain has no valid mail exchange entry, it cannot receive mail at all, so every address on it is invalid by definition. Confirming a working entry is the prerequisite for any deeper mailbox check, because there is no point probing a server that does not exist.
- First gate: The MX lookup runs before the mailbox check, screening out domains that cannot receive mail in a single fast step. This early filter saves the verifier from wasting an SMTP connection on a domain with no mail server at all.
- No MX means no mail: A domain without a valid mail server entry has no inbound mail route, so every address there is undeliverable. The verifier can mark those addresses invalid instantly, with no need to query a non-existent server.
A working MX record is the precondition for deliverability, which is why verifiers check it before anything else in the process.
How Do Verifiers Use the MX Record?
A verifier performs an MX lookup on the domain, confirms a mail server exists, then connects to that server for the SMTP check. The result does two jobs at once: it filters out dead domains instantly, and it tells the verifier exactly which server to send its existence probe to during the deeper mailbox check.
- Filter dead domains: Domains returning no valid entry fail immediately, removing parked sites and typo domains from the list before any mailbox probe. This screening keeps obvious dead ends out of the slower, connection-based stage of verification.
- Locate the mail server: The lookup hands the verifier the exact hostname to connect to for the SMTP check. Without that pointer, the existence probe would have nowhere to go, so the lookup is what makes the deeper check possible.
The verifier checks the domain’s mail server before confirming whether a specific mailbox exists.
— Hunter, Email Verifier API documentation
The MX lookup does double duty: it screens dead domains and points the SMTP check at the right server in one early step.
What Happens When a Domain Has No MX Record?
No MX record means the domain is not set up to receive email, so verifiers mark every address there invalid immediately. This commonly happens with parked domains, typo domains, and websites that were never configured for mail. A missing MX record is one of the fastest and most certain invalid signals a verifier can detect.
- Parked domains: A registered but unused domain often has a website placeholder and no mail configuration, leaving it with no mail routing configured. Addresses invented on such a domain are undeliverable, and the verifier flags them invalid the moment the lookup returns empty.
- Typo domains: A misspelled domain in a list rarely has working mail set up, so the lookup comes back empty. Catching these typos at this stage removes guaranteed bounces before they ever reach the sending stage of a campaign.
- Website-only domains: Some domains serve a site but were never configured to receive email, leaving an A record present but no mail server entry. The verifier treats every address on such a domain as invalid, since no mail server stands behind it.
- Decommissioned domains: A domain whose mail service has been shut down loses its mail exchange entry, so addresses that once worked now fail the lookup. Re-verifying an aging list catches these expired domains before they damage a sender’s bounce rate.
- Instant invalid signal: An empty lookup response lets the verifier reject the address without opening any connection, making it the cheapest invalid result to detect. That speed is why this gate runs before the slower mailbox probe.
A domain with no MX record cannot accept mail and is treated as undeliverable.
— IETF, RFC 5321 Simple Mail Transfer Protocol
A missing MX record is an instant invalid. The domain simply cannot accept mail, so no address on it can ever be reached.
MX Record vs A Record: What’s the Difference?
An A record maps a domain to a website’s IPv4 address; an MX record maps it to a mail server. A domain can have one without the other, which is why a live website does not guarantee a working email domain. For deliverability, verifiers care about the mail exchange entry, not the A record that serves the site.
Source: DNS record definitions per IETF RFC 5321 (mail routing) and standard DNS resource-record types, verified 2026-06-28. An A record maps a hostname to an IPv4 address; AAAA maps to IPv6; only the MX record governs where email is delivered.
A live website backed by an A record does not mean working email. Only a valid mail exchange entry proves that mail can actually arrive at the domain.
How Does Hunter Use MX Records?
Hunter checks the MX record as an early layer of its verification, filtering out domains that cannot receive mail before running the SMTP existence check. The lookup result feeds into the overall status and confidence score, screening obvious dead domains up front so the slower mailbox probe only runs where a mail server actually exists.
- Early filter: Hunter resolves the mail exchange entry first and discards domains that return none, sparing an unnecessary SMTP connection. This ordering keeps verification fast by removing unreachable domains before the more expensive existence check begins.
- Feeds the score: That result is one of several signals. folded into Hunter’s status and confidence percentage. A clean entry supports a deliverable verdict, while a missing one drives an invalid result on its own.
An MX lookup is the first gate; clearing it is what keeps bounce rates low before a send.
— Growth Hack Suite, pre-send verification workflow
In Hunter, this early check removes unreachable domains before the deeper SMTP test runs. that removes unreachable domains before the deeper SMTP test runs.
What Are the Limits of MX-Based Checks?
A valid MX record proves the domain can receive mail, but not that a specific mailbox exists on it. Spammers and catch-all domains have valid entries too, so a passing MX check alone never confirms an address. This check is necessary but not sufficient; an SMTP check must follow to confirm the individual mailbox.
- Domain-level only: The MX record answers a question about the whole domain, never about one address. A working mail server can host thousands of valid and invalid mailboxes, so the MX result cannot judge any single recipient by itself.
- Not mailbox proof: A valid MX record is easy for any domain owner to publish, including spammers and disposable-mail providers. Because the record only shows a server is willing to receive mail, the deeper SMTP check remains essential to confirm a real mailbox.
- Catch-all blindness: A domain with a valid mail server entry may accept every recipient regardless of whether the mailbox exists regardless of whether the mailbox exists, so the MX result cannot flag a catch-all on its own. Resolving that ambiguity requires the SMTP check and additional risk signals layered on top.
- No reputation insight: The lookup reveals nothing about whether a domain is a spam trap, a disposable provider or a trusted sender. Those quality judgements depend on signals beyond DNS, which is why verification combines the MX gate with deeper checks.
- Necessary, not sufficient: Passing this check is a precondition for a deliverable verdict, never the verdict itself for a deliverable verdict, never the verdict itself. The result tells the verifier to continue rather than to stop, so an SMTP probe always follows a clean MX lookup.
A valid MX record confirms the domain, never the mailbox. It is a gate that mail can pass through, not the final answer about an address.
How Do You Check a Domain’s MX Record?
You can check a domain’s mail exchange entries with a DNS lookup tool or a command-line query, but for email purposes a verifier does it automatically as part of each check. Enter or upload addresses and the verifier handles the MX lookup plus the deeper mailbox verification in one step, so you rarely need to inspect the record by hand.
- DNS lookup tool: A web-based DNS checker or a terminal command returns a domain’s mail server entries on demand, showing each mail server and priority. This route suits an engineer inspecting one domain, but it stops at the record and never tests a mailbox.
- Or use a verifier: An email verifier runs the MX lookup silently inside every address check inside every address check, then continues to the SMTP existence test. This path turns a technical DNS query into a single click and bundles it with the deliverability answer that matters.
Verify an email free — the MX lookup runs automatically.
Verify an Email Free →Free plan · No credit card · MX plus mailbox check
A verifier runs the lookup for you, bundled with the full existence check, bundled with the full existence check, so you read back one clear status instead of raw DNS output.
What Tools Check MX Records for Verification?
Every email verifier performs an MX lookup as a built-in step, while standalone DNS tools show the mail exchange entry but do not verify mailboxes. Hunter includes MX checking within full verification on a recurring free tier. The table below compares the common options on the points that decide which tool fits a given job.
Source: hunter.io/pricing, verified 2026-06-28 (free plan 50 credits/mo = ~100 verifications at 0.5 credit each). Other rows describe common tool categories; confirm each provider’s current features before buying.
DNS tools show the mail exchange entry and stop there. A verifier uses that same lookup as step one of confirming the mailbox actually exists.
Verdict: Why MX Records Matter in Verification
The MX record is the first checkpoint in email verification: no valid entry, no mail, instant invalid, instant invalid. It cannot confirm a specific mailbox by itself, but as the gate that screens unreachable domains before the SMTP check, it makes verification both faster and more accurate. Understanding it explains why a verifier rejects some addresses before any probe.
Verdict: The MX record is verification’s first gate. No valid mail exchange entry means the domain cannot receive mail, so every address is invalid instantly. A passing MX check confirms the domain only, never the mailbox, so the SMTP check always follows to confirm the address.
An MX record specifies the mail server responsible for accepting email for a domain.
— Wikipedia, MX record
Verify an email free with a full MX and SMTP check.
Verify an Email Free →Free plan · No credit card · Real mailbox status returned
Related Tools in the Hunter Stack
The MX check is one verification layer, not the whole picture. The Hunter Email Verifier guide covers the full validation process and every check it runs, including the MX lookup, while the finder review covers building the lists worth verifying in the same connected stack on one credit pool.
- Hunter Email Verifier: The validation layer that wraps the MX lookup in syntax, SMTP and risk signals — start with what the Hunter Email Verifier is.
- Hunter Email Finder: The list-building half of the bundle that shares the same credit pool — read the Hunter.io email finder review for sourcing costs.
MX Record: Frequently Asked Questions
The 12 most-asked questions about MX records.
What is an MX record?
An MX record, or mail exchange record, is a DNS entry that names the mail server responsible for receiving email for a domain. When a message is sent, the sending server looks up this entry to find where to deliver it. Without a valid mail exchange entry, a domain cannot accept inbound mail.
How does an MX record work?
When email is sent, the sending server queries DNS for the recipient domain’s MX record, reads back the mail server hostname and its priority value, then connects to the highest-priority server. Lower priority numbers are preferred, and extra entries act as backups if the first server is unreachable.
Why do MX records matter for email verification?
MX records are the first deliverability gate a verifier checks. If a domain has no valid entry, it cannot receive mail at all, so every address on it is invalid by definition. Confirming a working mail exchange entry is the prerequisite for any deeper mailbox check the verifier runs.
How do verifiers use the MX record?
A verifier performs an MX lookup, confirms a mail server exists, then connects to that server for the SMTP existence check. The result filters out dead domains instantly and tells the verifier exactly which server to probe, so the lookup both screens and routes the deeper check.
What if a domain has no MX record?
No MX record means the domain is not configured to receive email, so verifiers mark every address there invalid immediately. This is common with parked domains, typo domains and websites never set up for mail. A missing mail exchange entry is one of the fastest and most certain invalid signals.
MX record vs A record?
An A record maps a domain to a website’s IPv4 address, while an MX record maps it to a mail server. A domain can have one without the other, so a live website does not guarantee working email. Verifiers care about the mail exchange entry, because only it governs where mail is delivered.
Does a website guarantee working email?
No. A working website relies on an A or AAAA record, which is separate from the mail exchange entry that handles inbound mail. A domain can serve a site perfectly yet have no mail routing configured and accept no email at all. Only an MX lookup confirms that mail can actually be delivered.
What are the limits of MX checks?
A valid MX record proves the domain can receive mail, but not that a specific mailbox exists. Spammers and catch-all domains publish valid entries too. So this check is necessary but not sufficient, and an SMTP probe must follow to confirm the individual address is real.
How do I check a domain’s MX record?
You can use a web-based DNS lookup tool or a terminal command such as dig or nslookup to read a domain’s mail exchange entries. For email purposes, a verifier runs the MX lookup automatically inside every check, then continues to the mailbox test, so most people never query the entry by hand.
What tools check MX records?
Every email verifier performs an MX lookup as a built-in step, including Hunter and pure-play verifiers, while standalone DNS tools show the mail exchange entry without testing a mailbox. Hunter pairs this check with full verification on a recurring free tier of about 100 verifications a month.
Can a spam domain have a valid MX record?
Yes. Publishing an MX record is trivial for any domain owner, including spammers and disposable-mail services, because the entry only declares a server willing to receive mail. A valid mail exchange entry therefore proves the domain can accept email, not that the sender or its mailboxes are trustworthy.
Is an MX check enough to verify an email?
No. An MX check confirms the domain can receive mail, but it cannot tell whether a specific mailbox exists. Full verification follows this lookup with an SMTP existence check that probes the individual address. The MX step is the gate, and the SMTP step is the proof of the mailbox.
