MX Record Lookup

See which mail servers receive email for a domain. Enter a domain and the lookup shows its MX records, each with its priority and TTL, sorted with the most-preferred server first. The query runs live against a public DNS resolver over a secure connection from your browser, so results reflect what is published now (though they may be cached — note the TTL).

Read the guide: How to Check MX Records
Look up a domain to see which mail servers receive its email, in priority order. Records come from a public resolver over a secure connection and may be cached (TTL).

How it works

  1. 1

    Enter the domain

    Type the email domain you want to check, for example the part after the @ in an address.

  2. 2

    Look up the MX records

    Press Look up. A public resolver returns the mail-exchange records published for that domain.

  3. 3

    Read priority and host

    Each row shows a priority number and a mail server. Lower numbers are tried first; the rest are fallbacks. The TTL is how long the answer may be cached.

Instant & 100% private — nothing is uploaded

Everything runs locally in your browser. Your code, text and files are processed on your own device and are never sent to a server — so there are no upload waits, no size limits from us, and nothing is ever stored or logged.

Frequently asked questions

What does the MX priority number mean?
Each MX record has a preference value, usually called the priority. Sending servers try the record with the lowest number first, and only move to higher numbers if that host is unreachable. So priority 10 is preferred over priority 20. Equal numbers share the load. This tool sorts the records by priority for you.
A domain has no MX records — can it still get email?
If there is no MX record, mail servers fall back to the domain’s A or AAAA record under the standard, but most modern setups always publish an MX. No MX and no address record means the domain cannot receive mail at all, which is common for domains used only for a website.
Are these results live or cached?
They come from a public resolver over a secure connection, so they reflect what is published, but the resolver may serve a cached copy. The TTL on each record is how many seconds that cache is valid. Right after a change you may see the old servers until the TTL runs out.