The DNS lookup tool queries global nameservers to retrieve all active Domain Name System records associated with any given domain name. It displays configuration data in one centralized view to help you understand how a domain routes traffic and handles mail delivery.
What is it
A DNS lookup is the process of querying the Domain Name System to find the technical records assigned to a domain. Think of the DNS as the phonebook of the internet, translating human-friendly domain names like example.com into machine-readable IP addresses. When you run a DNS lookup, you are asking authoritative and recursive nameservers for a complete inventory of the instructions they hold for that domain.
Every domain relies on a collection of different record types to function properly. 'A' records point a domain to an IPv4 address, while 'AAAA' records point to IPv6 addresses. Mail Exchange ('MX') records direct incoming emails to the correct mail servers. Text ('TXT') records store arbitrary data used for security frameworks like SPF, DKIM, and DMARC. Canonical Name ('CNAME') records alias one name to another. Start of Authority ('SOA') records define administrative details about the zone, and Name Server ('NS') records declare which servers hold the authoritative data for the zone. Finally, Certification Authority Authorization ('CAA') records specify which certificate authorities are permitted to issue SSL certificates for the domain.
Why it matters
Website owners and IT administrators rely on DNS lookups daily to diagnose connectivity failures, verify domain migrations, and maintain security configurations. If your website is unreachable or your emails are bouncing, the root cause is frequently a misconfigured DNS record. By inspecting these records directly, you can bypass local browser caching and see the exact instructions the rest of the internet receives when trying to reach your infrastructure.
Furthermore, proper DNS management is critical for domain security and brand protection. Checking your TXT and CAA records ensures that malicious actors cannot spoof your email identity or request unauthorized SSL certificates for your domains. Routine DNS audits help you catch stale records left over from previous hosting providers, reducing your attack surface and preventing routing loops before they impact your visitors.
How to use this tool
- Locate the input field on the DNS lookup tool interface.
- Enter the target domain name you wish to inspect, such as
example.com(do not include http:// or https:// prefixes). - Click the Check button to initiate the query across multiple global nameservers.
- Review the generated list of DNS records displayed on your screen to analyze the current configuration.
How to read the results
The results page displays all discovered DNS records grouped by their record type, complete with Time to Live (TTL) values and target destinations. For example, when inspecting example.com, you might see an 'A' record pointing to 93.184.216.34 with a TTL of 3600, indicating that resolvers can cache this IP address for one hour. You will also see 'MX' records showing preference numbers, such as 10 mail.example.com, which tells sending mail servers the priority order for delivery attempts. TXT records will display string values like v=spf1 include:_spf.google.com ~all, confirming the authorized mail senders for the domain. NS records will list nameservers such as a.iana-servers.net, and SOA records will show the primary nameserver, administrator email, and serial numbers necessary for zone synchronization.
Common problems and how to fix them
Missing or Incorrect A Records
If your website fails to load and returns a server not found error, your A record may be missing or pointing to an old IP address. Log into your DNS provider, locate the root A record, and update the destination value to your current hosting provider's IPv4 address.
@ 3600 IN A 192.0.2.1
Conflicting CNAME and Apex Records
Attempting to create a CNAME record at the root or apex of your domain (e.g., example.com) violates DNS standards and breaks web traffic. Replace the apex CNAME with an A record, or use an alias record type supported by your DNS host.
Broken Mail Delivery Due to Faulty MX Records
If incoming emails are failing, your MX records might reference a hostname that lacks a valid A record. Ensure your MX records point to valid hostnames that resolve correctly to active mail servers.
@ 3600 IN MX 10 mail.example.com.
Best practices
Always set appropriate TTL values before making major DNS changes. Lower the TTL to 300 seconds a day prior to a migration so resolvers pull fresh records quickly, and raise it back to 86400 seconds afterward to reduce query load. Regularly audit your TXT records to remove obsolete verification tokens from services you no longer use, and ensure your DNS provider uses DNSSEC to protect your zone data from cache poisoning attacks.