You don't have javascript enabled. Please enable javascript to use this website.
MX Lookup

MX Lookup

Check MX records of a given domain (Using Forward DNS Lookup)
     

You might also be interested in:

CNAME Lookup
MX Lookup
NS Lookup
SPF Lookup
TXT Lookup
DNS Lookup

What is an MX Record ?

An MX (Mail Exchange) record is a type of DNS (Domain Name System) record that specifies which mail server is responsible for accepting email messages on behalf of a domain. The MX record is used by other mail servers to determine where to send email messages addressed to a particular domain.

For example, if someone sends an email to [email protected], the email server will look up the MX record for example.com to determine where to deliver the email message. The MX record will typically specify the hostname of the mail server that is responsible for handling email messages for the example.com domain.

Multiple MX records can be specified for a single domain, with each record having a priority value indicating the order in which mail servers should be contacted. In the event that the primary mail server is unavailable or does not respond, the mail server will attempt to deliver the email to the next server in the priority list.

MX records are an essential component of the email infrastructure and are used by all email servers to deliver email messages between domains. Without MX records, email messages would not be able to be routed to the correct mail server for delivery.


What is an MX-Records-Lookup Tool ?

An MX-Records-Lookup Tool is an online utility that allows you to query the Domain Name System (DNS) for the MX (Mail Exchange) records associated with a domain. The tool will provide you with a list of mail servers that are responsible for accepting email messages on behalf of the domain.

To use an MX-Records-Lookup Tool, you simply enter the domain name for which you want to query the MX records, and the tool will retrieve the MX records from the DNS and display them in a readable format. The tool may also display additional information about each mail server, such as its IP address, priority value, and other DNS records associated with the server.

MX-Records-Lookup Tools are commonly used by system administrators, email marketers, and other IT professionals to troubleshoot email delivery issues, verify that mail servers are properly configured, and identify potential security issues. By using an MX-Records-Lookup Tool, you can quickly and easily obtain important information about the email infrastructure associated with a domain, which can help you diagnose and resolve issues related to email delivery.


What can an MX-Records-Lookup Tool be used for ?

CNAME Records Lookup Tools can be useful for a variety of purposes, including:

  1. Troubleshooting Email Delivery Issues: An MX-Records-Lookup Tool can be used to identify and troubleshoot email delivery issues. By querying the DNS for the MX records associated with a domain, you can verify that the mail servers responsible for handling email messages are configured correctly and are reachable.

  2. Verifying Email Authentication: MX-Records-Lookup Tools can be used to verify that email messages are being sent from authorized servers. By checking the DNS for SPF (Sender Policy Framework) and DKIM (DomainKeys Identified Mail) records associated with the mail server, you can ensure that the server is authorized to send email messages on behalf of the domain.

  3. Identifying Spamming Sources: An MX-Records-Lookup Tool can be used to identify sources of spam or other malicious email messages. By analyzing the MX records associated with a domain, you can identify any suspicious or unauthorized mail servers that may be sending unsolicited email messages.

  4. Diagnosing DNS Issues: An MX-Records-Lookup Tool can be used to diagnose DNS issues related to a domain. By querying the DNS for the MX records associated with a domain, you can verify that the domain is properly configured and that its DNS records are up-to-date.

  5. Identifying Email Routing Issues: An MX-Records-Lookup Tool can be used to identify issues related to email routing. By analyzing the MX records associated with a domain, you can determine whether email messages are being delivered to the correct mail servers and whether any routing issues are present.

  6. Verifying Email Server Configuration: An MX-Records-Lookup Tool can be used to verify that email servers are properly configured. By checking the MX records associated with a domain, you can verify that the mail servers are configured with the correct settings, such as priority values and IP addresses.

  7. Analyzing Email Delivery Times: An MX-Records-Lookup Tool can be used to analyze email delivery times. By querying the DNS for the MX records associated with a domain, you can identify any bottlenecks or delays in the email delivery process.

  8. Monitoring Email Delivery: An MX-Records-Lookup Tool can be used to monitor email delivery for a domain. By regularly querying the DNS for the MX records associated with a domain, you can monitor changes in the email infrastructure and identify any issues that may arise.

  9. Investigating Email Spoofing: An MX-Records-Lookup Tool can be used to investigate email spoofing. By analyzing the MX records associated with a domain, you can identify any unauthorized mail servers that may be attempting to spoof email messages from the domain.

  10. Verifying Third-Party Email Services: An MX-Records-Lookup Tool can be used to verify third-party email services. By checking the MX records associated with a domain, you can verify that the third-party email service is properly configured and is authorized to send email messages on behalf of the domain.


List of Commonly Used DNS Record types:


TypeDescriptionFunction
A IPv4 Address record Returns a 32-bit IPv4 address, most commonly used to map hostnames to an IP address of the host, but it is also used for DNSBLs, storing subnet masks in RFC 1101, etc.
AAAA IPv6 address record Returns a 128-bit IPv6 address, most commonly used to map hostnames to an IP address of the host.
AFSDB AFS database record Location of database servers of an AFS cell. This record is commonly used by AFS clients to contact AFS cells outside their local domain. A subtype of this record is used by the obsolete DCE/DFS file system.
APL APL
CAA Certification Authority Authorization DNS Certification Authority Authorization, constraining acceptable CAs for a host/domain
CERT Certificate record Stores PKIX, SPKI, PGP, etc.
CNAME Canonical name record Alias of one name to another: the DNS lookup will continue by retrying the lookup with the new name.
DHCID DHCP identifier Used in conjunction with the FQDN option to DHCP
DNAME Delegation name record Alias for a name and all its subnames, unlike CNAME, which is an alias for only the exact name. Like a CNAME record, the DNS lookup will continue by retrying the lookup with the new name.
DNSKEY DNS Key record The key record used in DNSSEC. Uses the same format as the KEY record.
DS Delegation signer The record used to identify the DNSSEC signing key of a delegated zone
IPSECKEY IPsec Key Key record that can be used with IPsec
LOC Location record Specifies a geographical location associated with a domain name
MX Mail exchange record Maps a domain name to a list of message transfer agents for that domain
NAPTR Naming Authority Pointer Allows regular-expression-based rewriting of domain names which can then be used as URIs, further domain names to lookups, etc.
NS Name server record Delegates a DNS zone to use the given authoritative name servers
NSEC Next Secure record Part of DNSSEC—used to prove a name does not exist. Uses the same format as the (obsolete) NXT record.
NSEC3 Next Secure record version 3 An extension to DNSSEC that allows proof of nonexistence for a name without permitting zonewalking
NSEC3PARAM NSEC3 parameters Parameter record for use with NSEC3
PTR PTR Resource Record Pointer to a canonical name. Unlike a CNAME, DNS processing stops and just the name is returned. The most common use is for implementing reverse DNS lookups, but other uses include such things as DNS-SD.
RP Responsible Person Information about the responsible person(s) for the domain. Usually an email address with the @ replaced by a .
RRSIG DNSSEC signature Signature for a DNSSEC-secured record set. Uses the same format as the SIG record.
SOA Start of [a zone of] authority record Specifies authoritative information about a DNS zone, including the primary name server, the email of the domain administrator, the domain serial number, and several timers relating to refreshing the zone.
SRV Service locator Generalized service location record, used for newer protocols instead of creating protocol-specific records such as MX.
SSHFP SSH Public Key Fingerprint Resource record for publishing SSH public host key fingerprints in the DNS System, in order to aid in verifying the authenticity of the host. RFC 6594 defines ECC SSH keys and SHA-256 hashes. See the IANA SSHFP RR parameters registry for details.
TLSA TLSA certificate association A record for DANE. RFC 6698 defines "The TLSA DNS resource record is used to associate a TLS server certificate or public key with the domain name where the record is found, thus forming a 'TLSA certificate association'".
TSIG Transaction Signature Can be used to authenticate dynamic updates as coming from an approved client, or to authenticate responses as coming from an approved recursive name server[13] similar to DNSSEC.
TXT Text record Originally for arbitrary human-readable text in a DNS record. Since the early 1990s, however, this record more often carries machine-readable data, such as specified by RFC 1464, opportunistic encryption, Sender Policy Framework, DKIM, DMARC, DNS-SD, etc.
URI Uniform Resource Identifier Can be used for publishing mappings from hostnames to URIs.