MX Lookup — Check a Domain’s Mail Servers

Enter a domain or email address to list its MX records in priority order, resolve each server’s IP addresses and identify who hosts the mailbox.

What is an MX record?

An MX (Mail Exchanger) record is the DNS entry that tells the rest of the internet where to deliver email for a domain. When someone sends a message to [email protected], their mail server looks up the MX records for example.com, sorts them by priority and connects to the first server that answers.

Each record has two parts: a priority (lower numbers are tried first) and a hostname. Several records with the same priority share load; higher numbers act as backups.

example.com.  3600  IN  MX  1   aspmx.l.google.com.
example.com.  3600  IN  MX  5   alt1.aspmx.l.google.com.

What this MX lookup checks

  • Every MX record, sorted by priority, with the IP addresses each mail server resolves to.
  • The email provider behind the domain — Google Workspace, Microsoft 365, Zoho, GoDaddy, Amazon SES and more — plus the matching SMTP settings to send through it.
  • Common mistakes: MX records pointing at IP addresses (not allowed), hostnames that do not resolve, missing MX records and null MX records.

MX records vs. SMTP server

MX records are for receiving mail. The server you use to send mail (your SMTP submission server) is usually different — for Google Workspace, MX points to aspmx.l.google.com but you send through smtp.gmail.com on port 587. This tool shows both, and you can test the sending side with our SMTP checker.

Fixing MX problems

  • No MX records — add the records your email provider gives you at your DNS host. Without them, mail falls back to the domain’s A record and usually bounces.
  • MX points to an IP address — create a hostname (e.g. mail.example.com) with an A record and point the MX at it.
  • Old provider still listed — after migrating, remove the previous provider’s MX records or some mail will keep going to the old mailbox.
  • Changes not showing — DNS changes propagate within the record’s TTL, typically minutes to a few hours.

Frequently asked questions

Enter the domain (or any email address at that domain) in the MX lookup above. The tool queries DNS live and lists every mail server with its priority and IP addresses. On the command line you can run dig MX example.com or nslookup -type=mx example.com.

Senders try the record with the lowest priority number first. If it is unreachable they move to the next one. Records with equal priority are used in random order to spread load.

Most changes are visible within minutes, but resolvers may cache the old answer until the previous TTL expires — commonly 1 hour and occasionally up to 48 hours. Lower the TTL a day before a planned migration.

Yes, but then it cannot reliably receive email. Senders fall back to the domain’s A record, which usually points at a web server that does not accept mail. Domains that should never receive email can publish a null MX (0 .).