Domain and URL cleanup
The input accepts domains or URLs, extracts hostnames where possible, removes duplicate domains and flags invalid input such as IP addresses, spaces or incomplete hostnames.
Network Tools
| Domain | Priority | Mail Exchanger | TTL | Resolved IPs | Resolver | Message | Copy |
|---|---|---|---|---|---|---|---|
| No MX lookup has run yet. | |||||||
Run a lookup to see raw JSON output.
Mail DNS checks
This MX lookup online tool checks which mail servers are published for a domain and shows the records in a practical table. It is built for developers, support teams, DNS admins and operations teams who need to inspect mail routing during setup, migration or troubleshooting. Paste one domain or URL per line, choose Cloudflare or Google DNS-over-HTTPS, decide whether to resolve exchanger A/AAAA addresses, then run the lookup explicitly. The result shows exchanger hostnames, priority values, TTL, resolver source, messages and exportable JSON or CSV output.
The input accepts domains or URLs, extracts hostnames where possible, removes duplicate domains and flags invalid input such as IP addresses, spaces or incomplete hostnames.
Results include mail exchanger hosts, priority values, TTL and resolver source. Records are sorted by priority so primary and fallback mail servers are easier to compare.
When Resolve exchanger A/AAAA IPs is enabled, the page performs visible address lookups for each exchanger host and includes the resulting IPv4 or IPv6 addresses in the table.
Use domains such as example.com or full URLs whose hostname should be checked. IP literals, single-label names and malformed domain labels are rejected.
Lower MX priority numbers are preferred first by mail senders. Multiple records can share a priority, and fallback hosts usually have higher numbers.
TTL is the resolver-provided cache lifetime in seconds. A high TTL can make changes appear slower across public resolvers during a migration.
MX records explain where inbound mail should be routed, but they do not prove end-to-end email deliverability. SPF, DKIM, DMARC, mailbox configuration, provider health, reputation and DNS propagation still matter. Results can vary by resolver and cache, so compare Cloudflare and Google when a migration looks inconsistent. The lookup runs through browser fetch requests to the selected DNS-over-HTTPS resolver after you click Lookup MX. For TXT records such as SPF, DKIM and DMARC, use the DNS Lookup page.
It checks DNS MX records for each domain you enter and reports the mail exchanger host, priority, TTL, resolver source and lookup message.
No. MX records show where mail should be routed, but deliverability also depends on SPF, DKIM, DMARC, mailbox setup, provider state, reputation and DNS propagation.
Yes. You can compare the returned exchanger hosts and priorities with the records required by Google Workspace, Microsoft 365 or another mail provider during a migration.
DNS answers can vary because resolvers cache records, see propagation at different times or apply different upstream behavior. The page shows the selected resolver so you know where the answer came from.
Yes, if Resolve exchanger A/AAAA IPs is enabled. The page then runs visible A and AAAA lookups for each mail exchanger host after the MX lookup.
Use MX Lookup when you only need mail exchanger routing. Use DNS Lookup when you need TXT records such as SPF, DKIM or DMARC, or other DNS record types.