Network & Domain

MX Record Lookup

Inspect a domain’s mail exchangers and priority values.

Read the guide

Run the tool

JVR Software’s server processes the public target you enter. The diagnostic is rate-limited. Use a system you own or are authorised to check.

More information

Back to the tool

What it is and when to use it

MX Record Lookup lists the public mail exchangers for a domain. It is useful before and after a mail-provider migration, when incoming mail is routed somewhere unexpected, or when technical support needs to verify the destination that other servers are being told to use.

How it works

An MX record contains a target hostname and a numeric preference. Sending servers normally try the lowest number first. Equal numbers describe equivalent preference, while a higher number commonly represents a fallback. The MX lookup asks for that record type rather than attempting to connect to an inbox or send a message.

How to use it

  1. Enter the part after the @ in the address that should receive mail.
  2. Compare target hostnames and priority numbers with the values provided by your mail host.
  3. After a change, check again once the previous TTL has had time to expire.

Worked example

Suppose mx1 has a preference of 10 and mx2 has a preference of 20. Other mail systems normally try mx1 before mx2. If both have a preference of 10, neither has preference based on that field alone.

Reading the result

In the output, look for target and pri, then check TTL. A target of a single dot with priority 0 is a deliberate null MX and indicates the domain says it accepts no mail. An empty answer is a different condition and needs investigation before drawing a conclusion.

When testing a migration, compare the result with the exact list from your inbound mail provider. If both providers appear, delivery may reach either service depending on priority and reachability. Check that all intended mailboxes exist at the active destinations before removing a working old route.

Common mistakes and limits

MX describes incoming mail routing. It does not prove that a mailbox exists, that a provider accepts mail for this domain, or that outgoing messages pass SPF or DKIM. Use Email DNS Health for authentication records and check provider delivery logs for real messages through authorised channels.