When you send an email to someone@example.com, your mail server needs to know which server is responsible for receiving mail at example.com. It finds this out by querying the domain's MX (Mail Exchange) DNS records. Understanding MX records is essential for email deliverability troubleshooting, domain migrations, and email infrastructure configuration.

What Are MX Records?

MX records are a type of DNS (Domain Name System) record that specifies the mail servers responsible for accepting incoming email for a domain. Each MX record contains two pieces of information:

• Priority (Preference): A numerical value that determines the order in which mail servers are tried. Lower numbers indicate higher priority. If the primary server is unavailable, the sending server tries the next one in order.
• Exchange (Mail Server Host): The hostname of the mail server (e.g., mail.example.com or aspmx.l.google.com).

A typical MX record set looks like this:

This tells sending mail servers: try aspmx.l.google.com first. If that fails, try alt1.aspmx.l.google.com, and so on.

Common Use Cases

Troubleshooting Email Delivery

If emails to a domain are bouncing or not arriving, the first diagnostic step is to check the MX records. Misconfigured or missing MX records are the most common cause of email delivery failures after domain transfers or DNS changes.

Verifying Email Provider Setup

When you move to a new email provider (Google Workspace, Microsoft 365, Zoho, etc.), you must update your domain's MX records to point to the new provider's mail servers. This tool lets you confirm the change has propagated correctly.

Identifying Email Providers

MX record hostnames reveal which email service a company uses. Hostnames ending in google.com indicate Google Workspace. Those ending in outlook.com or protection.outlook.com indicate Microsoft 365. This is useful for sales, outreach, and security research.

Email Security Auditing

MX records work alongside other email-specific DNS records. If you are auditing email security, always check MX records alongside:

• SPF records (TXT): Define which servers can send email on behalf of the domain
• DKIM records (TXT): Provide a cryptographic signature to verify email authenticity
• DMARC records (TXT): Set policies for handling email that fails SPF/DKIM checks

How to Use the MX Record Lookup

1. Enter the domain name (e.g., google.com) in the input field. You can paste a full URL — the tool automatically strips the protocol and path.
2. Click Lookup MX to query Cloudflare's secure DNS-over-HTTPS resolver.
3. Results appear sorted by priority, with the primary mail server highlighted.

How DNS Propagation Affects MX Lookups

After changing MX records, the new values may not be immediately visible worldwide because of DNS caching (TTL — Time to Live). The TTL value on the previous MX record determines how long resolvers cache the old value. Common TTL values range from 300 seconds (5 minutes) to 86400 seconds (24 hours). Always wait for the full TTL period after making DNS changes before confirming they have propagated.