An MX record lookup queries the DNS mail exchange records for a domain to reveal which mail servers handle its incoming email. Use this tool to verify email configuration, identify your mail provider, and troubleshoot delivery issues — all via DNS over HTTPS.
MX Record Lookup
Enter any domain name (e.g., gmail.com, outlook.com)
Querying MX records via DNS over HTTPS...
| Priority | Mail Server | TTL | Provider | Copy |
|---|
No MX records found
This domain may not have email configured, or it may use a subdomain for mail.
How to Use the MX Record Lookup Tool
The MX record lookup tool queries DNS mail exchange records via Cloudflare's DNS over HTTPS (DoH) API. It fetches and displays the mail servers for any domain sorted by priority — so you immediately see which server handles email first.
Step 1: Enter the Domain
Type the domain you want to check in the input field — for example gmail.com or yourcompany.com. You can include the full URL — the tool will strip https://, www., and trailing slashes automatically.
Step 2: View Results
Results appear in a priority-sorted table showing: Priority (lower = higher preference), Mail Server hostname, TTL (cache duration in seconds), and detected provider if recognized. Common providers like Google Workspace, Microsoft 365, Zoho Mail, and ProtonMail are auto-detected.
Understanding MX Record Priority
MX records have a preference number that determines delivery order. A server with priority 10 is tried before one with priority 20. If priority 10 is unavailable, the sending server retries via priority 20. This failover mechanism ensures email reaches you even if your primary mail server is temporarily down.
Common Use Cases
- Email not receiving — verify MX records point to your mail provider
- Migrating email providers — confirm new MX records have propagated
- Security audit — check for unexpected mail servers in your MX records
- Email deliverability — ensure priority values are set correctly for redundancy
- Check a vendor's email setup — see which mail system they use before sending
Copy and Share Results
Use the Copy button next to each record to copy that mail server's details, or click "Copy All" to copy the complete MX record set as formatted text. Useful for documentation, support tickets, or sharing with your email provider.
FAQ
What is an MX record?
An MX (Mail Exchange) record is a DNS record that specifies which mail servers are responsible for accepting email for a domain. When someone sends email to user@example.com, the sender's mail server queries DNS for example.com's MX records to find out where to deliver the message. Without valid MX records, email delivery will fail.
What does MX record priority mean?
MX records have a priority number (also called preference). Lower numbers have higher priority — so priority 10 is tried before priority 20. This allows you to set primary and backup mail servers. If the priority 10 server is unavailable, mail will be delivered to the priority 20 server instead. Multiple records with the same priority receive mail in round-robin fashion.
How do I know which email provider is configured?
You can identify the email provider by the mail server hostnames in the MX records. Google Workspace uses servers ending in 'aspmx.l.google.com'. Microsoft 365 uses 'mail.protection.outlook.com'. Zoho uses 'mx.zoho.com'. Proton Mail uses 'mail.protonmail.ch'. This tool automatically detects these common providers and labels them.
Why might my domain have no MX records?
If a domain has no MX records, some mail servers will attempt to deliver email to the A record (the main IP address) as a fallback. This is unreliable and means email may not be delivered. If you're setting up email for a domain, you must add MX records pointing to your email provider's servers.
Is this MX lookup tool free?
Yes, this MX record lookup tool is completely free. It uses DNS over HTTPS via Cloudflare's public API to query records directly from your browser. No account or signup is required, and your lookups are not stored.
Is my lookup data private?
Your domain queries are sent to Cloudflare's public DNS over HTTPS API (1.1.1.1), which Cloudflare processes but does not permanently log individual queries per their privacy policy. No data is stored on our servers — the query goes directly from your browser to Cloudflare.