Free MX record checker

MX Record Lookup

Find the mail servers that receive email for any domain, with priorities, IP addresses and the email provider behind them.

Free, no sign-up. We only read public DNS records and do not keep what you check.

Result look wrong, or not sure what to change? A GoProIT technician can check it with you over a secure remote session. $59 per fix, Monday to Friday 8am to 8pm Eastern.

Book a technician(844) 734-1288

What an MX record is

An MX (mail exchanger) record tells the rest of the internet which server accepts email for your domain. When someone emails you@yourcompany.com, their mail server looks up the MX records for yourcompany.com and delivers the message to the server listed there.

Each MX record has a priority number. Lower numbers are tried first. If two records share the same number, senders spread mail between them. Higher numbers are backups used only when the first servers don’t answer.

Typical MX records by provider

ProviderWhat the MX record looks like
Microsoft 365One record: yourcompany-com.mail.protection.outlook.com. Newer tenants may get a host ending in mx.microsoft.
Google Workspacesmtp.google.com with priority 1 for newer setups, or the older set of five aspmx.l.google.com records. Both work.
Hostinger Emailmx1.hostinger.com and mx2.hostinger.com
Security gateway (Proofpoint, Mimecast, Barracuda)The gateway’s hosts. Mail is filtered there, then passed on to Microsoft 365 or Google.

Common MX problems this lookup finds

  • Leftover records from an old provider. After moving from GoDaddy or your web host to Microsoft 365, the old MX records are often left behind. Some mail then goes to a mailbox nobody reads.
  • No MX record at all. The domain can’t receive email. This often happens when a domain is moved to a new DNS host and only the website records are copied.
  • A mail server that doesn’t resolve. The MX points to a hostname that no longer exists, so senders get errors or delays.
  • An MX record that points to an IP address. MX records must contain a hostname. Create an A record for the IP and point the MX at it.

How to check MX records yourself

This MX lookup tool queries public DNS for you, but you can also check MX records from your own computer. It’s useful when you want to see what your office network sees, or when you need to test a specific DNS server.

Windows 11: Command Prompt

Press the Windows key, type cmd and press Enter. Then run:

nslookup -type=mx yourcompany.com

The answer lists each record as MX preference = 0, mail exchanger = yourcompany-com.mail.protection.outlook.com. “Non-authoritative answer” above the list is normal. It just means the reply came from a resolver’s cache, not from your domain’s own DNS server.

To ask a particular resolver, add its address at the end, for example nslookup -type=mx yourcompany.com 1.1.1.1 for Cloudflare or 8.8.8.8 for Google.

Windows 11: PowerShell

PowerShell gives cleaner output:

Resolve-DnsName yourcompany.com -Type MX

You’ll get a small table with NameExchange (the mail server) and Preference (the priority).

macOS or Linux: Terminal

Open Terminal and run dig mx yourcompany.com +short. Each line shows the priority, then the server name. Use dig mx yourcompany.com @8.8.8.8 +short to query a specific resolver.

Checking the source, not a cache

Right after a change, resolvers may still hold the old answer. To see what your DNS host is publishing right now, find your nameservers with nslookup -type=ns yourcompany.com, then query one of them directly, for example nslookup -type=mx yourcompany.com ns1.yourdnshost.com. If that shows the new record, the change is saved and you’re only waiting for caches to expire. The DNS propagation checker does this across several resolvers at once.

How to read your MX lookup results

What you seeWhat it means
One record pointing to mail.protection.outlook.comNormal for Microsoft 365. One MX is all Microsoft needs.
smtp.google.com, or five aspmx recordsNormal for Google Workspace.
Microsoft or Google plus another provider’s hostsUsually a leftover from a migration. Some mail is going to the wrong place.
A single record of 0 . (a dot)A “null MX”. The domain owner has declared that it doesn’t accept email at all. That’s correct for a domain used only for a website.
No MX record foundSenders fall back to the domain’s A record, which is usually a web server that won’t accept mail. Treat it as broken if you expect email.
MX host with no IP addressThe server name doesn’t resolve. Senders will queue and then bounce your mail.

How to change MX records at common DNS hosts

Make the change wherever your nameservers point. Run the NS lookup above if you’re not sure which company that is.

  • GoDaddy: open your Domain Portfolio, select the domain, go to DNS, then DNS Records. Edit or delete the existing MX rows and use Add New Record with type MX.
  • Cloudflare: select the domain, open DNS, then Records, and click Add record with type MX. If your MX points to a hostname on your own domain, such as mail.yourcompany.com, the A record for that name must be set to DNS only (grey cloud), because Cloudflare’s proxy doesn’t carry email.
  • Namecheap: go to Domain List, click Manage, open Advanced DNS, and under Mail Settings choose Custom MX before adding your records.
  • Squarespace Domains: open the domain’s DNS settings and add the MX rows under custom records. Remove any default mail records Squarespace added if you use a different provider.

In every case, the host field is usually @, which means the domain itself. Enter the mail server name exactly as your provider gives it.

Switching email providers without losing mail

Most lost email during a move happens because MX records were changed on the wrong day or the old provider was cancelled too soon. A safer order for a typical small office moving from host-provided email to Microsoft 365 or Google Workspace:

  1. A day or two before, lower the TTL on your current MX records to 300 seconds (5 minutes). Shorter TTLs mean the switch spreads faster.
  2. Verify the domain with the new provider and create every mailbox first. Mail that arrives for a user who doesn’t exist yet will bounce.
  3. Copy the existing mail across, or at least the last few months of it.
  4. Change the MX records, ideally late in the day. Delete the old provider’s MX rows at the same time.
  5. Run this MX lookup again from outside your network and confirm only the new records show.
  6. Keep the old mailboxes open for at least a week and check them. A few senders hold old answers longer than they should.

If you’re planning a move and want someone to handle the DNS side, a technician can do it over a remote support session for a one-time $59.

When the MX lookup looks right but mail still doesn’t arrive

Correct MX records only get mail to the front door of your provider. If senders still get bounces, the problem is further in. Common examples:

  • 550 5.1.1 or “recipient not found”: the mailbox or alias doesn’t exist at the new provider, or the address is misspelt.
  • Microsoft 365 rejects mail for your domain: the domain isn’t fully verified as an accepted domain in the Microsoft 365 admin center under Settings, Domains.
  • Mail arrives, but in the wrong folder: an inbox rule or a quarantine policy is moving it. Check the user’s rules and the quarantine in the Microsoft Defender portal or Google Admin console.
  • Only some senders fail: a security gateway in front of your mailboxes may be blocking them, or their server is still using a cached old MX.

Frequently asked questions

How long does an MX record change take to work?

Usually 5 to 60 minutes, but it can take up to the TTL of the old record, often 1 to 4 hours and at most 24 or 48 hours. During that time some senders still use the old server, so keep the old mailbox active until the change has fully spread.

Can I have MX records for two email providers?

Only if one is a security gateway that forwards mail to the other. Two separate mailbox providers (for example Microsoft 365 and Google Workspace) on the same domain will split your incoming email between them at random.

Why does this tool show different MX records than my registrar?

Your domain uses whichever DNS host is set in its nameservers. If you changed nameservers to Cloudflare or your web host, edits at the registrar have no effect. Make the change at the DNS host the nameservers point to.

What does a priority of 0 or 10 mean?

The number only matters compared with your other MX records. Lower is tried first. A single MX record with priority 0, 1 or 10 behaves exactly the same.

Does every domain need an MX record?

Only domains that receive email. A domain used just for a website can skip it, but it’s better to publish a null MX (0 .) so senders know straight away not to try. Without either, some servers will try to deliver to the website’s IP address.

Can an MX record point to a CNAME?

It shouldn’t. The DNS standards say an MX record must point to a hostname that has its own A or AAAA record, not to an alias. Some servers tolerate a CNAME, but others will refuse to deliver, so point MX records straight at the real mail server name.

Do MX records affect sending email?

No. MX records only control where incoming mail is delivered. Whether your outgoing mail is trusted depends on SPF, DKIM and DMARC, which you can test with the email domain health check.

How do I find out who hosts a domain’s email?

Run an MX record lookup on the domain. The hostnames usually reveal the provider: outlook.com means Microsoft 365, google.com means Google Workspace, and names like pphosted.com or mimecast.com point to a security gateway sitting in front of the real mailboxes.

Related guides

Moving email to Microsoft 365 or Google?We plan the MX switch so no mail is lost on the way.
Get help from a technician

More free tools

See all 30 free IT tools

Free tools find it. We fix it.

Want a technician to sort it out for you?

One-time remote fix for $59, or unlimited help for your whole team at $49 per user per month. No contract and no setup fee.

WhatsApp us(202) 960-2022 · messages