DNS Lookup Tool
Query A, AAAA, CNAME, MX, TXT, NS, and SOA records for any domain.
Checking How a Domain Is Actually Configured
A domain not resolving correctly, an email not delivering, a website pointing to the wrong server — most of these trace back to DNS records, the system that maps human-readable domain names to the actual server addresses and configuration behind them. This tool queries a domain's A, AAAA, CNAME, MX, TXT, NS, and SOA records directly, showing exactly how that domain is currently configured.
What Each Record Type Actually Tells You
A records map a domain to an IPv4 address — where its website actually lives; AAAA records do the same for IPv6. CNAME records point one domain name to another as an alias, common for subdomains pointing to a hosting provider's infrastructure. MX records specify which mail servers handle email for that domain, in priority order — critical for diagnosing email delivery issues. TXT records hold arbitrary text data, frequently used for domain verification and email authentication (SPF, DKIM records live here). NS records list the domain's authoritative nameservers. SOA holds administrative metadata about the domain's DNS zone itself.
A Worked Example
Diagnosing why a company's email keeps landing in recipients' spam folders, checking the domain's TXT records often reveals a missing or misconfigured SPF record — a text entry that tells receiving mail servers which servers are authorized to send email on that domain's behalf. A domain lacking this record, or with an SPF record that doesn't include the actual email service being used, gives spam filters a legitimate reason to distrust the message, regardless of how well-written the email itself is.
Who Actually Needs to Check DNS Records
A developer troubleshooting why a newly pointed domain isn't loading the expected website, checking whether the A record actually points to the new server's IP. Someone setting up a business email service, verifying the MX records are correctly configured to route mail to the right provider. A security-conscious site owner checking their domain's SPF, DKIM, and DMARC TXT records to confirm email authentication is properly configured. Anyone buying a domain who wants to see who currently manages its nameservers before making changes.
Why DNS Changes Take Time to Show Up Everywhere
DNS records are cached at multiple points across the internet — your own device, your ISP's DNS resolver, and countless other resolvers worldwide — each with its own expiration time (TTL, or time-to-live) before it re-checks the authoritative source. This is why a DNS change made minutes ago might already show correctly in one lookup tool while still showing old data somewhere else; full global propagation typically takes anywhere from minutes to 48 hours depending on the record's configured TTL.
A Genuine DNS Query, Not a Local Calculation
Looking up a domain's DNS records requires an actual query to the DNS system itself — there's no way to know what a domain's current records are without asking, since DNS is inherently a distributed, queryable public system. This tool sends that query directly and displays the response, rather than processing anything locally, which is an inherent requirement of what DNS lookup fundamentally is.
Reading Results When Something Looks Wrong
An unexpectedly empty result for a record type usually means that record genuinely isn't configured for the domain, not a lookup failure — plenty of domains legitimately have no AAAA (IPv6) record, for instance, if they haven't set up IPv6 support. A result that looks outdated compared to a recent change is more likely explained by DNS caching and TTL delay than by an actual misconfiguration.
Why does this show different results than what I see in another DNS tool?
DNS caching across different resolvers can cause temporary discrepancies, especially right after a recent change — results generally converge once caches expire based on each record's TTL.
What does it mean if a domain has no MX record at all?
It typically means that domain isn't configured to receive email at all, which is common and expected for domains used purely for a website with no associated email service.
Is checking a domain's DNS records something anyone can do, or does it require special access?
DNS records are publicly published and queryable by design — anyone can look up any domain's public DNS records without needing special permission or ownership of that domain.
How long does a DNS change typically take to fully propagate?
It depends on the record's configured TTL, but full global propagation commonly ranges from a few minutes to up to 48 hours in some cases.
What's the difference between an A record and a CNAME record?
An A record points directly to an IP address; a CNAME points to another domain name instead, which itself then resolves to an IP — useful for subdomains that should follow wherever the target domain's own IP eventually points.