Skip to content
AdminKit

How do you read an MX lookup result?

AdminKit's MX lookup result lists the mail hosts a domain has published, each with a priority number, then shows whether each host actually resolves to an IP address: a lower number is tried first, hosts sharing one priority are an equally-ranked group, and a host with no A/AAAA record is a stale entry that cannot receive mail despite still appearing.

By AdminKit team, Netbase JSC · Updated

Key takeaways

  • The result has two parts: the MX records themselves (priority and host name) and a check of whether each host resolves to an IPv4 or IPv6 address.
  • The lowest priority number is tried first. Hosts that share a number form one group, and senders must pick among them at random.
  • A host that shows none for both IPv4 and IPv6 can’t receive mail. If it’s a backup, the gap only shows up when the primary fails.
  • No MX records means senders fall back to the domain’s own address. A domain that never takes mail should publish a null MX, which shows up as a single 0 . record.
  • A resolving host isn’t proof that mail works. The lookup doesn’t connect to port 25 or test TLS.

What does an MX lookup result show?

An MX lookup answers two separate questions at once, and reading the result correctly means keeping them apart. The first layer is the MX record itself: which hostnames a domain has designated as mail servers, and in what priority order. The second layer, which a plain MX query doesn’t give you, is whether each of those hostnames currently resolves to an IP address at all. RFC 1035 defines the MX record as holding only a preference number and a hostname — never an address — and the MX record type itself (type code 15) is registered alongside every other DNS record type in IANA’s DNS Parameters registry. So AdminKit’s MX lookup tool runs a second round of A/AAAA lookups against each returned host (up to 5) specifically to close that gap, showing at a glance whether a correctly-listed host can actually be reached, not just whether it appears in the record.

On the page, the two layers appear as two tables. Here is an illustrative result for a domain with a primary and a backup host, using documentation names and addresses. The first table lists the records, sorted with the lowest priority first:

NameTypeTTLData
example.comMX3600s10 mail1.example.com.
example.comMX3600s20 mail2.example.com.

The second table, headed “Do the mail hosts resolve?”, shows what each host’s A and AAAA lookups returned:

HostIPv4 (A)IPv6 (AAAA)
mail1.example.com192.0.2.102001:db8::10
mail2.example.com198.51.100.20none

This one is healthy. Both hosts resolve, and the backup simply has no IPv6 address, which is fine as long as it has an IPv4 one. Senders need only one working address to connect.

How do you read the priority column?

Each row in the result pairs a hostname with a priority (preference) number, and the rule is always the same: lower numbers are tried first. Cloudflare’s own explainer on MX records describes the identical convention — the mail server with the lowest preference value is tried first — confirming this isn’t an AdminKit-specific reading of the field. A domain listing 10 mail1.example.com and 20 mail2.example.com is telling every sending server to attempt mail1 first and fall back to mail2 only if mail1 is unreachable. Two or more hosts sharing the identical priority number form a single, equally-ranked group instead. RFC 5321 §5.1 says a sender “MUST randomize them to spread the load”, which is how organizations spread mail across more than one server without declaring a strict primary/backup relationship. The mechanics of ties, fallbacks and the “null MX” convention for domains that handle no mail at all are covered in more depth in what MX record priority actually does; this guide focuses on reading the result you’re looking at right now rather than re-deriving that logic.

The numbers only matter relative to each other. 10 and 20 behave the same as 1 and 2. What to look for is whether the host you expect to take most of your mail has the lowest number, and whether anything below it belongs to a provider you no longer use.

What does the TTL column tell you?

The TTL is the number of seconds a resolver may cache the record before it has to ask again. RFC 1035 defines it as “the time interval (in seconds) that the resource record may be cached before it should be discarded”. AdminKit’s lookup goes through a recursive resolver, so the TTL you see is the one that resolver returned. If the record was already in its cache, the number can be lower than the TTL in your zone file, because a cached TTL counts down while the record is stored. RFC 2308 §5 describes negative answers decrementing “in a similar manner to a normal cached answer”.

Two practical readings follow. A long TTL, such as a day, means a change you make now can take up to a day to reach every resolver that cached the old answer. And a “no records” answer is cached too, for a time set by the zone’s SOA record (RFC 2308). If you looked up a domain before adding its MX records, an empty answer can linger for a while after you fix it.

What does it mean when a listed host doesn’t resolve?

The single most useful thing the second A/AAAA round tells you is the difference between a host that’s merely listed and one that’s actually reachable. A host with no A or AAAA record cannot receive an SMTP connection, full stop — a sending server has no address to connect to, regardless of how correctly its priority is configured. This shows up in two very different ways depending on which host is affected:

  • The only host, or the lowest-priority host, doesn’t resolve. Mail delivery is broken right now, not just at risk. Fix the missing record immediately.
  • A higher-priority backup host doesn’t resolve. Delivery looks fine today because the primary is still working, but the redundancy you think you have doesn’t exist — the day the primary fails, there is nowhere for mail to fall back to. This is the more dangerous case precisely because nothing looks wrong until the moment it matters.

A related problem is an MX host that is an alias. RFC 2181 §10.3 says the name in an MX record “must not be an alias” and must have address records of its own. Because the address columns show everything the lookup returned, an alias can show up as a host name in front of the addresses. If you see that, point the MX record at the final host name instead. When an MX record points to a CNAME explains how mail software reacts to this.

What you seeWhat it meansWhat to do
Every host has an IPv4 or IPv6 addressRouting looks healthyCheck authentication next
Lowest-numbered host shows none twiceMail is going to a host that doesn’t existAdd its A/AAAA record, or fix the MX target
Only a backup host shows none twiceThe fallback is brokenFix or remove the backup record
A host name appears in an address columnThe MX target is an alias (CNAME)Point the MX at the canonical host name
Old and new providers’ hosts both listedA migration under way, or a leftoverRemove the old hosts once the cutover is done
A single 0 . record and no host tableNull MX: the domain accepts no mailFine, if the domain really never receives mail

How should you read a result during a provider migration?

A lookup run mid-migration often shows something that looks like a mistake but usually isn’t: both the old and new provider’s mail hosts, or only the old ones, days after you believed the change was complete. Every DNS record carries a TTL controlling how long a resolver may cache it before re-checking the authoritative answer, so a result can briefly lag the real, current record until that TTL expires everywhere it was cached — see DNS propagation and TTL explained for how long that realistically takes. Before assuming a migration failed, re-run the lookup after the old TTL has had time to expire, and confirm you’re checking the exact domain or subdomain the new provider told you to point mail at — the same check worth running after any domain transfer, as covered on our domain portfolio owners and buyers page. MX is only one of four records a provider switch touches — see migrating email providers without breaking SPF, DKIM or DMARC for the full cutover order. Provider setup pages give the values to compare against: Google Workspace’s MX record instructions give smtp.google.com with priority 1, and note that domains that started using Google Workspace before 2023 may still have legacy values beginning with “aspmx”.

If you publish an MTA-STS policy, it lists the MX host names senders should accept. AdminKit’s MTA-STS check reads that list back. Compare it with the hosts in your MX result after a migration: under an enforcing policy, senders refuse to deliver to an MX host the policy doesn’t cover.

Is an empty result a problem?

Not every domain is supposed to handle mail. A marketing redirect, a domain reserved purely for brand protection, or a subdomain used only for static assets can legitimately have no MX record at all. When no MX record exists, RFC 5321 §5.1 tells senders to treat the domain’s own A/AAAA address as an implicit MX “with a preference of 0”. That address usually belongs to a web server that doesn’t accept mail, so senders queue and retry instead of getting a clear answer. RFC 7505 standardizes a cleaner way to express that intent explicitly: a single MX record pointing at . (the DNS root), known as a null MX, telling any sender unambiguously not to bother trying. In AdminKit’s result, a null MX appears as one record with the data 0 . and no host table, because there is no host to resolve. An empty MX result on a domain that’s never meant to send or receive mail works, but a null MX says so explicitly; an empty result on a domain you expect to receive mail is the actual problem worth investigating, and is a strong sign no one has configured mail routing for it yet.

; Illustrative zone lines (documentation names)
example.com.         3600  IN  MX  10  mail1.example.com.   ; receives mail
parked-example.com.  3600  IN  MX  0   .                    ; null MX: accepts no mail

What doesn’t this result confirm?

A resolving A/AAAA record next to a mail host confirms only that the host exists on the network — nothing about whether it’s actually running a mail server, listening on port 25, or willing to accept a given message. That requires a live SMTP connection, which this lookup deliberately doesn’t attempt. It also says nothing about whether the server offers encryption; does your mail server actually enforce STARTTLS? covers that layer. Once you’ve confirmed mail is routing to the host you expect, the next question is usually whether messages sent through it will be trusted rather than rejected or marked as spam, which is a separate authentication layer covered in SPF, DKIM and DMARC explained, part of AdminKit’s email authentication cluster. Run AdminKit’s MX lookup first to confirm routing, then check authentication separately rather than assuming one implies the other.

This guide is general information, not a security audit of your specific network — see our disclaimer for what AdminKit's guidance does and does not commit to.

Frequently asked questions

Why does the result show IP addresses next to each mail hostname?

An MX record only ever contains a hostname, never an IP address directly, so AdminKit's MX lookup makes a second round of A/AAAA lookups against each returned host (up to 5) and shows the result next to it. This answers a question a plain MX query can't: not just 'is this host listed' but 'does this host currently resolve to anything a sending server could actually connect to.'

One of my listed mail hosts shows no A/AAAA record — is that a problem?

Yes, for that host specifically — a mail host with no A or AAAA record cannot receive a connection no matter how correctly its priority is set, since sending servers need an IP address to connect to. If it's your only host, mail delivery is broken; if it's a backup behind a working primary, it's a silent gap that only matters the day the primary actually fails. Either way, it needs a real DNS record, not just an MX entry pointing at a name nothing else resolves.

I just switched email providers — why does the lookup still show my old mail hosts?

This is almost always DNS caching, not a failed change: every DNS record carries a TTL that controls how long a resolver may keep serving the previous answer before re-checking the authoritative source. A lookup reflects what the resolver currently has cached, which can lag a real change until the old TTL expires everywhere it was cached — see dns propagation and TTL explained for realistic timelines before assuming the migration didn't take.

My MX lookup returns nothing at all — does that mean the domain is broken?

Not necessarily. It means either the domain genuinely isn't set up to receive mail (common for a domain that only hosts a website, or one reserved for brand protection), or it has a problem if mail was expected to work. Under RFC 5321 §5.1, senders then treat the domain's own A/AAAA address as an implicit mail host, which is usually a web server that doesn't accept mail. A domain that deliberately never handles mail should publish a null MX record rather than leave this ambiguous — see what MX record priority actually does for how a null MX differs from simply having no MX record at all.

Can I tell which email provider a domain uses just from the MX lookup result?

Sometimes, informally — many providers' mail hosts use a recognizable, consistent hostname pattern across their customers, so a familiar-looking hostname is a reasonable hint. It isn't a guarantee: a provider can change its naming at any time, and some organizations run mail infrastructure under their own domain name instead of a recognizable third-party one. Treat it as a clue worth a second look, not a confirmed identification.

Why does the result list more MX records than it resolves?

AdminKit's MX lookup shows every MX record the domain publishes, but makes the second round of A/AAAA lookups for at most 5 distinct mail hosts, to keep the result fast. Hosts beyond the fifth still appear in the records table without an address check. Check those with the DNS lookup tool, using record type A or AAAA.

Want AdminKit to watch this for you?

Free checks tell you the state today. Protective DNS and monitoring tell you when it changes.

Huy Nguyen (David), Founder and CEO of Netbase JSC

Talk to an expert

Huy Nguyen (David), Founder & CEO, Netbase JSC

Ask whether this fix applies to your setup, or get a second pair of eyes on your DNS and mail records.