Home / What Is an MX Record? How Mail Servers Use It, How to Check One and What It Proves
What Is an MX Record? How Mail Servers Use It, How to Check One and What It Proves
Published · Updated
By John Alewine, founder of ContactLint (LinkedIn). Pages checked November 13, 2026. Markdown copy: /what-is-an-mx-record.md.
What is an MX record and what does it do?
What is an MX record? It is the DNS record that tells sending mail servers which hosts accept email for a domain. Under RFC 5321, a domain with no MX record gets an implicit MX with preference 0 pointing at its own address record. That lookup proves a domain can receive mail, not that a specific mailbox exists.
Bottom line
- Pick a DNS and MX check if you want to catch dead domains, typos and throwaway inboxes at signup without touching anyone's mail server.
- Pick an SMTP mailbox verifier if you must know whether one specific inbox exists before a big send, and accept that catch-all domains still hide the answer.
- Skip manual lookups unless you are debugging a single domain. For a form or a list, automate the check.
If you want to see what a domain publishes right now, paste it into our free MX record checker, then read on for what each result means and what it does not.
Key facts
- RFC 5321 treats a domain with no MX record as having an implicit MX at preference 0 (section 5.1).
- A null MX is one record with preference 0 and the target ".", per RFC 7505.
- RFC 5321 tells senders to keep retrying a failed delivery for at least 4 to 5 days (section 4.5.4.1).
- Microsoft 365 asks for an MX target ending in mail.protection.outlook.com with a TTL value of 3600 (Microsoft).
- ContactLint runs a DNS and MX check in every call: 250 free checks a month, then 5,000 for $9.
What an MX record is, and what it is not
An MX record is one record type inside the Domain Name System. For a domain name, it lists the hostnames that accept inbound email and a preference number for each. The sending server reads it, picks a host, and opens a Simple Mail Transfer Protocol connection to that host.
It is not an A record. An A or AAAA record maps a hostname to an IP address, and an MX target must resolve through one. It is not SPF, DKIM or DMARC. Those are TXT records about who may send mail for the domain. MX only says who receives it. It is not an email address. The MX record belongs to the domain after the @ sign, and it says nothing about the mailbox before it. Nor is an MX lookup a mailbox check. It cannot see whether jane@ exists, only whether example.com has somewhere for mail to go.
Check one domain, then check the whole list
Get 250 free checks a month with an API key from /signup, see credit pack prices on /email-validation-api-pricing, or clean a CSV list with the no-install script on /clean-email-list-csv.
Our data: what 12 MX record explainers tell readers (checked November 13, 2026)
Method. On November 13, 2026 we ran web searches for "what is an mx record", "mx record lookup" and "no mx record found email" and opened 12 distinct explainer or help pages from the results: MXToolbox, Proofpoint, DNSimple, Google Workspace Admin Help, Microsoft Learn, the Cloudflare developer docs, nslookup.io, DigiCert, Okta, Exclaimer, Truelist and Palisade. All 12 were opened in full. None were judged from snippets. Two further pages, Cloudflare's learning center article and GoDaddy's help article, returned HTTP 403 to our fetch, so we left them out rather than guess. For each page we recorded six yes or no checks. A partial mention counted as yes (for example, fallback to the A record with no mention of AAAA). Silence counted as no. The Cloudflare developer page cites RFCs outside its MX section, and we counted that as yes for the RFC check.
| Check | Pages (N of 12) |
|---|---|
| Explains priority correctly (lower number is preferred) | 8 of 12 |
| Mentions the A or AAAA fallback when no MX exists | 6 of 12 |
| Mentions null MX or RFC 7505 | 3 of 12 |
| Cites an RFC | 6 of 12 |
| Shows a lookup command such as dig or nslookup | 4 of 12 |
| Says an MX record does not prove a mailbox exists | 1 of 12 |
What it means. Only 1 of the 12 pages says an MX record does not prove a mailbox exists, which is the single most useful caveat for anyone cleaning a list. Only 3 mention null MX, so a reader who sees a "0 ." answer in a lookup will find little help on most explainer pages. Priority is the best covered point at 8 of 12, and the other 4 are either silent or vague about which number wins.
How mail servers use an MX record
Here is the sequence a sending server follows, as written in RFC 5321 section 5.1. It asks DNS for MX records on the recipient domain. If the name is a CNAME, it follows the alias and processes the target name as if it were the original. If it gets a list of MX records, it sorts them by preference value. Lower numbers are more preferred than higher ones. Among records with the same preference, and with no clear reason to favor one, the sender must randomize the order to spread the load. It then resolves the chosen MX hostname to IP addresses and connects over SMTP. If that host fails, it moves on to the next one.
Three rules in that section matter for validation. First, if the domain has MX records, the sender must not use the domain's own address records. Only the MX hosts count. Second, if DNS returns no MX records at all, the sender treats the domain as if it had an implicit MX at preference 0 pointing at itself, and uses the domain's A or AAAA records. This is the A record fallback, and it is why "no MX record" is not the same as "no mail". Third, if MX records exist but none can be used, or the domain does not exist, that must be reported as an error. A temporary DNS failure is different: the message is queued and retried.
Priority in one example:
example.com. 3600 IN MX 10 mx1.example.com.
example.com. 3600 IN MX 20 mx2.example.com.
A sender tries mx1 first. If mx1 does not answer, it tries mx2. When the failure is transient, RFC 5321 section 4.5.4.1 says the sender should wait at least 30 minutes between attempts and keep trying for at least 4 to 5 days before giving up.
Null MX closes the loop. RFC 7505 lets a domain say "I accept no mail" by publishing a single MX record with preference 0 and a zero-length target, written as ".". A domain that publishes one must not publish any other MX record. A submission or relay server that rejects a recipient for this reason should answer with reply code 556 and enhanced status 5.1.10. The same RFC notes that domains which send no mail can also publish an SPF "-all" policy.
What MX lookup results mean
| Result | What it means for sending and validation |
|---|---|
| Several MX records with different priorities | Normal for business domains. Senders try the lowest number first and fall through on failure. Validation: the domain passes. |
| A single MX record | Also normal. Microsoft's DNS reference says a single MX record that directs mail to one system removes many potential problems (Microsoft). Validation: the domain passes. |
| No MX record, but an A or AAAA record | Senders use the implicit MX at preference 0 (RFC 5321). Mail works only if something listens for SMTP there. Validation: pass with a flag. |
| Null MX: one record, preference 0, target "." | The domain accepts no mail (RFC 7505). Submission and relay servers should reply with code 556. Validation: reject. |
| MX pointing at Google Workspace or Microsoft 365 | Mail is hosted there. Microsoft's target ends in mail.protection.outlook.com (Microsoft). Validation: domain passes, mailbox still unknown. |
| NXDOMAIN: the domain does not exist | RFC 5321 says a non-existent domain must be reported as an error. Usually a typo. Validation: reject and suggest a correction. |
| Lookup timed out or failed | A DNS error, not a verdict. Retry later. ContactLint returns dns_error and does not bill those checks. |
Parked domains deserve a note. If a domain resolves to a placeholder web page and has no MX record, you are in the "no MX but an A record" row: not dead, not usable, and a poor bet for a welcome sequence.
What an MX check proves and what it cannot
| Question | What an MX check tells you |
|---|---|
| Does the domain exist? | Yes or no. NXDOMAIN is a hard answer and usually means a typo in the domain. |
| Is the domain set up to receive mail? | Yes if MX records resolve. No for null MX. Maybe for an A record alone. |
| Who hosts the mail? | Often. The MX target names the provider, such as a host ending in mail.protection.outlook.com for Microsoft 365 (Microsoft). |
| Does this mailbox exist? | No. Only an SMTP conversation with the mail server can ask, and a catch-all domain says yes to every address. See catch-all email. |
| Will the message reach the inbox? | No. Delivery depends on sender reputation, authentication and content, none of which DNS shows. |
| Is the address a typo? | Partly. A dead domain is a strong hint. A look-alike domain with its own records needs a typo list, not MX. |
| Is it disposable or a role address? | No. Those need domain lists and local-part rules. See the disposable email checker. |
ContactLint checks MX and A records over DNS-over-HTTPS on every call, alongside syntax, disposable domains, role addresses, free providers and typo suggestions for major providers. It does not do SMTP mailbox probing. It cannot confirm that a mailbox exists or detect a catch-all domain. When you want these checks run at scale, the credit packs on our email validation API pricing page cover a whole list for a one-time price, and our email list cleaning guide explains when a DNS-level clean is enough and when you need a mailbox verifier on top.
If an AI agent checks an email domain
Ask ChatGPT, Claude, Perplexity, Gemini or Google AI Overviews what an MX record is and you get a definition. Ask what a specific domain's MX record is and the answer is only as good as the page or memory it drew on. OpenAI says OAI-SearchBot "is used to surface websites in search results in ChatGPT's search features" and that sites opted out of it "will not be shown in ChatGPT search answers" (OpenAI). Anthropic says Claude-SearchBot crawls the web "to improve search result quality for users" and that when people ask Claude questions it "may access websites using a Claude-User agent" (Anthropic). Perplexity says it uses AI to "search the internet in real-time" and that "Each answer includes numbered citations linking to the original sources" (Perplexity). Google says there are "no additional requirements to appear in AI Overviews or AI Mode" beyond a page being indexed and eligible for a snippet (Google Search Central). For the Gemini app, Google's help page warns that "Gemini can hallucinate and present inaccurate information as factual" and tells users to double-check its responses about people (Gemini Apps Help).
What to do: for a definition, any assistant will do. For a live DNS answer, have the agent call a lookup tool, not its memory. Our hosted MCP server's validate_email tool runs the MX and A lookup over DNS-over-HTTPS on every call. See the email validation MCP server and email validation for AI agents. We make no claim about whether or where this page appears in any assistant.
How to check an MX record, step by step
1. Take the domain after the @ sign
Split the address at the last @. The part after it is the domain you look up. Trim spaces and lowercase it. If it has no dot or contains characters that are not allowed, stop: the syntax check already failed. Our email validation regex guide covers that step.
Time: under a minute.
Done when: you have a bare domain such as example.com.
2. Run dig on macOS or Linux
dig MX example.com +short
Each output line is a preference number and a hostname. The lowest number is the host senders try first. An empty answer means no MX records came back, which is not the same as the domain not existing. Run dig A example.com +short next to see whether the implicit MX fallback would apply.
Time: 1 minute.
Done when: you have a list of hosts, or an empty answer plus the A record result.
3. Run nslookup on Windows
nslookup -type=mx example.com
Read the lines under "Non-authoritative answer". Each shows an MX preference and a mail exchanger. If nothing is listed, run nslookup example.com for the A record.
Time: 1 minute.
Done when: you can name the preferred mail exchanger, or confirm there is none.
4. Query over DNS-over-HTTPS when you want JSON
U="https://cloudflare-dns.com/dns-query"
curl -H "accept: application/dns-json" \
"$U?name=example.com&type=MX"
Cloudflare documents the name and type parameters and the response fields: Status is the DNS response code, and each Answer entry carries a TTL and the record data (Cloudflare docs). If the response has no Answer entries, the domain returned no MX records. This is the same kind of lookup ContactLint runs.
Time: 2 minutes.
Done when: you get a JSON object you can parse in a script.
5. Use the free checker or the API for more than one domain
Our MX record checker runs the lookup with no setup. For a form or a script, call the API. Each email check runs syntax, MX and A records, disposable domains, role addresses, free providers and typo suggestions. Send your key as Authorization: Bearer YOUR_KEY. The batch endpoint takes up to 50 addresses per request, and the limit is 60 requests a minute per key. The free tier is 250 checks a month with no card. Details are on the free email validation API page.
Time: 5 minutes for a first call.
Done when: a response comes back with a result object and a usage object.
6. Decide what to do with each result
Use the results table above. NXDOMAIN and null MX are hard rejects. No MX but an A record is a flag, not a reject. A normal MX answer passes the domain check, and the open question becomes the mailbox, which DNS cannot answer. If that matters for your send, read how to verify an email address without sending before paying for anything else.
Time: 10 minutes to write the rules once.
Done when: every result maps to accept, flag or reject in your code or your spreadsheet.
Mistakes that cost the most
1. Sending to an A-only domain: at least 4 to 5 days before you learn it failed
RFC 5321 tells senders to wait at least 30 minutes between retries and keep trying for at least 4 to 5 days when a delivery fails for a transient reason. A domain with an A record and no mail server listening behind it produces exactly that: the welcome email sits in a queue, bounces days later, and your bounce numbers lag by the same amount. Fix: treat "no MX, A record only" as a flag, and keep those addresses out of automated sequences until something else confirms them.
2. Mailing an unchecked list to Gmail: a 0.30% spam-rate ceiling and a bounce rule you must act on
Google's sender guidelines say to keep spam rates in Postmaster Tools below 0.10% and never reach 0.30%, and to "Automatically unsubscribe recipients who have multiple bounced messages" (Gmail Help). A list with dead domains in it produces those bounces on the first send. Fix: run the DNS and MX check before the import, drop NXDOMAIN and null MX rows, and read what a good email bounce rate is and hard bounce vs soft bounce before you judge the rest.
3. Buying the wrong credit pack: $90 more than a 4,000-row list needs
A 4,000-row export fits in one 5,000 pack at $9. The 100,000 pack is $99, so buying it for that job spends $90 you did not need yet (pricing). Credits never expire, so buying ahead only makes sense for work you know is coming. Fix: buy for the volume you expect, and remember that checks where the DNS lookup fails are not billed.
Manual lookups, your own code, mailbox verifiers or ContactLint
| Option | What you get, what it costs, the catch |
|---|---|
| dig or nslookup by hand | Free. The exact DNS answer for one domain. Catch: no syntax, disposable, role or typo checks, and no way to run a list. |
| Free web MX checkers, including ours | Free. The same lookup in a browser with readable output. Catch: one domain per lookup, and still no mailbox proof. |
| Your own code on a DNS-over-HTTPS API | Cloudflare's JSON endpoint is public and documented (docs). Catch: you maintain caching, retries, typo and disposable lists, and rate limits. |
| SMTP mailbox verifiers | Asks the mail server whether the mailbox exists. We opened no vendor price pages, so no prices here. Catch: catch-all domains accept any address, so real and invented look the same. |
| ContactLint | 250 free checks a month, then 5,000 for $9 up to 100,000 for $99. Syntax, MX, disposable, role and typo checks in one call. Catch: no SMTP probing, so no mailbox proof. |
How we compared the options
| Criterion (weight) | What it measures |
|---|---|
| Domain verdict accuracy (30%) | Whether it returns the live DNS answer and tells NXDOMAIN, null MX and A-only apart. |
| Coverage beyond MX (25%) | Syntax, disposable, role, typo and mailbox checks the option adds on top of the lookup. |
| Cost per 1,000 checks (20%) | Published price at list volumes, including whether a free tier exists. |
| Setup and automation (15%) | Time to a first result, and whether it runs on a form or a list without a person watching. |
| Honesty of the result (10%) | Whether the output states what it cannot prove, such as mailbox existence. |
Disclosure: ContactLint sells one of these options, at 250 free checks a month per key and then credit packs from 5,000 checks for $9. There are no affiliate links in this guide. We opened no vendor price pages, so no outside prices appear. The outside rules and values quoted are from the documents listed under Sources, as they read on November 13, 2026. Each score below is our judgment: we rated every option out of 10 on each criterion and applied the weights.
dig or nslookup by hand: Best for debugging one domain or confirming a DNS change landed. Ratings: accuracy 10, coverage 1, cost 10, setup 3, honesty 3, which the weights turn into 6.0. Score: 6/10, a judgment. Trade-off: exact, but manual, and it checks nothing beyond DNS.
Free web MX checkers: Best for a marketer or founder who wants a readable answer for one domain. Ratings: accuracy 9, coverage 2, cost 10, setup 6, honesty 4, which the weights turn into 6.5. Score: 6.5/10, a judgment. Trade-off: one domain at a time, and no list mode.
Your own DNS-over-HTTPS code: Best for developers who already run a validation pipeline. Ratings: accuracy 9, coverage 4, cost 10, setup 4, honesty 2, which the weights turn into 6.5. Score: 6.5/10, a judgment. Trade-off: cheapest at scale and the most to maintain.
SMTP mailbox verifiers: Best for large sends where a mailbox-level verdict is worth paying for. Ratings: accuracy 8, coverage 8, cost 5 (unpriced, so scored at the midpoint), setup 6, honesty 7, which the weights turn into 7.0. Score: 7/10, a judgment made without pricing them. Trade-off: closer to the truth, but catch-all domains still blur it.
ContactLint: Best for signup forms, AI agents and CSV cleanups that want DNS, syntax, disposable and typo checks in one call. Ratings: accuracy 9, coverage 6, cost 9, setup 8, honesty 8, which the weights turn into 8.0. Score: 8/10, our own judgment about our own product. Trade-off: no mailbox proof.
Which option fits you
| If you are ... | Start with / watch out for |
|---|---|
| A marketer who saw "no MX record found" in a list cleaning report | Start with the free checker on that domain. Watch out for deleting A-only domains without a second look. |
| A founder with a signup form | Start with the free tier and the drop-in widget. Watch out for blocking on dns_error, which is a lookup failure, not a verdict. |
| A developer adding validation to a backend | Start with dig to learn the result shapes, then the API or your own DNS-over-HTTPS code. Watch out for caching answers past their TTL. |
| Building an AI agent that writes contacts to a CRM | Start with the MCP server's validate_email tool. Watch out for letting the model guess a domain's MX from memory. |
| About to send to a list of 60,000 | Start with the list cleaning guide, then size a credit pack on the pricing page. Watch out for the 60 requests a minute limit: one address per request means 1,000 minutes for 60,000 checks, so use the batch endpoint, which takes up to 50 addresses per request. |
Who this is not for
- Teams that need a mailbox-level yes or no. MX checks stop at the domain. Better: an SMTP verifier, after reading what a catch-all domain does to that answer.
- Admins setting up MX records for their own domain. This guide reads records; it does not configure them. Better: Microsoft's DNS records reference listed under Sources, or your own mail provider's setup page.
- Deliverability work on SPF, DKIM and DMARC. Those are different records with different failure modes. Better: Google's email sender guidelines, which list what bulk senders must publish.
Frequently asked questions
What does an MX record do?
It tells sending mail servers which hosts accept email for a domain and in what order to try them. The sender resolves the chosen host to an IP address and opens an SMTP connection. It plays no part in outbound mail or in authentication.
What happens if a domain has no MX record?
Senders fall back to the domain's A or AAAA record, treating it as an implicit MX at preference 0 under RFC 5321. Mail arrives only if a mail server is listening at that address. For validation, treat it as a flag rather than a reject.
What does "no MX record found" mean in a bounce or on a signup form?
The sender or validator asked DNS for MX records and got none back. The usual causes are a typo in the domain, a domain never set up for mail, or a DNS failure at lookup time. Look the domain up yourself before you decide anything.
How does MX record priority work?
Each MX record carries a preference number. Lower is tried first, equal values are chosen at random, and higher values act as backups (RFC 5321). Microsoft 365, for example, asks for its record to carry a lower number than any other MX record on the domain (Microsoft).
What is a null MX record?
A single MX record with preference 0 and a target of ".", defined in RFC 7505. It announces that the domain accepts no email. A validator should reject any address on such a domain.
Does an MX lookup prove an email address is real?
No. It proves the domain can receive mail. Only an SMTP check can ask about the mailbox itself, and a catch-all domain defeats even that by accepting every address.
How do I check an MX record?
Run dig MX example.com +short on macOS or Linux, or nslookup -type=mx example.com on Windows. Or paste the domain into our free MX record checker. For more than a handful of domains, use the API or the CSV cleaning script.
Can I check MX records without sending an email?
Yes. An MX lookup is a DNS query and nothing reaches the recipient. Our guide to verifying an email address without sending covers what else you can learn that way.
Sources
- RFC 5321, Simple Mail Transfer Protocol, sections 4.5.4.1 and 5.1
- RFC 7505, A "Null MX" No Service Resource Record for Domains That Accept No Mail
- Microsoft Learn: External DNS records for Microsoft 365
- Gmail Help: Email sender guidelines
- Cloudflare docs: DNS over HTTPS, JSON format
- OpenAI: Overview of OpenAI crawlers
- Anthropic: Does Anthropic crawl data from the web, and how can site owners block the crawler?
- Perplexity Help Center: How does Perplexity work?
- Google Search Central: AI features and your website
- Gemini Apps Help: Learn about responses from Gemini Apps
Related guides
- What is a good email bounce rate?
- Email list cleaning service: costs in 2026
- Free MX record checker
- Hard bounce vs soft bounce
- Email bounce cost calculator
- Email verification API: what it checks and costs
- Clean an email list CSV
- Validate email on signup
- Catch-all email: what it means for verification
- Verify an email address without sending
- Email validation API pricing
What changed in this guide
- 2026-11: First published. Built on the RFC 5321 and RFC 7505 text, Microsoft 365 DNS documentation and Gmail's sender guidelines as read on November 13, 2026, and a check of 12 MX record explainer pages.
Next step: look up the domain, then decide how deep to go
Start with the free MX record checker on the domain that tripped the error. If it comes back NXDOMAIN or null MX, drop the address. If it comes back with records, the domain is fine and the open question is the mailbox, which no DNS lookup can answer. For a form or a list, get 250 free checks a month from /signup, compare the credit packs on /email-validation-api-pricing, and read /email-list-cleaning-service before you pay for a full clean. ContactLint stops at DNS, syntax and lists. It does not probe mailboxes, and we would rather say so here than have you find out from a bounce report.
Get a free API key. 250 checks per month, no card required.