tool / mx
MX Lookup
Mail servers and priorities for a domain.
try
Real resolvers
Every gap labelled.
Each result shows its source and what was not tested.
How MX Lookup works
MX records tell other mail servers where to deliver email for a domain. An MX lookup shows those servers in priority order, with their IP addresses.
Enter the domain part of the email address, for example example.com.
Read the list. The lowest priority number is tried first.
Check that every host resolves to an IP address.
Troubleshooting & Remediation
How to Read & Fix Results
How to read the result
- ProblemNo MX record, or an MX host that does not resolve to an IP. Mail to the domain will bounce or be delayed.
- WarningOnly one MX, or hosts with equal priority that you did not intend.
- PassAt least one MX, each host resolves, and the lowest priority number points at your real mail provider.
How to fix issues
- 1Get the exact MX hostnames from your mail provider. Do not guess them.
- 2In your DNS host, remove old MX records first, then add the provider's.
- 3Set the priorities the provider gives you. The lowest number is tried first.
- 4Run this check again and send a test message from an outside account.
Common mistakes to avoid
- •Leaving the old provider's MX records next to the new ones, so mail splits between two systems.
- •Pointing MX at an IP address. MX must name a host.
- •Pointing MX at a CNAME. Many servers reject it.
Example MX Records
10 mail1.example.net. 20 mail2.example.net.
We query the domain's MX records through public DNS, then look up each host's address. Delivery itself is not tested.
Next checks:Check SPF, DKIM and DMARCCheck blacklistsTest a real message
Specifications & Scope
About MX Lookup
- 01 / What it does
- MX records tell other mail servers where to deliver email for a domain. An MX lookup shows those servers in priority order, with their IP addresses.
- 02 / How to use
- 1. Enter the domain part of the email address, for example example.com. 2. Read the list. The lowest priority number is tried first. 3. Check that every host resolves to an IP address.
- 03 / Good to know
- A domain with no MX record usually cannot receive mail. A single MX with the value "." means the domain says it accepts no mail on purpose.
Got Questions?
Frequently Asked Questions
Knowledge Base
Technical Guides & Reference
Explore More
More in Domain & Email
Tool Details & Usage Guide
RFC specifications, input expectations, outputs, and edge limitations.
MX record lookup guide
An MX (Mail Exchange) record tells other mail servers where to deliver email for a domain. This tool asks public DNS resolvers for the MX records a domain currently publishes and lists each mail server with its priority.
Supported inputs
- Domain name, for example
example.com. Use the part after the @ in an email address, not a full URL.
How to read the output
- Priority (preference): A lower number is tried first. A server with priority 10 is tried before one with priority 20. Equal numbers share the load.
- Mail server host name: Must be a host name with its own A or AAAA record. An MX target should not be an IP address and should not point to a CNAME.
- Several records: Normal. The extra ones are backups or part of a hosted mail provider’s set.
Common problems
- No MX records: Senders may fall back to the domain’s A record, but most domains that want email should publish MX records explicitly. A domain that never receives mail can publish a “null MX” (a single record with priority 0 and a dot as the target, RFC 7505).
- MX points to a name that does not resolve: Mail bounces or is delayed. Check that the target host has an A or AAAA record.
- Records changed but old ones still show: Resolvers cache answers for the record’s TTL. Wait for the old TTL to expire before assuming the change failed.
- Mixed providers: MX records from two different mail providers at the same priority can split mail between them. Keep only the provider you use.
Limits
- This tool reads DNS only. It does not connect to the mail servers, so it cannot tell whether a listed server is online or accepting mail.
- Related checks: SPF, DKIM and DMARC records control who may send as your domain, and are checked separately in the Full Audit.
Recommended Troubleshooting Deep Dives
Authoritative SRE implementation tutorials related to this tool.
Reading Raw Email Headers in Outlook Web App: A Step‑by‑Step Guide
When a message lands in your inbox, most of its journey is hidden from view. The raw email header is the “passport” that records every hop, verification check, ...
Read guideDetecting Email Spoofing with DMARC Reports
Email spoofing is the digital equivalent of a forged signature—attackers send messages that appear to come from a trusted domain, hoping recipients will click a...
Read guideHow to Configure DKIM for Zendesk Email
Configuring DKIM (DomainKeys Identified Mail) for your Zendesk email ensures that messages sent from support agents land in inboxes, not spam folders. Below is ...
Read guideRelated tools
View all toolsSpam Checker
Free email deliverability test. Check SPF, DMARC, MX and blacklist signals for your sending domain and get fix steps for each issue.
DMARC Analyzer
Free DMARC checker. Read the DMARC record at _dmarc for any domain, see the policy (none, quarantine, reject) and what to fix to stop email spoofing.
BIMI Checker
Free BIMI checker. Check the BIMI record, logo URL and whether your DMARC policy meets the requirement for showing a brand logo in the inbox.