What Is an MX Record?
When someone sends an email to hello@yourcompany.com, they're not sending it directly to your computer. They're telling their email server, "Deliver this to yourcompany.com." But yourcompany.com is just a name—it doesn't have a physical location. So how does the message find its way to your inbox?
That's where MX records come in. MX stands for Mail Exchanger, which is a technical way of saying "the server that receives email for this domain." An MX record is a simple line in your domain's DNS that announces to the world, "Here's where my mail gets delivered." It points to the servers run by your email provider—like Google Workspace or Microsoft 365—that actually accept and store your messages.
Without an MX record, email simply has no place to go. It would be like sending a letter to a building with no mailroom—the postal service would just return it as undeliverable.
Real-World Analogy
Think of your domain name as the street address of a large office building. The MX record is the specific mailroom inside that building. You might have a dozen different storefronts in the building, but all incoming mail goes to one central sorting room that knows where each person sits. If the mailroom closes or moves and the building's address plaque isn't updated, new letters stack up outside.
How MX Routing Works
Layer 1: The Delivery Flow in Plain English
Here's what happens behind the scenes when someone emails you:
1. Their email server notices the destination (you@yourcompany.com) and asks a global directory (the Domain Name System, or DNS) for the MX records of yourcompany.com.
2. The directory responds with one or more server addresses—like or —alongside a priority number. Think of it as a list of backup mailrooms, ranked by how quickly the sender should try them.
3. The sender's server then contacts the server with the lowest priority number first. If that server answers immediately, the message is handed over. If it's busy or down, the sender moves to the next priority, and so on, until one accepts the mail.
4. Once connected, the two servers talk briefly, verify the domain, and the message lands in your inbox. The whole sequence is automatic and nearly instant.
Why MX Records Matter for Your Business
Your MX records are the foundation of your ability to receive email. If they're set correctly, every message from a lead, customer, or partner lands safely. When they're misconfigured, the cost is immediate and invisible—you simply stop hearing from people.
For a small business, a day of missed emails can mean lost sales, delayed support requests, and confusion. A prospect who emails a sales address and gets a bounce-back might assume you've gone out of business. And you'd never know.
It's not just about delivery. Email providers and security filters also check MX records when deciding whether to trust your domain. A missing or misconfigured MX can make your domain look abandoned, which might even affect outbound email deliverability. Think of it as the email equivalent of having a "closed" sign on your front door.
Common Issues and Warning Signs
Most MX problems appear after a migration—like switching from one email provider to another—or when DNS settings are changed without fully removing old records. The symptoms are usually easy to spot:
Common Issues
How to Fix or Improve Your MX Records
Fixing MX records usually takes just a few minutes and requires access to your domain's DNS settings. The goal is to ensure your MX records point exclusively to the servers your current email provider specifies, with the correct priorities.
If someone else manages your DNS (an agency, a hosting provider, an IT consultant), forward this page to them with a note: "Our MX records need to point to [your email provider's servers]. Here's how to check." That's often all it takes.
One thing you can do right now: Run a free TechSpy scan on your domain. In 60 seconds, it'll tell you if your MX records are healthy or if something needs attention—no technical knowledge required.
<!-- self-check: layer1_readable=true | fix_doable=true | no_padding=true | jargon_expanded=true -->