MX Record Checker

Look up the mail servers and priority values published in a domain's DNS. Use the results to review mail-routing configuration or identify missing MX records.

Check MX Records

Try:

What We Check

📧 MX Records

DNS lookup of mail exchange records showing priority and mail server hostnames.

🔢 Priority Order

Sort the published records so the preferred mail route is easy to identify.

🔎 Missing Records

Identify when the DNS resolver returns no MX records for the domain.

🧭 Redundancy Context

See whether multiple routes are published and how their priorities differ.

Understanding Results

✅ Records Found

The resolver returned one or more published MX records and priority values.

ℹ️ One Record Found

A single record can be valid. Confirm with your provider whether it represents the availability design you expect.

❌ No Records Found

The resolver returned no MX records. The domain may not accept mail, its DNS may be misconfigured, or the lookup may have failed.

Best Practices

  • Use multiple MX records for redundancy
  • Set appropriate priority values (10, 20, 30)
  • Verify server availability separately with your email provider
  • Use fully qualified domain names (FQDN)
  • Avoid pointing MX to CNAME records
  • Review DNS changes from more than one resolver when propagation matters

MX Priority Guide

Primary Server

Priority: 10
Server: mail.example.com

Lowest priority number = highest priority. This server receives all email traffic first.

Backup Server

Priority: 20
Server: mail2.example.com

A sending server can try this route after the lower-numbered route. Confirm the behavior with your email provider.

Tertiary Server

Priority: 30
Server: mail3.example.com

An additional route in this example. More records do not guarantee availability unless the underlying systems are independently resilient.

Common Issues & Solutions

No MX Records Found

Cause: Domain has no MX records configured in DNS.
Solution: Add MX records pointing to your mail server in your DNS settings.

⚠️

Unexpected Mail Server Hostname

Cause: A stale or incorrect hostname may be published in DNS.
Solution:Compare the result with your email provider's required MX values and update DNS if needed.

ℹ️

Single Point of Failure

Observation: Only one MX record is published.
Next step: Ask your provider whether that hostname already represents a redundant service before adding records.

Frequently Asked Questions

What are MX records?

MX (Mail Exchange) records are DNS entries that specify which mail servers handle email delivery for a domain. They include priority values to determine the order in which servers should be contacted.

Why check MX records?

Checking MX records helps verify email configuration, troubleshoot delivery issues, ensure redundancy with backup servers, and confirm that emails can be delivered to your domain.

What does MX record priority mean?

MX priority determines the order mail servers are contacted. Lower numbers have higher priority. If the primary server (lowest number) is unavailable, mail is routed to the next priority server.

How many MX records should I have?

Domains that receive email normally publish at least one MX record. Multiple records can provide redundancy when they point to independently available mail systems, but the right design depends on your email provider.

Does this tool test SMTP delivery?

No. This tool performs a DNS MX lookup only. It does not connect to the listed servers, send a message, verify inbox placement, or measure sender reputation.

What causes MX record issues?

Common DNS-side issues include missing MX records, incorrect mail-server hostnames, unexpected priorities, or records that have not reached the resolver being queried. Server availability must be checked separately.