Look up the IPv6 address(es) a domain points to.
Every other tool on this site runs entirely as JavaScript in your browser and never contacts a server at all. This one is a deliberate exception, by necessity: the domain name you enter is sent to this site’s server so it can run the DNS query — that’s unavoidable, since browsers can’t query DNS directly — using this server’s own DNS resolution (Node.js’s built-in dns module), with no third-party API involved. Nothing about the request is logged, stored, written to a cookie, or shared with any third party — it's handled and discarded the moment the response is sent back to you.
This describes only what this specific tool does with what you type into it. It doesn't cover the rest of this site — see the Privacy Policy for how analytics and advertising cookies are handled elsewhere.
This queries live DNS records for any domain — A and AAAA (the IPv4/IPv6 addresses a domain points to), MX (mail servers), TXT (free-form text records, commonly used for domain verification, SPF, and other email/security configuration), NS (nameservers), CNAME (aliases pointing to another domain), and SOA (zone administration details).
This is useful for confirming a DNS change actually took effect, checking where a domain's email is routed, verifying a TXT record you were asked to add for domain verification, or just understanding how a domain is configured without needing a command-line tool like dig or nslookup.
A domain having no records of a given type isn't an error — most domains don't have every record type set, so an empty MX result, for instance, just means no mail server is configured for that domain, not that the lookup failed.
Browsers have no raw DNS query capability — there’s no way for JavaScript running in a page to send a DNS request directly. This is one of a small number of tools on this site that necessarily involves the server for that reason.
No — this uses Node.js’s own built-in DNS resolution, querying through this server’s normal DNS resolver. No external API is called, and the domain you look up isn’t logged.
DNS results can genuinely differ by resolver, especially right after a change (see the DNS Propagation Checker) or if you’re on a VPN or corporate network with custom DNS settings.
It means that domain doesn’t have any records of the type you selected — not every domain sets every record type. It’s different from the domain not existing at all, which returns a clear error instead.