- Home
- Tools
- Network Tools
- DNS Lookup
DNS Lookup
Look up the A, AAAA, MX, TXT, NS and CNAME records of a domain.
What the record types are for
| Type | What it holds |
|---|---|
| A | The IPv4 address of a name |
| AAAA | The IPv6 address of a name |
| CNAME | Another name that this one is an alias of. A name with a CNAME has no other records |
| MX | The mail servers of a domain. The one with the lowest number is tried first |
| TXT | Text. In practice: SPF, DKIM and DMARC records, and codes that prove you own the domain |
| NS | The name servers in charge of the domain, which is where its DNS is really managed |
| SOA | Administrative details of the zone, such as its primary server and a serial number that goes up with every change |
| CAA | The certificate authorities that may issue certificates for the domain |
| PTR | The name that belongs to an IP address. Enter an address and the tool looks this up |
Mail records hide in TXT
SPF starts with v=spf1, lists the servers that may send mail for a domain and sits on the domain itself. The other two live elsewhere and need a lookup of their own: the DMARC policy at _dmarc.example.com, and DKIM keys at selector._domainkey.example.com, where the selector is the s= value in the DKIM-Signature header of a message.
A long record, such as a 2048-bit DKIM key, is stored as several strings of at most 255 bytes each. They are shown joined, which is how mail servers read them.
TTL, and why a change takes time
Every record carries a TTL, a number of seconds. Whoever looks the record up may keep the answer that long without asking again. The resolvers of internet providers do this, and so do browsers and operating systems.
That is all "DNS propagation" is. A change is normally live on the domain's own name servers within minutes. What takes time is caches all over the world running down the old TTL, each on its own clock. With a TTL of 3600 the last one catches up an hour later, and nothing can hurry it. That is why people lower the TTL a day or two before a planned move.
The TTL shown here is what is left in the resolver's cache, not the value set on the domain. Look the name up twice and you can watch it count down.
Who answers
A web page cannot send DNS queries itself, so the tool asks a public resolver over HTTPS: Cloudflare's (the service behind 1.1.1.1), or Google's (8.8.8.8) when Cloudflare cannot be reached. The request goes straight from your browser to them. It contains the name and the record type, and like any site you visit they see your IP address. Nothing passes through this website.
You get what those resolvers have, which is what most of the world sees. Your own computer may still hold an older answer, or use a provider that blocks certain names.
DNSSEC and the error codes
A domain that uses DNSSEC signs its records, so a resolver can check that an answer was not tampered with. "Validated" means that check was done and passed. "Not validated" nearly always means the domain is not signed.
- NXDOMAIN: the name does not exist at all.
- An empty answer: the name exists but has no record of that type. That is normal; most domains have no CAA record, for one.
- SERVFAIL: the resolver could not get a usable answer. The domain's name servers are unreachable or misconfigured, or its DNSSEC signatures are wrong.
A page for each kind of lookup
More network tools
All tools