How to read your MX record lookup results
MX records tell every mail server on the internet where to deliver email for your domain. The MX lookup above lists them in the order senders try them, with the IP address behind each host. The notes below explain what the result means and how to spot a broken setup.
MX record format and priority
Each MX record has two parts: a priority number and a mail server hostname. Lower numbers are tried first. A domain with two records at priority 10 and 20 sends everything to the first server and uses the second only when the first doesn't answer. Two records with the same number share the load. Every MX value must be a hostname, never a bare IP address, and that hostname must have its own A or AAAA record.
MX records for popular email providers
| Provider | Typical MX host | Priority |
|---|---|---|
| Google Workspace (new setups) | smtp.google.com | 1 |
| Google Workspace (older setups) | aspmx.l.google.com plus alt1 to alt4 | 1, 5, 10 |
| Microsoft 365 | yourdomain-com.mail.protection.outlook.com | 0 |
| Zoho Mail (US) | mx.zoho.com, mx2.zoho.com, mx3.zoho.com | 10, 20, 50 |
Providers update these values from time to time, so confirm them in the admin console when you set up a domain. The lookup is also a fast way to find which provider handles mail for any company domain: the MX host gives it away. For Outlook specifics, see our guide on Outlook MX records and rDNS setup.
Common MX record problems
A domain with no MX records falls back to its A record, which usually points to a web server that doesn't accept mail, so messages bounce. MX records that point to a CNAME or an IP address break the standard and some senders refuse them. Leftover records from an old provider are another frequent issue: after a migration, part of your mail can still go to the server you stopped using. A host that resolves but doesn't respond on port 25 also shows up here as unreachable. One special case is a null MX, a single record with priority 0 and a dot as the host, which tells senders the domain accepts no mail at all. It's correct for parked domains and a mistake on any domain you send from. More background in what DNS MX, A and rDNS records do.
Does an MX record affect email deliverability?
MX records handle incoming mail, but they matter for sending too. Many spam filters check that the sender's domain can receive replies and bounces, and a domain with broken MX looks like a throwaway.
Next step after the MX lookup
Mail servers in order? Check the records that decide whether your outgoing mail is trusted. The DNS Record Checker reviews SPF, DKIM, DMARC and MX in one pass, and the Blacklist Checker shows whether your mail server IPs are listed. Warmy keeps an eye on all of it daily and warms up your mailboxes so they land in the inbox.
Mail servers look good? Make sure your emails reach the inbox. Try Warmy free for 7 days or book a demo.

























