Next-Gen App & Browser Testing Cloud
Trusted by 2 Mn+ QAs & Devs to accelerate their release cycles

Instantly check any domain's MX (mail exchange) records, priorities, and mail server details. A fast, browser-based MX record checker for DNS and email diagnostics.
An MX Lookup (or MX record check) queries a domain's DNS for its MX (Mail Exchange) records, the servers responsible for receiving email for that domain. Each MX record has a priority value that tells sending mail servers which server to try first. This tool resolves those records in real time, right in your browser, and also resolves each mail server's IP address along with its ASN and organization.
Note: Enter a valid domain without prefixes like "https://" or a trailing "/". The tool normalizes common formats automatically.
Every MX record carries a priority value, and that number decides the order in which sending servers try your mail hosts. Here is how the priority field behaves in practice.
An MX record check is a core step in email and DNS troubleshooting, and it pairs naturally with the other free network tools from TestMu AI such as the domain to IP lookup, hostname to IP resolver, reverse IP lookup, and IP to hostname tools. Use an MX lookup to:
An MX (Mail Exchange) record is a DNS record that specifies the mail servers responsible for accepting email for a domain, along with a priority value that controls the order in which they are tried.
The priority (or preference) controls the order mail servers are tried. A lower number is preferred, so sending servers attempt the lowest-priority record first and fall back to higher numbers if it is unavailable.
Large mail providers use anycast and geo-based DNS, so a mail server hostname resolves to different IP addresses depending on where and when the query runs. The hostnames and priorities are stable, but the IP and its country can vary between tools.
If a domain has no MX records, mail may fall back to its A record per RFC 5321. A single "Null MX" record (priority 0 with no host) means the domain explicitly accepts no email.
Yes. The lookup runs entirely in your browser using public DNS-over-HTTPS. No data is stored or tracked.
MX changes propagate as the old record's TTL expires, often within minutes to a few hours but up to 24 to 48 hours worldwide. Lowering the TTL before a migration makes the cutover faster.
Indirectly. MX records route incoming mail, while SPF, DKIM, and DMARC govern whether your outbound mail is trusted. Correct MX records plus aligned authentication records together give the best inbox placement.
Did you find this page helpful?
TestMu AI forEnterprise
Get access to solutions built on Enterprise
grade security, privacy, & compliance