Article Summary: This guide explains what DNS records are, covers every major record type with practical examples, and shows how the DNS Record Lookup tool retrieves live data from authoritative nameservers without needing to install dig or nslookup. Whether you are troubleshooting email delivery, verifying a domain migration, or auditing a zone file, this reference has you covered.
What Is DNS Record Lookup?
The Domain Name System (DNS) is the internet's distributed directory service, translating human-readable domain names like example.com into the IP addresses and server instructions that computers actually use. Every domain has a zone file stored on its authoritative nameservers, and that zone file contains a set of DNS resource records that define exactly how the domain behaves.
A DNS record lookup is the act of querying those authoritative nameservers to retrieve one or more of those resource records. Administrators use lookups to verify configuration changes, diagnose delivery problems, and audit a domain's overall DNS health. Traditionally this required command-line tools like dig (on Linux/macOS) or nslookup (on Windows). This tool provides the same authoritative data through a simple web interface, with no software to install.
How It Works
The DNS Resolution Chain
When you enter a domain and click Lookup, the tool sends a DNS query directly to the domain's authoritative nameservers. This bypasses any caching resolver, which means you always see the current, live record values rather than stale cached data. The response includes the record's value, its type, and its TTL — the number of seconds downstream resolvers are allowed to cache it.
Reading TTL Values
The Time to Live (TTL) on each DNS record governs propagation speed. A record with a TTL of 300 seconds (5 minutes) will be refreshed frequently by resolvers around the world, making changes propagate quickly. A TTL of 86400 seconds (24 hours) means resolvers can cache the old answer for up to a full day after you update it. Before making any DNS changes, especially a hosting migration, it is best practice to lower the TTL to 300 or less several hours in advance.
Querying All Record Types at Once
Unlike the command-line dig tool, which requires you to specify a record type for each query, this tool retrieves all common record types in a single pass: A, AAAA, MX, NS, TXT, CNAME, SOA, and more. Results are grouped by type for clarity, making it easy to get a complete picture of a domain's DNS configuration at a glance.
Common Use Cases
Verifying a New DNS Configuration
After Changing Hosting or Registrar
When you migrate a website to a new server or transfer a domain to a new registrar, you need to confirm that the A record now points to the correct IP address and the NS records reflect the new authoritative nameservers. A DNS record lookup lets you verify this instantly, without waiting for your local resolver's cache to expire.
Troubleshooting Email Delivery Problems
Checking MX, SPF, and DMARC Records
Email deliverability failures are almost always rooted in misconfigured DNS. Checking the MX record confirms where inbound email is being delivered. Inspecting the TXT record for v=spf1 verifies your SPF policy, while a TXT lookup on _dmarc.yourdomain.com reveals your DMARC policy. DKIM selectors are also stored as TXT records. Getting all of these right is essential for reaching the inbox rather than the spam folder.
Auditing Domain Ownership Verification Records
Google Search Console, SSL Issuance, and SaaS Platforms
Many platforms require you to add a specific TXT record to prove domain ownership before they grant access or issue an SSL certificate. After adding the record through your DNS provider, a DNS record lookup confirms the value is live and correctly formatted, saving you the frustration of a failed verification caused by a typo or propagation delay.
Investigating a Domain's Infrastructure
Security Research and Competitive Intelligence
The SOA record reveals the primary nameserver and the administrator's email address. NS records expose which DNS hosting provider a domain uses. MX records indicate the email platform in use, such as Google Workspace, Microsoft 365, or Proton Mail. Together, these records paint a detailed picture of a domain's technical infrastructure, useful for security researchers and IT professionals evaluating a domain before acquisition.
Technical Reference
| Type | Full Name | Purpose | Example Value |
|---|---|---|---|
| A | Address Record | Maps a domain to an IPv4 address | 93.184.216.34 |
| AAAA | IPv6 Address Record | Maps a domain to an IPv6 address | 2606:2800:220:1:248:1893:25c8:1946 |
| MX | Mail Exchanger | Specifies the mail server for inbound email | 10 mail.example.com |
| NS | Name Server | Delegates a zone to authoritative nameservers | ns1.cloudflare.com |
| TXT | Text Record | Stores arbitrary text; used for SPF, DKIM, DMARC, and verification tokens | v=spf1 include:_spf.google.com ~all |
| CNAME | Canonical Name | Aliases one domain name to another | www CNAME example.com |
| SOA | Start of Authority | Contains zone metadata: primary NS, admin email, serial, and refresh timers | ns1.example.com. admin.example.com. 2024010101 3600 900 604800 300 |
| PTR | Pointer Record | Maps an IP address back to a hostname (reverse DNS) | 34.216.184.93.in-addr.arpa PTR example.com |
| SRV | Service Record | Specifies host and port for specific services such as SIP or XMPP | _sip._tcp.example.com 10 20 5060 sip.example.com |
| CAA | Certification Authority Authorization | Restricts which certificate authorities may issue SSL/TLS certs for the domain | 0 issue "letsencrypt.org" |
Frequently Asked Questions
What is a DNS record?
A DNS record is a single entry in a domain's zone file stored on its authoritative nameservers. Each record has a type (such as A, MX, or TXT), a name (often the domain itself or a subdomain), a value (the data it holds), and a TTL. Together, the records in a zone file define how the domain resolves, where its email goes, what services it advertises, and who is authorized to issue certificates for it.
Why do I need to look up DNS records?
DNS misconfigurations are among the most common causes of website downtime, email delivery failure, and failed SSL certificate issuance. Looking up DNS records lets you verify that a change has taken effect, confirm that a third-party provider's instructions were followed correctly, or diagnose why something stopped working after a migration. It is an essential step in any DNS troubleshooting workflow.
What is TTL in DNS?
TTL (Time to Live) is the number of seconds a DNS resolver is permitted to cache a record before querying the authoritative nameserver again. A low TTL such as 60-300 seconds means changes propagate quickly but generate more query traffic. A high TTL such as 86400 seconds (24 hours) reduces query load but means that after a record change, the old value can persist in resolver caches worldwide for up to that many seconds.
How is this different from using dig or nslookup?
The dig command (Linux and macOS) and nslookup (Windows) are powerful command-line tools that query DNS. This tool provides equivalent functionality through a browser interface with no terminal, no flags to memorize, and no software installation required. Results are presented in a clean, readable table rather than raw text output. The underlying DNS queries are identical: both methods reach the same authoritative nameservers and return the same record data.
Conclusion and Takeaways
Understanding DNS records is a fundamental skill for anyone who manages a domain, runs a website, or administers email. The DNS Record Lookup tool removes the friction of the command line and gives you instant, authoritative answers about any domain's configuration. Whether you are checking an A record after a server migration, validating an SPF TXT record to fix email deliverability, or exploring a domain's infrastructure, this tool gives you the full picture in seconds.
Ready to Look Up DNS Records?
Use the DNS Record Lookup tool above — no login required, instant results from authoritative nameservers.