Topic · DNS & Infrastructure
MX record
A Mail Exchanger record identifies receiving mail servers for a domain.
How it works
DNS priority numbers order preferred SMTP delivery targets; lower numbers are preferred.
What can go wrong
An MX record controls inbound routing, not outbound authentication. An incorrect MX target can prevent mail acceptance altogether.
What to check or do
Check all advertised hosts, their address records and SMTP availability.
How to investigate MX record
- Signal to investigate
- Mail is intermittently lost after migrating MX hosts because old records remain reachable.
- Evidence to collect
- Compare authoritative MX answers and preferences with all expected mail exchanger hosts.
- Common wrong conclusion
- An MX record points to mail exchangers; it does not itself authorize outbound email senders.
How to interpret the evidence
MX records specify which mail exchangers accept mail for a domain, with preferences that determine candidate ordering. Every advertised MX may become active during failure or sender-specific routing, including lower-priority backups. A primary host's health check cannot validate the entire inbound path.
What to change and how to verify it
Enumerate all authoritative MX hosts and their A/AAAA records. Check TCP reachability, banner, STARTTLS and policy compliance for each host. For domains that never accept mail, consider whether an explicit null MX is more accurate than leaving mail-routing intent ambiguous.
dig +short MX example.comEducational example; not validated against your live infrastructure.Put this into practice
Run a focused check, then explore protection if your domain needs it.