Free MX Record Checker — Verify Mail Exchange DNS Setup
Free MX record lookup tool. Check your domain's mail exchange records, verify priorities, and ensure redundancy for reliable email delivery. Instant DNS results.
MX (Mail Exchange) records are DNS entries that specify which mail servers are responsible for receiving email on behalf of your domain. Properly configured MX records with correct priorities and redundancy are essential for reliable email delivery.
Enter your domain below to instantly look up its MX records.
What Are MX Records?
MX (Mail Exchange) records are a type of DNS record that tells the internet which mail servers are responsible for accepting email messages on behalf of your domain. When someone sends an email to your domain, their mail server queries DNS for your MX records to determine where to deliver the message.
Each MX record contains two key pieces of information: a priority value (also called preference) and the hostname of the mail server. The sending server will attempt delivery to the server with the lowest priority number first, and fall back to higher-numbered servers if the primary is unavailable.
Why MX Priority Matters
The priority value in an MX record determines the order in which mail servers are tried during delivery. A lower number means higher priority — a server with priority 10 will be tried before one with priority 20. This system allows you to designate a primary mail server and one or more backup servers.
Correct priority configuration ensures that your primary mail server handles most traffic while backup servers provide a safety net. If two MX records share the same priority, sending servers will distribute load between them randomly, which can be useful for load balancing across multiple servers.
MX Redundancy and Reliability
Having multiple MX records with different priorities provides redundancy for your email infrastructure. If your primary mail server goes down, sending servers will automatically retry delivery using the next server in the priority list. This failover mechanism is built into the SMTP protocol and requires no intervention on your part.
Best practices recommend having at least two MX records pointing to mail servers on different networks or hosting providers. This protects against network outages, hardware failures, and maintenance windows. Without redundancy, a single server failure could cause email to bounce or be delayed for extended periods.
Common MX Record Issues
- Missing MX records — email cannot be delivered to your domain at all
- MX pointing to a CNAME — violates RFC 2181 and can cause delivery failures
- Single MX record — no redundancy if the mail server goes offline
- Unreachable mail servers — MX hosts that do not respond on port 25
- Mismatched priorities — all records at the same priority when failover is intended
Improve your email deliverability with MailerBit
Built-in domain verification (we generate your DKIM and Return-Path records), automatic bounce and spam-complaint handling, and automatic warm-up for new domains — all included in your free trial.
Start Free TrialFurther reading on our blog

MX Records Explained: Why Replies to Your Emails Never Arrive
Your reminders reach the inbox, but client replies vanish? Learn what MX records do, how they differ from SPF and DKIM, the six most common MX mistakes and how to check yours.

How to Fix SPF Record Errors: A Step-by-Step Guide
Emails landing in spam? Fix the 8 most common SPF record errors, from duplicate records and the 10-lookup limit to +all and forgotten subdomains, with broken vs fixed examples.

Email Blacklist Check: Find Out If You're Listed and Get Delisted
Bounces mention Spamhaus and replies dried up? Learn how to check if your domain or IP is on an email blacklist, why it happened, and how to get delisted for good.

Email Deliverability in 2026: Keep Client Emails Out of Spam
A payment reminder in the spam folder is a payment that arrives late. A practical guide to authentication, warm-up and clean client data, so your notices reach the inbox.

Gmail, Yahoo & Microsoft Sender Requirements: Checklist
Gmail, Yahoo and Microsoft now enforce sender rules. A practical checklist of SPF, DKIM, DMARC, one-click unsubscribe and spam rate, so your reminders and statements keep arriving.

DMARC Policy: How to Move from p=none to p=reject Safely
A step-by-step DMARC rollout: what alignment means, how to read a record, and how to go from p=none to quarantine and reject without losing a single legitimate email.

DKIM Setup Explained: How It Works and Common Errors
DKIM in plain language: what the signature, selector and public key do, how to publish the record correctly, and how to fix the DNS mistakes that make DKIM fail.

Client Contact Hygiene: Keep Payment Reminders Out of Spam
Outdated addresses and typos quietly push your payment reminders toward spam and leave clients uninformed. How to keep your client contact data clean, step by step, every month.