Mail migration
Compare published exchanges with the new provider’s requirements after a DNS update. Cached responses can take time to expire.
Inspect a domain’s mail-routing records and identify its receiving provider.
MX records name the servers a domain publishes for incoming mail. This lookup helps diagnose a domain setup, compare priorities and distinguish an explicit refusal of mail from an inconclusive DNS lookup.

Use the part after @, for example example.com. Do not enter a full website path.
Read the exchange hostname and preference number. A smaller number has a higher preference.
If the lookup is empty or fails, review DNS and retry before declaring a mailbox invalid.
Illustrative scenarios, not live results for the addresses or records shown. Open a scenario to see the next action.
A sender normally tries the lower preference number first. These are illustrative hostnames, not live lookup results.
Next action Check that both entries match the mail provider’s setup.
The dot is a deliberate declaration that the domain accepts no email. It is not a server hostname.
Next action Ask for another receiving address.
Missing MX is different from null MX; SMTP can use address-record fallback in some setups.
Next action Check the domain’s A/AAAA records and provider instructions.
Compare published exchanges with the new provider’s requirements after a DNS update. Cached responses can take time to expire.
Separate a routing problem from a misspelled local part. An MX lookup cannot tell whether alex@ exists.
No. The records apply to the domain, not an individual inbox.
No. The number is a preference, not a quality score. Lower numbers are preferred.
Cached answers can persist until their TTL expires. A lookup error can also be temporary.
Explore the email provider market share tracker for aggregate MX observations. Technical reference: Null MX specification.