MX records direct incoming email to the mail servers responsible for a domain. For cold outreach, the practical question is whether a recipient’s reply reaches the mailbox your team checks. Configure the receiving email service, publish its required DNS records and test the reply route before launching a campaign.
Check yours with the free Rhycon email deliverability checker, which looks up your MX records and flags common problems.
What an MX record is
An MX (mail exchanger) record is a DNS entry that names the server that accepts mail for your domain. Each one has a priority number. Lower numbers are tried first, and higher numbers are backups. For example, Google Workspace now uses a single record pointing to smtp.google.com with priority 1, and older setups use five ASPMX records at priorities 1 to 10. Microsoft 365 uses a hostname like yourdomain-com.mail.protection.outlook.com.
Why MX matters for cold outreach
You need to see replies. If MX is missing or wrong, replies bounce and prospects think you ignored them.
Bounces are visible. A “no such domain or mailbox” bounce is a delivery failure that your sending platform tracks, and a pattern of them hurts reputation.
It establishes the intended receiving route. Do not assume that successful outbound delivery also proves incoming replies work.
Common MX mistakes
No MX record at all. Common on freshly bought domains. Mail may fall back to the domain’s A record, which is rarely what you want.
Old provider records left in place. After moving mail from one provider to another, the old MX records can still receive mail, and you never see it. Remove them.
MX pointing at an IP address. MX records must point to a hostname, not an IP.
MX pointing at a CNAME. The standard says MX targets should not be aliases. Some servers cope, some do not.
Unplanned mixed providers. Mixing Google and Microsoft destinations without a designed routing arrangement can deliver messages to an unintended system. Follow your receiving architecture rather than combining setup instructions.
Wrong priorities. A backup server with the lowest number gets the mail first.
When a domain should have no inbox
Some domains are not meant to receive mail, such as a domain you only use for web traffic. You can publish a “null MX” record, which is 0 . with priority 0 and a single dot as the target. It tells senders clearly that the domain does not accept mail. Do not do this on a domain that sends cold email, because you want replies.
How to set up MX for a new sending domain
Create the mailbox with your provider (Google Workspace or Microsoft 365).
Copy the MX records from the receiving provider into the authoritative DNS zone. For a migration, preserve the current values and plan the cutover before removing obsolete MX destinations.
Wait for DNS to update, then send a test email to the address and confirm it arrives.
Add SPF, DKIM and DMARC. See our guides to SPF, DKIM and DMARC.
Re-run the checker to confirm all four pass.
Doing this for 10, 20 or 50 domains by hand is slow and easy to get wrong. If you would rather not, see Rhycon’s managed infrastructure, which uses Rhycon-owned domains and mailboxes for your outreach.
How to read an MX lookup result
An MX lookup tool should show the domain, priority numbers and destination hostnames. For example, an illustrative result might contain “10 mx1.example.net.” and “20 mx2.example.net.” The lower number identifies the preferred route. It does not describe a percentage of email traffic or the strength of an authentication result.
Multiple MX records can provide alternate destinations when a preferred server cannot accept mail. If two destinations have equal preference, SMTP clients can distribute attempts between them. This is a routing arrangement, not proof of synchronized inboxes. Each destination still needs to accept mail for the domain and deliver it into the intended email service.
MX records point to hostnames, rather than literal IP addresses. The receiving route then resolves those hostnames to address records. Under the DNS rules, an MX target must not point to a CNAME record. Do not replace a provider’s required MX hostname with a guessed address or your website’s hostname.
MX records work as part of the Simple Mail Transfer Protocol delivery process. They identify where a sender should try to deliver a message. They do not create mailboxes, grant users access or configure a forwarding rule. Check the account and the route together when someone reports that incoming mail is missing.
Check the DNS zone that is actually authoritative
Your domain registrar and your active DNS host may be different companies. A DNS MX record entered at the registrar has no effect if another service hosts the authoritative zone.
Check the domain’s nameservers before editing. Then use a public lookup to confirm that the new mail exchanger records appear outside the account where you entered them.
For a terminal check, an administrator can use “dig MX example.com +short”, replacing the example with the relevant receiving domain. A browser-based DNS lookup tool is also suitable. Compare the answer with the receiving provider’s exact values. Query the mailbox domain, which may be a subdomain, rather than automatically using www or the website hostname.
If different DNS servers return different results, compare the authoritative answer with cached resolver answers. Record when the change was made and the earlier TTL. Repeatedly deleting and recreating the same record makes the timeline harder to follow. First establish which answer is current and which system is still serving a cached value.
Plan a provider migration without losing replies
Before changing email routing, create and verify the destination mailboxes. Export the existing MX records and document any forwarding or split-delivery arrangement. Decide which system will receive messages during the transition and who will check it. An old inbox can still contain replies even after you have moved the main delivery route.
Update only the records required for the planned migration. Keep the website’s DNS records and unrelated authentication records intact unless the provider’s instructions require a change.
After publishing the new MX destinations, confirm public DNS and send a test from an external account. Then reply in both directions using the real addresses your campaign will use.
A backup MX record is not a substitute for this transition plan. If the old provider remains as a backup but no longer accepts your domain, an attempted fallback can fail. If it still accepts mail, messages might reach an inbox your team has stopped checking. Keep only destinations that belong in your receiving architecture.
Diagnose the complete reply route
Valid MX records are one part of a successful reply. Check whether the mailbox exists, whether the provider recognizes the domain and whether any forwarding rule points elsewhere.
Also check the Reply-To address in the original campaign message. A reply sent to a different domain follows that domain’s MX records, even when the visible From domain is configured correctly.
Keep the full delivery error when a test fails. A missing user, an unavailable receiving server and a domain with no receiving service need different fixes. If mail reaches the provider but not the inbox, investigate the account, quarantine and routing rules. Changing MX blindly may move email servers without resolving the actual problem.
Provider reference: Google Workspace MX setup includes the current smtp.google.com value and notes that working legacy ASPMX configurations do not need changing.
Standards references: SMTP delivery and MX preference in RFC 5321 explain routing and alternate destinations.
For alias restrictions, read RFC 2181; for domains that intentionally accept no mail, read the null MX specification in RFC 7505.
MX record FAQs
Can I have more than one MX record?
Yes. Multiple records give you backups. The lowest priority number is tried first.
Do I need MX records to send email?
MX is for receiving email, not authorizing an outbound server. Your outreach workflow still needs a working route for replies and delivery notices. Configure and test the appropriate receiving domain instead of assuming outbound success proves it can receive mail.
How long do MX changes take?
Timing depends on cached DNS answers and the previous TTL. Google advises that its new MX values can take up to 72 hours to be recognized. Lowering a TTL does not instantly remove answers that are already cached.
What is a null MX record?
A record with priority 0 and a dot as the target. It says a domain does not accept email.
See how Rhycon works and complete the homepage onboarding to explore how research, outreach and replies fit your workflow.
