MX Records and Routing Checks Explained
MX warnings do not always mean inbound delivery is broken, but they do tell you your DNS picture may not match your intended mail flow.
Review these basics
- MX records exist for the domain you are testing
- The targets resolve correctly
- Old providers were removed after cutover
- Priority values match the intended routing order
Common migration mistakes
- Leaving legacy MX records in place
- Updating only SPF or DKIM but not the inbound routing records
- Testing the wrong domain after a rebrand or subdomain move
If your sender identity changed recently, compare the actual domain in the message with the domain you updated in DNS. Many “MX problems” are really domain-selection mistakes.