Query Google's Public DNS resolvers to retrieve A, AAAA, CNAME, MX, NS, and TXT records for any domain instantly.
DNS (Domain Name System) records are text-based instructions stored on authoritative nameservers that tell the internet how to route traffic for a domain. Without DNS, you would need to memorise numeric IP addresses to visit every website. DNS translates human-readable names like google.com into machine-readable addresses like 142.250.70.14.
This tool queries Google's Public DNS resolver (8.8.8.8) over HTTPS to retrieve live DNS records. The results reflect what Google's resolvers currently have cached, which closely mirrors what your browser sees when you visit a website.
The most fundamental DNS record. It maps a domain name directly to an IPv4 address. When you type example.com into your browser, the A record tells your computer which server to connect to. Every website needs at least one A record.
Identical to an A record but maps to an IPv6 address instead of IPv4. As the internet transitions to IPv6, more domains are adding AAAA records alongside their A records to support dual-stack connectivity.
Forwards one domain to another domain (never to an IP). For example, www.example.com might CNAME to example.com, which then has the A record. CNAMEs are commonly used for subdomains and CDN configurations.
Specifies which mail servers accept email for the domain, along with a priority value. Lower priority numbers are tried first. If you use Google Workspace, your MX records point to aspmx.l.google.com.
Stores arbitrary text data. Most commonly used for SPF (Sender Policy Framework), DKIM (DomainKeys Identified Mail), and DMARC email authentication. Also used to verify domain ownership for services like Google Search Console and Microsoft 365.
Indicates which DNS servers are authoritative for the domain. These are the "source of truth" servers that hold the actual DNS records. Changing NS records at your registrar is how you delegate DNS management to providers like Cloudflare or Route 53.
When you type a domain into your browser, a multi-step lookup process happens in milliseconds:
8.8.8.8 or Cloudflare 1.1.1.1)..com, .org, etc..com replies with the NS records for the specific domain. Every DNS record has a TTL value measured in seconds. This tells DNS resolvers how long they should cache the record before asking the authoritative server again. A TTL of 300 means the record is cached for 5 minutes. A TTL of 86400 means 24 hours.
Short TTLs (60-300 seconds) are used when you expect frequent changes — for example, during a server migration or when using dynamic DNS. Long TTLs (3600-86400 seconds) reduce DNS query load and improve performance for stable records. When you see TTL values in the results table above, lower values indicate the domain owner expects that record to change more frequently.
Many DNS providers (including Cloudflare) block ANY queries for security reasons, as they can be used in DNS amplification DDoS attacks. If ANY returns nothing, try querying specific record types (A, MX, TXT) individually.
This tool queries Google's Public DNS resolver. If you recently changed your DNS records and Google still shows the old values, it means the previous record's TTL has not yet expired in Google's cache. Wait for the TTL duration and check again.
Yes! Select "MX" to verify your mail exchange servers, and "TXT" to check your SPF, DKIM, and DMARC records. Misconfigured email DNS is the number one reason emails go to spam.