MX Records: a beginner's guide

An MX record ("Mail eXchanger" record) is a special type of DNS entry that tells the rest of the internet which servers handle email for a particular domain. When someone sends an email to `you@example.com`, the sending server doesn't already know where your inbox lives — it has to ask DNS, "who handles email for `example.com`?" The answer comes back as one or more MX records, each pointing at a hostname (like `aspmx.l.google.com` for Google Workspace, or `example-com.mail.protection.outlook.com` for Microsoft 365), each with a numeric priority. The sending server tries the lowest-priority server first; if that fails, it tries the next one; and so on.

You should care because without correct MX records, your domain cannot receive email at all. There is no fallback, no alternate path, no "oh, it'll figure it out." If your MX records are wrong — pointing at a server that no longer exists, or missing entirely — every message sent to your domain will silently bounce, and the senders will get a delivery-failure notice while you sit there wondering why the customer never wrote back. This is one of the highest-stakes pieces of DNS configuration, and one of the easiest to break during a migration.

The five things every MX record check looks at:

• Does at least one MX record exist? A domain with no MX records cannot receive email.

• Do the listed mail servers actually resolve and accept SMTP connections? An MX record pointing at a hostname that returns NXDOMAIN is silently broken.

• Are the priorities correct? The lowest number wins. If your primary server is priority 10 and your backup is priority 20, that's right. If they're the same, they share the load.

• Does the domain use a recognized email provider? Most domains today use Google Workspace, Microsoft 365, Zoho, ProtonMail, or a similar managed provider. The hostnames in the MX records reveal which one.

• Is there a Null MX record? A `0 .` (priority zero, target dot) tells receivers that this domain explicitly does not accept mail — useful for parked domains and brand-protection registrations.

Three questions an MX record check answers:

• Can my domain actually receive email right now?

• Did the recent email-provider migration go correctly, or are some MX records still pointing at the old service?

• Which email provider is this domain (mine or a competitor's) actually using?

The cost of broken MX records is total email loss — the worst possible failure mode for a business. The fix is one DNS edit. The protection is checking your MX records every time you migrate email providers, every time you launch a new domain, and on a recurring schedule for your most important domains. The MX record format is defined in RFC 5321, the same standard that defines SMTP.

In one sentence: Find mail servers and detect email provider

Retrieves MX (Mail Exchange) records for a domain and identifies the email service provider. Returns mail server hostnames, priority values, and provider detection for Google Workspace, Microsoft 365, Proofpoint, Mimecast, Barracuda, Amazon SES, ProtonMail, Zoho, Fastmail, iCloud Mail, and more.

Don't worry if some of the words above are still unfamiliar — there's a plain-language glossary at the bottom of this page, and most of the terms link to their own beginner guides if you want to learn more.

Here's what's actually happening behind the scenes when you call this endpoint:

Queries MX records and analyzes mail server hostnames to identify the email provider and security gateways. Detects Null MX (the official internet standard) configurations — domains that explicitly do not accept email. Returns priority-sorted records with provider confidence scoring.

If you're using an AI assistant through MCP, you don't need to understand any of the technical details — the assistant calls the tool and translates the result for you.

Let's skip the marketing fluff and answer the only question that actually matters: why should you, a real human with a real to-do list, care about the MX Records tool? Here's the plain-English version, written the way you'd hear it from a friend who happens to do this for a living.

MX record (Mail eXchanger record) analysis is critical for email deliverability troubleshooting, email security posture assessment, and identifying infrastructure misconfigurations. Identifies email security gateways (Proofpoint, Mimecast, Barracuda) in the mail path, useful for understanding an organization's email defense stack.

Picture this in real life. Imagine an email administrator. Here's the situation they're walking into: Emails to a specific domain are bouncing. Check if MX records exist and are properly configured. Without the right tool, that person would be stuck copy-pasting between five browser tabs, reading documentation written for engineers, and crossing their fingers that the answer they cobble together is correct. With the MX Records tool, the same person gets a clear answer in seconds — no spreadsheets, no guessing, no waiting for someone on the infrastructure team to free up.

Three questions this tool answers in plain English. If any of these have ever crossed your mind, the MX Records tool is built for you:

• Is my domain pointing to the right place right now?

• Did the DNS change I just made actually take effect everywhere in the world?

• Is anything in my DNS misconfigured in a way that could break email or break the website?

You can either click the tool and get the answer yourself, or ask your AI assistant — connected through MCP (Model Context Protocol) — to ask the question for you and translate the answer into something you can paste into Slack.

Who gets the most out of this. Founders running their own infrastructure, marketers coordinating launches, IT admins inheriting domains from a former employee, and ops engineers troubleshooting live outages. If you see yourself in that list, this is one of the EdgeDNS tools you should bookmark today.

What happens if you skip this entirely. Skip it and you're flying blind on the one piece of config that decides whether your website and email work at all. That's why running this check — even once a month — is one of the cheapest forms of insurance you can give your domain.

If you're still on the fence about whether the MX Records tool belongs in your toolbox, this section is for you. Below you'll meet three real people — an email administrator, a security analyst, and an IT consultant — facing three real situations where this tool turns a stressful afternoon into a five-minute task. Read whichever story sounds closest to your week.

Story 1: Email Deliverability Troubleshooting

Imagine you're an email administrator. Emails to a specific domain are bouncing. Check if MX records exist and are properly configured.

Why it matters: Quickly diagnose email delivery issues by verifying mail server configuration.

Story 2: Email Security Posture Assessment

Imagine you're a security analyst. Map an organization's email security stack by identifying security gateways (Proofpoint, Mimecast, Barracuda), cloud email providers, and backup mail servers from MX records.

Why it matters: Understand email infrastructure defenses without active scanning — identify gaps in the security gateway chain.

Story 3: Migration Planning

Imagine you're an IT consultant. Document current email infrastructure before migrating clients to a new email platform.

Why it matters: Ensure smooth email migrations by understanding existing mail routing.

Common situations across teams. Beyond the three stories above, here are the everyday workplace moments when people across the company reach for the MX Records tool — or one of the tools right next to it in this category. If any of these are on your calendar this month, that's your sign:

• Right before launching a new website or migrating to a new host.

• After making any DNS change, to confirm the new settings are live everywhere.

• When customers report that your site or email "just stopped working" out of nowhere.

• As a recurring monthly health check to catch silent misconfigurations early.

If you can see yourself in even one of those bullets, the MX Records tool will pay for itself the first time you use it.

Still not sure? Here's the easiest test in the world. Open Claude, ChatGPT, Gemini, or any other AI assistant connected to the EdgeDNS MCP server and ask, in your own words: "Is the MX Records tool useful for my job?" The assistant will look at the tool, ask you a couple of follow-up questions about what you're trying to accomplish, and give you a straight answer in plain English. No commitment, no signup forms, no jargon.

If you've connected the EdgeDNS MCP server to Claude, ChatGPT, Gemini, Cursor, or any other AI assistant, you don't need to write any code. Just ask in plain English:

"Use the MX Records tool to check google.com and explain anything that looks wrong in plain language."

The AI will figure out which tool to call, fill in the right parameters, run it, and then explain the result back to you. No copy-pasting between tabs. No reading raw JSON. No memorizing endpoint names.

If you're a developer and want to call the endpoint from a script or your own application, here's the simplest possible example. Replace the placeholder API key with the real one from your dashboard.

There's just one piece of information you need to provide. The table below explains exactly what it is and what a real value looks like.

When you call this tool, you'll get back a JSON object with the fields below. If you're talking to it through an AI assistant, the assistant reads these for you and explains them in plain language — you don't need to memorize them.

These tools pair naturally with MX Records. If you're already running this check, the related ones often answer the next question that comes up:

• MX Health — Check mail server health and redundancy

• SPF Check — Validate SPF record syntax, DNS lookups, and policy

• Email Hosting — Detect email service provider

• TXT Records — Get TXT records including verification entries

If you're using an AI assistant through MCP (Model Context Protocol), you can ask it to run several of these in one go: "Check MX Records and the related tools for example.com and tell me what looks off."

If any words on this page felt like jargon, here's a plain-language version. Click any linked term to read a full beginner-friendly guide.

MX record (Mail eXchanger record) — A DNS entry that tells the internet which servers handle email for your domain.

RFC (Request for Comments) — The official internet standards documents. When someone says 'RFC 8484' they mean a specific numbered standards document — in that case, the one defining DNS over HTTPS.