Skip to content

Platform

Send: campaigns Send: SMTP relay & Email API Verify Deliver AI Automation All features

Developers

API documentation Email API overview Integrations Custom domains

Solutions

Small businesses E-commerce Agencies Startups & SaaS Creators & individuals

Resources

Blog Help center Free tools Free email verifier Blacklist checker Compare platforms Pricing

Free · no sign-up

MX record lookup

See which mail servers receive email for a domain, in priority order, with their IP addresses, reverse DNS and the email provider behind them.

What this MX lookup shows

Every domain that receives email publishes one or more MX records. This tool reads them straight from DNS and, for each mail server, shows:

  • Priority — the order in which other servers try to deliver;
  • IP address — where the host name points, and whether it is reachable from the internet;
  • Reverse DNS — the PTR name of that IP, which helps identify the operator;
  • Email provider — recognised automatically for Google Workspace, Microsoft 365, Zoho, Proton, Fastmail and many others.

Common MX problems

  • No MX record: mail falls back to the domain's A record and is usually lost. Add the MX records your email provider gives you.
  • MX pointing to an IP address or a CNAME: not allowed by the standard and rejected by some senders.
  • Old records left behind after moving to a new provider: some mail keeps going to the old server. Remove MX records you no longer use.
  • Host names that do not resolve: a typo in the target host means mail cannot be delivered at all.

MX records and email deliverability

MX records decide where you receive mail, but they also matter when you send: bounce messages and replies go to your domain, and some spam filters check that a sending domain can receive mail. If you send newsletters or transactional email, make sure your domain has working MX records and valid SPF, DKIM and DMARC records. Our guide to SPF, DKIM and DMARC explains how they fit together.

Before you send to a list, you can also check that each recipient's domain has mail servers — that is one of the checks in InboxRoads bulk email verification.

Frequently asked questions

An MX (mail exchanger) record is a DNS record that tells other mail servers where to deliver email for a domain. Each MX record has a host name and a priority number; senders try the lowest number first.

Lower numbers are tried first. If the server with priority 10 does not answer, senders try the next one (for example priority 20). Records with the same priority share the load.

No. The standard (RFC 5321) requires a host name. Create an A record such as mail.example.com and point the MX record at that name.

Most changes are visible within minutes to a few hours, depending on the TTL of the old record. Some resolvers cache records for up to 48 hours.

Not strictly — MX records control receiving. But many spam filters check that the sending domain can receive replies and bounces, so a domain that sends email should also have working MX records.

Verify your whole list, not just one address

Upload a CSV and InboxRoads checks every address, removes duplicates for free and gives you clean files to download.