example.com or mail.google.com — into the Domain field. No https:// prefix needed.DNS Lookup works like dig or nslookup in your browser — no terminal required. This free online DNS checker is useful for verifying DNS propagation after changing nameservers, confirming mail server (MX) configuration, debugging SPF and DMARC TXT records, checking that a CNAME alias is pointing at the right host, or looking up the IPv4 (A) and IPv6 (AAAA) addresses for any hostname.
DNS Lookup queries Google's public DNS-over-HTTPS (DoH) resolver at dns.google/resolve. Unlike a plain-text DNS request sent by your operating system, DoH wraps the query in HTTPS — so it is encrypted in transit and cannot be intercepted by your ISP or network provider. Results come directly from Google's authoritative resolver and are not cached by your browser or this tool, so you always see up-to-date records.
93.184.216.34). The most common record type.www → example.com).You can query A (IPv4 address), AAAA (IPv6 address), MX (mail exchanger / email servers), TXT (SPF, DKIM, DMARC, domain verification), NS (authoritative nameservers), CNAME (canonical name alias), SOA (start of authority), and PTR (reverse DNS / rDNS) records. Use the quick-select buttons to switch between types without retyping the domain.
This DNS checker uses Google's public DNS-over-HTTPS (DoH) API at dns.google/resolve. Queries are encrypted with TLS — there is no plain-text DNS leakage. Google's resolver provides fast, reliable, globally accurate results and is an alternative to using dig, nslookup, or host on the command line.
Your ISP's DNS resolver caches records for their full TTL duration. If you recently updated your DNS (changed A records, switched nameservers, or set up a new MX record), your local resolver may still return the old cached value. Google's DoH resolver returns results much closer to the authoritative source. Full DNS propagation after a change can take anywhere from a few minutes to 48 hours depending on the TTL of the updated record.
TTL (Time To Live) is the number of seconds a DNS record may be cached by resolvers and browsers before they must re-query the authoritative nameserver. A TTL of 300 = 5 minutes; 3600 = 1 hour; 86400 = 24 hours. Before making DNS changes, lowering the TTL to 300 or less lets you propagate updates quickly. After the change is stable, raising the TTL back to 3600–86400 reduces DNS query load.
After using DNS Lookup, explore the full suite of Network tools — including Subnet Calculator, CIDR Calculator, IP Info, and 310+ other free utilities — at Chunky Munster.
This DNS Lookup follows 📖 Reference: Google Public DNS — DNS-over-HTTPS JSON API