MX Record Lookup

Queries a domain's MX records over DNS-over-HTTPS directly from your browser and lists its mail servers in priority order, lowest number first. A free online tool from Staaarter, right in your browser.

Runs locallyUpdated 2026-07-25

Overview

Introduction

Before a mail server can deliver a message to a domain, it needs to know which host actually accepts mail for it, which is exactly what an MX record answers.

This tool looks up a domain's MX records over DNS-over-HTTPS and lists them in the order a sending server would actually try them.

What Is MX Record Lookup?

An MX record lookup that queries a domain's mail exchanger records and sorts them by priority, lowest (most preferred) first.

It's part of this site's DNS & Domain Tools collection; the DNS query is a real, live request to a public resolver.

How MX Record Lookup Works

The domain is queried for its MX record type via DNS-over-HTTPS, which returns each mail server's hostname paired with a numeric priority.

Results are parsed and sorted so the most-preferred (lowest-numbered) mail server appears first, matching real delivery order.

When To Use MX Record Lookup

Use it when setting up or migrating email hosting, to confirm the MX records actually point at the provider you expect.

It's also useful for a quick sanity check when diagnosing 'mail isn't arriving' reports, to rule out a missing or misconfigured MX record.

Often used alongside DKIM Record Checker and MTA-STS Checker.

Features

Advantages

  • Shows records already sorted by delivery priority instead of in arbitrary DNS response order.
  • A single, fast lookup for confirming mail routing without a terminal or dig installed.

Limitations

  • Only reports what's published in DNS; it doesn't test whether the listed mail servers are actually reachable or accepting connections.
  • Doesn't check SPF, DKIM, or DMARC, which also affect whether mail from or to this domain is trusted.

Examples

A domain with a primary and backup mail server

Input

example.com

Output

10 → mail1.example.com
20 → mail2.example.com

mail1.example.com is tried first (priority 10); mail2.example.com is the backup (priority 20).

Best Practices & Notes

Best Practices

  • Verify MX records right after migrating email providers, before decommissioning the old provider's mailboxes.
  • Check this alongside SPF and DKIM records when setting up a new domain for outbound and inbound mail together.

Developer Notes

MX record data from DoH JSON APIs comes back as a single string like '10 mail.example.com.', so it's split on whitespace into a numeric priority and a hostname, with the trailing root dot stripped for display.

MX Record Lookup Use Cases

  • Confirming MX records point at the correct provider after a domain or email migration
  • Diagnosing inbound mail delivery failures by checking whether MX records exist at all
  • Auditing a newly acquired domain's existing mail configuration before making changes

Common Mistakes

  • Forgetting to update MX records as part of a provider migration, leaving mail routed to a decommissioned server.
  • Assuming a domain with no MX records can't send mail; MX only governs receiving, outbound delivery depends on the sending server's own configuration.

Tips

  • Check MTA-STS and DKIM for the same domain right after confirming MX, since all three are usually configured together during mail setup.

References

Frequently Asked Questions