DNS Lookup (All Records)

Check the DNS records of any domain live. Enter a domain, pick a record type — A, AAAA, MX, NS, TXT, CNAME, SOA or CAA — and see the matching records with their TTLs. The lookup queries a public DNS resolver over a secure connection straight from your browser. Results may be cached, so a TTL is shown for each record.

Read the guide: How to Do a DNS Lookup
Choose a record type and look up any domain to see its live DNS records over a secure connection. Values come from a public resolver and may be cached.

How it works

  1. 1

    Enter a domain

    Type the domain you want to inspect, such as example.com. You can paste a full URL and the host is taken automatically.

  2. 2

    Pick the record type

    Choose A for IPv4, AAAA for IPv6, MX for mail, NS for name servers, TXT for text records, CNAME, SOA or CAA. The default is A.

  3. 3

    Read the records

    Press Look up to query a public resolver. Each matching record shows its data and TTL, the number of seconds the answer can be cached.

Instant & 100% private — nothing is uploaded

Everything runs locally in your browser. Your code, text and files are processed on your own device and are never sent to a server — so there are no upload waits, no size limits from us, and nothing is ever stored or logged.

Frequently asked questions

Which DNS records can I look up?
A and AAAA for IPv4 and IPv6 addresses, MX for mail servers, NS for name servers, TXT for text records such as SPF, CNAME for aliases, SOA for the zone start-of-authority, and CAA for certificate-authority authorization. Pick the type from the menu before you look up.
Why does the TTL matter?
The TTL (time to live) is how many seconds a resolver is allowed to cache the answer. A result you see may be a cached copy rather than the live record, so after a change you may keep seeing the old value until the TTL expires. Lower the TTL before a planned change to shorten that window.
Does this need an internet connection?
Yes. Unlike the calculators on this site, a DNS lookup has to ask a name server, so it queries a public resolver over a secure connection from your browser. It will not work offline. Nothing is logged on our side; the request goes straight to the public resolver.