ToolsDNS & domains

DNS lookup

Look up any record type for a domain, or the reverse name for an IP address. Ask one public resolver or compare all three.

Queries built and decoded in your browser
Sent via abbott.cloud to the resolver you choose

Query

Domain name or IP address

Record type

You can paste a full web address or email address; only the domain is used. An IP address, even in a web address or with a port, looks up its reverse (PTR) name.

Resolver

Cloudflare Google Quad9 Compare all three

Include DNSSEC signatures

How this works

Your browser takes the domain from what you typed, dropping any web address parts, email user or port. An international name is converted to its xn-- form, after removing invisible characters such as soft hyphens and reading full-width letters and dots as ordinary ones (UTS #46). An IP address becomes its reverse name under in-addr.arpa or ip6.arpa.
It turns the name and record type into a standard DNS query packet: the same bytes a tool like dig would send.
Browsers can't send DNS packets themselves, so this page posts the packet to abbott.cloud/api/dns. That checks it's a single ordinary question and forwards the bytes, unchanged, to the resolver you picked using DNS over HTTPS (RFC 8484).
The resolver's answer comes back as raw bytes, and this page decodes and explains it. A record it can't decode is shown as raw bytes in hex instead. Open any entry in the request log below to see both packets.

What's kept: nothing. The name you look up goes in the page's address so you can share the result, but it isn't stored. The resolver sees the query arrive from Cloudflare's network, not from your IP address.

Resolvers: Cloudflare (1.1.1.1), Google Public DNS (8.8.8.8) and Quad9 (9.9.9.9) are public recursive resolvers. Each caches answers for up to the record's TTL, so after a change they can disagree for a while.

Code: dns.js (this page), dnswire.js (packet encoding and decoding), domain.js (names), net.js (requests).