Sorted by priority — lower number = higher priority (tried first)
Your All‑In‑One Online Tool Hub
Instantly look up the mail server records for any domain. See hostnames, priority, resolved IP addresses, PTR reverse DNS, TTL, email provider detection, DMARC policy, and SPF record — all in one place.
Sorted by priority — lower number = higher priority (tried first)
An MX (Mail Exchange) record is a DNS record that tells the internet which mail servers are responsible for receiving email for a domain. Every domain that can receive email must have at least one MX record. Each MX record contains a priority number and a mail server hostname. Lower priority numbers are tried first — a server with priority 5 is contacted before one with priority 10.
The priority number determines which mail server is tried first when delivering email. Lower numbers have higher priority — a server with priority 5 is tried before one with priority 10. If two MX records share the same priority, the sending server picks one at random for load balancing. If the primary server is unavailable, email automatically routes to the next highest priority server, providing redundancy and failover.
TTL stands for Time to Live — the number of seconds other DNS servers are allowed to cache your MX record before re-checking. A TTL of 3600 means one hour. If you are planning to switch email providers or change your mail server, lower your TTL to 300 (5 minutes) at least 48 hours before making the change. This allows the update to propagate quickly once made.
A PTR record is a reverse DNS record — it maps an IP address back to a hostname. For mail servers, a missing or mismatched PTR record is a common reason emails get flagged as spam or rejected outright. Major email providers including Gmail and Microsoft 365 check that the sending mail server's IP has a valid PTR record that matches the mail server's hostname. This is called Forward-Confirmed Reverse DNS (FCrDNS).
DMARC (Domain-based Message Authentication, Reporting and Conformance) is an email authentication policy that tells receiving mail servers what to do with messages that fail SPF or DKIM checks. The three policy values are: none — monitor only, take no action on failures; quarantine — send failing messages to the spam folder; reject — block failing messages entirely and return them to sender. A policy of reject provides the strongest protection against email spoofing and phishing.
An SPF (Sender Policy Framework) record is a DNS TXT record that lists which mail servers are authorized to send email on behalf of your domain. It helps prevent spammers from spoofing your domain in the From address. An SPF record starts with v=spf1 and includes mechanisms such as include:, ip4:, and ends with -all (hard fail) or ~all (soft fail). A hard fail -all is more secure and tells receivers to reject any email that does not match the authorized senders.
If no MX records are found for a domain, it cannot receive email. This may mean the domain has no email service configured, the MX records were accidentally deleted during a DNS migration, or the domain is used purely for a website. Without MX records, sending servers fall back to the domain's A record per RFC 5321 — which typically points at a web server with no mail daemon, resulting in bounced messages.
Disclaimer: QuickITTools.com and EnterPlanet LLC strive to make our tools as accurate as possible. MX record data is retrieved in real time from DNS and is subject to propagation delays. Geolocation data for mail server IPs is sourced from ip-api.com and is an estimate only. Always verify critical email configuration independently.