DNS lookup
Query any DNS record for a domain — A, AAAA, MX, TXT, NS, SOA, CNAME, CAA and more — through two independent public resolvers at once, so you can see whether they agree and whether a recent change has propagated.
Look up DNS records
Enter a domain, pick a record type (or all common) and press Look up. Each answer shows the record data, its TTL and which resolver returned it (Cloudflare 1.1.1.1 and Google 8.8.8.8 over DNS over HTTPS); a difference between the two is highlighted.
Record types explained
Each record type answers a different question about a domain.
A and AAAA
The IPv4 (A) and IPv6 (AAAA) addresses a hostname points to. A site with no AAAA record is not reachable over IPv6.
MX
The mail servers that accept email for the domain, with priorities; the lowest number is tried first.
TXT (SPF, DKIM, DMARC)
Free-form text used for verification and mail authentication: SPF (v=spf1 …) lists senders allowed to use the domain, DKIM selectors publish signing keys, DMARC (_dmarc. subdomain) says what to do with mail that fails both.
NS and SOA
NS records name the authoritative nameservers; the SOA record holds the zone's serial number and timers, useful for checking whether all nameservers serve the same version.
CNAME
An alias: the name is another name, and the resolver follows it. A CNAME cannot coexist with other records at the same name, which is why the apex of a domain cannot be a CNAME.
CAA
Which certificate authorities may issue certificates for the domain. Missing means any CA may.
nslookup vs dig
nslookup (Windows, also on macOS/Linux) and dig (macOS/Linux, BIND tools) query DNS from the command line; dig example.com MX +short is the equivalent of an MX lookup here. Both ask your configured resolver unless you name one (dig @1.1.1.1 …).
DNS propagation
After you change a record, resolvers around the world keep serving the old answer until its TTL expires; there is no central push. Comparing two resolvers here shows whether the change has reached them; an authoritative lookup (directly at the domain's nameservers) shows what will be served once caches expire. If one resolver still shows the old value, wait for the old TTL — which is why lowering the TTL a day before a planned change is good practice.
How DNS lookup works
A lookup starts at your resolver, which asks a root server for the top-level domain's nameservers, then those for the domain's nameservers, then those for the record itself, caching each step for its TTL. This page skips your resolver and asks two public ones directly, which is why its answers can differ from what your own device sees — the what is my DNS server page shows which resolver that is, and the DNS leak test shows where your queries actually go.
Frequently asked questions
Why would you perform a DNS lookup?
To check whether a domain's records are set correctly (after moving a site or configuring email), to see whether a change has propagated, to find a domain's mail servers or nameservers, or to diagnose why a site or email does not work.
How does DNS work step by step?
Your device asks its resolver; the resolver asks a root server which nameservers handle the top-level domain, asks those which nameservers handle the domain, asks those for the record, caches everything for the TTL and returns the answer. Later lookups are served from cache until the TTL expires.
Does DNS lookup use TCP or UDP?
Mostly UDP on port 53 for speed; TCP when an answer is too large for one UDP packet (zone transfers, large record sets, DNSSEC) or when the resolver chooses it. Encrypted DNS (DoH, DoT) runs over TCP/TLS.
What is the main purpose of nslookup?
To query DNS records from the command line and to check which resolver answered — the same job as this page, for any record type and any server.
What replaced nslookup?
dig (and delv for DNSSEC) in the BIND tools; on Windows, PowerShell's Resolve-DnsName. nslookup still ships everywhere and is fine for simple lookups.
Can I nslookup an IP address?
Yes — nslookup 203.0.113.42 performs a reverse lookup and returns the PTR hostname for the address, if one exists. The reverse DNS lookup page does the same.
Two independent public resolvers are asked and their answers compared record by record (TTL and order ignored); the TTL shown is the resolver's remaining cache time, not the zone's. Find a website's IP