Use our MX Record Lookup tool to check which mail servers a domain lists for receiving email. Enter a domain name to retrieve its publicly available Mail Exchange (MX) records, including server hostnames, priority values, and reported DNS Time to Live (TTL).
This lookup helps website owners, email administrators, and domain managers investigate email routing configurations without accessing their hosting control panel.
Check which mail servers a domain advertises for receiving email. View MX priorities, server hostnames and reported DNS TTLs. The domain you enter is sent to this website's server for the lookup. Results may be cached briefly. Hosting and DNS-provider logging policies may apply.MX Record Lookup
How to Check MX Records for Any Domain
Checking a domain’s MX records takes a few simple steps:
- Enter your domain name. Type a domain such as
example.cominto the lookup field. Do not includehttps://, a webpage path, or an email address. - Click Look Up MX Records. The tool requests the domain’s MX records using the website server’s configured DNS resolver.
- Review the results. Check the mail server hostnames, priority values, and available TTL information.
- Compare the records. If you are investigating an email setup problem, compare the results with the MX settings supplied by your email hosting provider.
You can also copy the returned records for reference or troubleshooting.
What Is an MX Record?
An MX (Mail Exchange) record is a type of Domain Name System (DNS) record that identifies the servers designated to receive email for a domain.
For example, when someone sends a message to contact@example.com, the sending mail system can query the MX records for example.com to find the mail servers responsible for handling incoming messages.
A domain can have one or several MX records. Each record contains a mail server hostname and a numerical preference value that helps sending servers determine which destination to try first.
MX records are primarily concerned with incoming email routing. They do not prove that a particular mailbox exists or that the receiving server will accept a message.
Understanding Your MX Lookup Results
The lookup displays several pieces of DNS information. Knowing what each field means makes it easier to identify incorrect or unexpected settings.
MX Priority
MX priority, also called preference, determines the order in which sending mail servers should consider available mail exchangers.
A lower number indicates a higher preference. For example, an MX record with priority 10 is preferred over one with priority 20.
If two mail servers have the same priority, they have equal preference. Sending mail systems may distribute attempts between them according to SMTP rules.
A higher numerical priority is not necessarily an error. Multiple records can be part of a properly configured email service.
Mail Server Hostname
The mail server hostname identifies the destination advertised for incoming email.
For example, a domain might be configured to use a hostname such as mail.example.com.
This hostname should correspond to the configuration supplied by the domain’s email provider. However, the presence of an MX hostname does not establish whether the underlying mail server is reachable or working correctly.
TTL (Time to Live)
TTL is the period, measured in seconds, associated with caching DNS information.
A higher configured TTL generally allows DNS resolvers to retain information longer, while a lower TTL can permit cached information to expire sooner.
The TTL displayed by this tool comes from the DNS response available to the website’s server. It may represent the remaining lifetime of cached information rather than the original TTL configured by the domain owner.
TTL is not an exact countdown to worldwide DNS propagation.
What Do Different MX Lookup Results Mean?
MX Records Found
The domain has returned one or more MX records.
Review the listed mail server hostnames and priorities. If they match your email provider’s current configuration, the published records may be correct.
However, finding MX records does not confirm that the receiving servers are available or that email delivery will succeed.
No MX Records Returned
The lookup did not receive MX records for the requested domain.
This does not automatically mean that the domain cannot receive email. Under SMTP rules, delivery may fall back to the domain’s IPv4 or IPv6 address records (A or AAAA) when no MX records exist.
An empty result also does not establish whether a domain exists or whether its DNS configuration is otherwise healthy. Further DNS checks may be needed.
Null MX Detected
A Null MX record tells sending mail systems that a domain does not accept incoming email.
Its special configuration uses priority 0 and an exchange value of . (a single dot).
This arrangement is defined by RFC 7505 and can be appropriate for domains intentionally configured not to receive email.
Configuration Warning
If the lookup reports a Null MX alongside ordinary MX records, the domain’s configuration needs attention.
The Null MX standard requires a domain using this declaration not to publish other MX records at the same name.
A domain administrator should review the authoritative DNS configuration and correct conflicting entries.
How to Fix MX Record Problems
If your domain is supposed to receive email but its MX records are missing, outdated, or unexpected, start with the following checks.
1. Verify Your Email Provider’s Settings
Open your email hosting provider’s official configuration instructions and identify the required MX destinations and preference values.
Do not assume that the same MX settings apply to all domains or hosting packages.
2. Check Your Domain’s DNS Management Panel
Sign in to the control panel where your domain’s authoritative DNS records are managed.
This may be your domain registrar, hosting company, or another DNS provider.
Locate the MX records and compare them with your email provider’s requirements.
3. Review Old or Conflicting Records
If you recently changed email providers, check for obsolete MX records pointing to the previous service.
Do not delete records merely because multiple entries appear. Some email providers intentionally use more than one mail exchanger.
Make changes only after confirming the required configuration.
4. Allow DNS Caches to Update
After saving MX changes, DNS resolvers may continue returning cached responses until their relevant caching periods expire.
Run another lookup after an appropriate interval. If records still appear incorrect, inspect the authoritative DNS settings and consult your provider.
5. Investigate Email Delivery Separately
Correct-looking MX records are only one part of email delivery.
If incoming messages are still failing, the problem may involve server availability, mailbox configuration, recipient restrictions, or other email service settings.
An MX lookup cannot identify all these problems.
MX Records vs Other DNS Records
Different DNS records have different responsibilities in an email system.
| Record | Main purpose |
|---|---|
| MX | Identifies incoming mail exchange servers |
| A / AAAA | Maps hostnames to IPv4 or IPv6 addresses |
| SPF | Identifies authorized sending sources through a DNS TXT record |
| DKIM | Publishes information used to verify cryptographic email signatures |
| DMARC | Publishes domain-level email authentication policy and reporting instructions |
MX records do not replace SPF, DKIM, or DMARC. Likewise, a valid SPF or DKIM configuration does not guarantee that incoming mail routing is correct.
How Our MX Record Lookup Works
The tool performs a server-side DNS query for the domain entered by the visitor.
The domain name is submitted to NetTools Pakistan’s website server, which uses its configured DNS resolver to request MX records. The returned information is organized into a table showing available server hostnames, priorities, and TTL values.
Results can be cached briefly to avoid unnecessary repeated queries. Consequently, a repeated lookup may show a recent cached result rather than a new DNS query.
The tool does not connect to your mailbox, send a test email, verify an email address, or attempt an SMTP delivery session. It also does not directly compare multiple public DNS resolvers or authoritative name servers.
Privacy and Data Handling
MX records are publicly accessible DNS information, but the domain name you submit is processed by the website server and its configured DNS resolver.
The tool uses temporary caching and basic request-rate limiting. Website hosting infrastructure, security services, or DNS resolvers may maintain their own operational logs.
Do not enter passwords or other confidential information. Only a domain name is required.
Common Questions About MX Records
Can I check MX records without logging in to my domain?
Yes. Public MX records can be queried without access to the domain’s administration panel. Changing those records, however, requires appropriate DNS management access.
Can a domain have multiple MX records?
Yes. A domain may publish multiple mail exchange records, including records with different or equal preference values. Whether those entries are correct depends on the email provider’s configuration.
Does an MX record confirm that email is working?
No. MX records identify advertised mail destinations. They do not verify mailbox existence, SMTP connectivity, server health, or successful delivery.
Why does my MX lookup show old records?
A DNS resolver may temporarily return cached information after records have changed. The domain’s authoritative DNS settings could also still contain the old entries. Check both before making further changes.
Technical References
The explanations on this page are based on established DNS and SMTP documentation:
- RFC 5321 – Simple Mail Transfer Protocol
- RFC 7505 – Null MX Records
- PHP DNS Record Lookup Documentation