MX records get set up once and then forgotten, which is fine until you are running forty sending domains and notice your reply rate looks worse than it should. Often it is not worse. The replies are arriving somewhere nobody is looking, or being rejected outright.
What MX records do, briefly
An MX record tells other mail servers where to deliver mail addressed to your domain. Your SPF, DKIM and DMARC records handle outbound authentication; MX handles inbound routing. They are separate jobs and a domain needs both.
A typical record looks like 10 mx.provider.com, where 10 is the priority. Lower numbers are attempted first, and additional records at higher numbers act as failover.
Why this matters more for cold email than normal mail
Three reasons specific to outbound.
Replies are the product. A missing MX record means the positive reply you worked for bounces back to the prospect. They will not try again.
Bounce notifications are diagnostics. Without MX you never receive the delivery failure messages that tell you a mailbox is throttled or a domain is blocklisted. You lose your early warning system.
A domain that cannot receive mail looks disposable. Legitimate senders accept mail. Some receivers factor this in, and it is a free negative signal to avoid.
The five mistakes worth checking for
| Mistake | What happens | Fix |
|---|---|---|
| No MX record at all | Replies bounce, bounces vanish | Publish the provider’s MX on every sending domain |
| MX pointing at an old provider | Mail routes to an account nobody reads | Audit the whole estate after any provider change |
| Duplicate MX at the same priority | Unpredictable routing, intermittent losses | One set of records, priorities distinct |
| Reply-to on an unmonitored mailbox | Replies arrive and sit unread | Route everything into one inbox you actually watch |
| MX on some domains, not others | Reply rate looks fine overall, terrible on a few domains | Audit per domain, not in aggregate |
The last one is the expensive one. Aggregate reply rate hides it completely: thirty-eight domains work, two do not, and the average still looks acceptable while you lose every reply from two domains’ worth of sending.
A two-minute check per domain
- Look up the MX record for the domain and confirm it points at your current mailbox provider.
- Send a test from an outside address, a personal Gmail is fine, to a mailbox on that domain.
- Confirm it arrives in the inbox you actually monitor, not just somewhere on the server.
- Reply to it and check the thread behaves normally.
Do this on every sending domain when you add it, and re-check the estate after any provider change. It is tedious, which is exactly why it gets skipped and why the failures persist.
Where replies should actually go
Getting MX right solves routing. It does not solve the second problem, which is that forty sending domains produce replies in forty places.
Teams handle this three ways. Forwarding rules into a shared mailbox works but loses thread context and makes it hard to tell which campaign produced what. Checking mailboxes individually does not scale past about ten. The workable answer is infrastructure that routes every reply into one inbox with the campaign, sequence and lead attached, which is what the unified inbox does, including LinkedIn replies alongside email.
That also makes an AI Reply Agent practical, because an agent can only handle replies it can see.
The short version
Every sending domain needs an MX record pointing at your mailbox provider, verified with a real test message, re-checked after any provider change, and routing into one inbox somebody reads. It takes two minutes per domain and it protects the only outcome that matters.
Next: managing DNS across 50+ domains, or reading the bounce messages MX makes possible.
Frequently asked questions
Do I need MX records for cold email domains?
Yes. Without MX records the domain cannot receive mail, which means replies, bounce notifications and out-of-office messages all vanish. It also looks suspicious to inbox providers, since a legitimate sending domain normally accepts mail as well.
What MX priority should I use?
Lower numbers are tried first. Use the values your mailbox provider specifies rather than inventing them. A single MX at priority 10 is fine for most sending domains; multiple records with different priorities give you failover.
Can several domains share one mailbox provider?
Yes, and that is the normal setup. Every sending domain points its MX at the same provider, and each has its own mailboxes. What must not be shared is DKIM keys, which should be unique per domain.
Why am I not receiving replies to cold emails?
Missing or wrong MX records is the most common cause, followed by replies going to a mailbox nobody monitors. Send yourself a test from an external address to each sending domain, and check the reply-to address is a mailbox you actually read.
Do MX records affect deliverability?
Indirectly but genuinely. A sending domain with no MX record looks like a throwaway, and some receivers treat that as a negative signal. Correct MX also means bounce messages reach you, which is how you detect problems early.