MX record discovery
Fetches all published MX records and sorts by priority — lowest number tried first.
Free tools
Enter any domain to look up MX records, priority values, mail hostnames, and resolved IP addresses for inbound mail routing context.
Query mail exchange records, sort by priority, and resolve each host to IP addresses.
DNS query
MX domain.com
Lower priority number = tried first · Equal priorities may load-balance
Capabilities
See where a domain receives mail, which host is primary, and whether DNS is configured correctly.
Fetches all published MX records and sorts by priority — lowest number tried first.
Resolves each MX exchange to A and AAAA addresses for routing troubleshooting.
See primary vs backup hosts and equal-priority load balancing at a glance.
Identifies RFC 7505 null MX (0 .) domains that do not accept inbound mail.
When no MX exists, checks apex A/AAAA per RFC 5321 fallback behavior.
Image captcha, session verification, and per-IP rate limits for public use.
How to use
Use any domain — customer, competitor, or your own — to see inbound mail routing.
Complete the image challenge before querying DNS.
Lower priority numbers are preferred. Multiple equal priorities may load-balance.
Confirm each exchange resolves — broken hosts block inbound delivery.
MX is inbound routing; use SPF/DKIM/DMARC tools for outbound authentication.
Mail Exchange (MX) DNS records tell sending servers where to deliver email for a domain. Each record has a priority (preference) and a hostname of the receiving mail server.
Senders try lower priority numbers first. If multiple records share the same priority, mail may be load-balanced between them.
MX records control inbound delivery to your domain. They do not authorize outbound sending — that is SPF, DKIM, and DMARC.
MX lookup is still useful when migrating mail hosts, auditing customer domains, or verifying DNS after a provider change.
This tool reads public DNS only. It does not test SMTP connectivity or mailbox availability on the MX hosts.
DNS propagation delays can make recent changes invisible until TTL expires.
For regulatory context on commercial email in the United States, see the FTC CAN-SPAM compliance guide.
Delivery note: MailFleet helps users manage campaigns through their own sending providers. Delivery outcomes depend on sender reputation, DNS authentication, content quality, recipient engagement, list quality, provider rules, and mailbox filtering systems.
No. MX routes inbound mail. Outbound deliverability depends on SPF, DKIM, DMARC, content, and sender reputation.
Get started
Desktop sending with provider profiles — pair MX context with SPF, DKIM, and DMARC checks.
Available on
Same desktop experience across every platform — one workflow for your entire team.