Network Tools

MX Lookup

Ready
Domains
0 domains0 MX recordsNo resolver
DomainPriorityMail ExchangerTTLResolved IPsResolverMessageCopy
No MX lookup has run yet.
Lookup runs only when you click Lookup MX. Extra exchanger IP lookups run only when the checkbox is enabled.

Mail DNS checks

MX lookup online for mail exchanger records

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.

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.

MX priority and TTL table

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.

Optional exchanger IP lookup

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.

How to check MX records

  1. 1. Paste one domain or URL per line in the input panel.
  2. 2. Choose the DNS-over-HTTPS resolver: Cloudflare or Google.
  3. 3. Set a timeout that fits your network conditions.
  4. 4. Enable Resolve exchanger A/AAAA IPs only if you need visible exchanger addresses.
  5. 5. Click Lookup MX and review priority, exchanger, TTL, resolver and messages.
  6. 6. Copy an exchanger, copy the result table, or download JSON/CSV for a ticket or migration checklist.

Practical use cases

  • Confirm that a domain points to the expected Google Workspace, Microsoft 365 or custom mail provider MX records.
  • Check mail-routing changes during migration windows and compare resolver output while DNS propagation settles.
  • Debug support tickets where a domain has no MX records, unexpected fallback hosts or stale TTL values.
  • Document DNS state for operations handoff with CSV or JSON exports.

Input and output guidance

Valid input

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.

Reading priority

Lower MX priority numbers are preferred first by mail senders. Multiple records can share a priority, and fallback hosts usually have higher numbers.

Reading TTL

TTL is the resolver-provided cache lifetime in seconds. A high TTL can make changes appear slower across public resolvers during a migration.

Limitations, privacy and accuracy

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.

Related network tools

MX lookup FAQ

What does this MX lookup online tool check?

It checks DNS MX records for each domain you enter and reports the mail exchanger host, priority, TTL, resolver source and lookup message.

Do MX records prove that email delivery is working?

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.

Can I check Google Workspace or Microsoft 365 migrations with this page?

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.

Why do MX lookup results vary between resolvers?

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.

Does the tool resolve exchanger IP addresses?

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.

When should I use DNS Lookup instead of 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.