DNS Lookup

Query A, AAAA, MX, TXT, and NS records for any domain in one lookup.

An IP address does a reverse (PTR) lookup
Quick presets

Look up any DNS record

Enter a domain to see its A, AAAA, CNAME, MX, TXT, NS, SOA and CAA records with real TTLs, DNSSEC status and a propagation check across public resolvers. Enter an IP address for a reverse lookup.

About the dns lookup

Look up the A, AAAA, MX, TXT, NS and CNAME records of any domain in one query. It works like nslookup or dig, but in the browser, and shows the TTL of every record so you know how long a change takes to spread.

Also searched as: DNS record checker · DNS checker · nslookup online · dig online · DNS resolver test · DNS records lookup · A record lookup · TXT record lookup

Which record answers which question

A and AAAA records map a name to an IPv4 or IPv6 address. MX records say which servers accept mail and in which priority order. TXT records carry text such as SPF and domain-verification tokens. NS records name the authoritative servers for the zone, and a CNAME makes one name an alias of another.

Reading the TTL

The time to live is how long resolvers may cache an answer. If you lower a TTL before a migration, wait for the old TTL to expire before changing the record; otherwise some users keep the old address for hours.

Troubleshooting with DNS

When a site or mailbox stops working, compare what you expect with what the lookup returns: a missing AAAA record, a CNAME at the zone apex, an MX that points to an IP address, or nameservers that disagree with the registrar are the usual causes.

How this tool works and how to read the results

What this tool does

Queries a domain's DNS records — A, AAAA, MX, TXT, NS, and CNAME — and returns everything currently published, all in one lookup instead of running separate queries for each record type.

When you'd use this

Confirming a DNS change has actually taken effect, verifying a new server's IP is correctly published before cutting over traffic, checking that a domain's mail routing (MX) and verification (TXT) records are set up as expected, or simply auditing what's publicly published for a domain you manage.

Why results can lag a recent change

DNS records are cached for the duration of their TTL (time-to-live) by resolvers between you and the authoritative nameservers. A record with a 3600-second TTL can take up to an hour to be consistently visible everywhere after a change, even though the authoritative server itself already has the new value — this is normal DNS propagation, not a sign the change failed.

Frequently asked questions

Why does this show different results than my local `nslookup`?

Your local resolver may have a cached (stale) answer from before a recent change. This tool queries fresh each time, so it reflects the current published records rather than a locally cached copy.

Why do I see multiple IP addresses for one A record?

That's round-robin DNS — the domain is intentionally pointed at several servers for load balancing or redundancy, and different queries may return them in a different order.

Why is the TTL not what I expected?

TTL controls how long resolvers are allowed to cache a record before re-checking it. If it was recently lowered (common right before a migration) or raised, what you see now reflects that change, not an error in the lookup.

Is this the same as nslookup or dig?

It asks the same question and shows the same records. nslookup and dig run on your computer and use your resolver; this tool queries from our server, so you see what the internet sees.

How long does DNS propagation take?

Up to the TTL of the old record, and sometimes longer for resolvers that ignore low TTLs. The TTL shown next to each record tells you how long it may stay cached.

Why does my domain have no AAAA record?

AAAA records are only needed if the server has an IPv6 address. Without one, the site works over IPv4 only, which is common and not an error.

Can I check TXT records for SPF and verification?

Yes. The TXT results list every text record, including SPF policies and tokens used by Google, Microsoft and other services to verify domain ownership.