Enter any domain and see its live MX (Mail Exchange) records — the servers responsible for receiving email on that domain's behalf — along with their priority order.
MX (Mail Exchange) records are entries in a domain's DNS configuration that tell the rest of the internet which mail servers are responsible for accepting email addressed to that domain. Each record has a priority number — lower numbers are tried first — so a domain can list a primary mail server and one or more backups. Without any MX records, a domain generally cannot receive email at all, even if the website itself works fine.
This tool performs a live lookup against a public DNS-over-HTTPS resolver and returns whatever records are currently published, sorted by priority, so you can quickly confirm whether a domain is set up to receive mail and which providers or servers it's routed through (which often reveals whether a company uses Google Workspace, Microsoft 365, or a custom mail server, based on the hostnames returned).
This is a standard first step when troubleshooting email delivery to a domain, verifying that a new domain's email has been configured correctly after a DNS change, or doing basic due diligence on whether an unfamiliar domain in an email address is actually capable of receiving mail before you invest time reaching out to someone there.
It's also worth re-running this lookup after any known change to a domain's email infrastructure — such as a migration between providers — since DNS updates can take time to propagate globally, and a lookup performed too soon after a change may still reflect cached, outdated records. Most DNS caches refresh within a few hours to a couple of days depending on the record's configured time-to-live, so a second check the following day is a reasonable way to confirm a change has fully taken effect.
No. MX records are public DNS data, visible to anyone on the internet who queries them — this is the same information any mail server checks before attempting delivery.
It generally means the domain isn't configured to receive email directly. Some organizations use a parent or subsidiary domain's mail servers instead, or the domain may simply not be set up for email at all.
DNS lookups inherently require querying the domain name system, which lives on the internet — there's no way to fetch live DNS records without a network request. This tool uses a public, privacy-respecting DNS-over-HTTPS resolver rather than a custom backend.
Often, yes — the hostnames in MX records frequently reveal the provider, since Google Workspace, Microsoft 365 and other providers use recognizable server naming patterns.
Results reflect the DNS records as currently published and cached by the resolver at query time, which is effectively real-time for most domains.