DNS Lookup

The DNS Lookup tool resolves DNS records for any domain through Google's public DNS-over-HTTPS resolver, so results reflect the state that real users experience on the global network. Enter a domain and pick one of eight record types — A, AAAA, MX, TXT, NS, CNAME, SOA, or CAA — then hit Lookup or press Enter to query. The domain field validates that only letters, numbers, dots, and dashes appear and that the value contains at least one dot before sending anything. Lookups carry a 15-second timeout that aborts slow or hanging responses. Stat cards summarize the number of records returned, the queried record type, the DNS status code shown as NOERROR when zero, and the resolver identity as Google DoH. Results render in a scrollable table with the owner name, a type badge, the TTL in seconds, and the record data. Sample domain chips for example.com, google.com, and cloudflare.com run a lookup instantly, and a matching lookup aborts a previous in-flight request to avoid stale answers. An amber banner appears when the query succeeds but returns no records for the chosen type, such as an MX query on a domain that only publishes A records.

1. 1

   Type a domain such as example.com into the Domain field; the hint below the label suggests the expected format.

2. 2

   Choose a record type from the Record type select — A, AAAA, MX, TXT, NS, CNAME, SOA, or CAA.

3. 3

   Click Lookup or press Enter in the domain field to run the query through the Google DNS-over-HTTPS resolver.

4. 4

   Click a Try chip for example.com, google.com, or cloudflare.com to run an in-place lookup for that sample domain.

5. 5

   Read the Stat cards and the results table, checking the name, type badge, TTL in seconds, and data column for each answer row.

• Propagation checks after a DNS change — confirm the new A or AAAA answer is live across caches on the public resolver before launch.
• Email deliverability triage — MX queries reveal missing or misweighted mail servers that silently bounce inbound messages.
• SPF and verification audits — TXT lookups surface the SPF, DKIM, and domain-verification strings that anti-spam filters expect.
• CDN and hostname debugging — CNAME responses show which hostname the domain really points to and where the alias terminates.
• Domain transfer planning — NS records identify the current authoritative name servers before you move delegation to another host.
• Security policy reviews — CAA entries list which certificate authorities may issue for a domain, exposing misconfigurations.

• Wait at least one full TTL before re-checking after a change; querying sooner will report a cached answer as a false failure.
• Look up both the apex and the www hostname, since many outages live in a missing www CNAME rather than the base record.
• Cross-check MX data against the mail provider's published documentation, and confirm the preference order matches your failover intent.
• Query TXT records from the public resolver to verify SPF includes are served for a domain before an email gate blocks your mail.
• Use CAA records to allow only the CAs you actually buy from, then spot-check them after quarterly audits for unexpected allow entries.
• Treat a NOERROR with zero answers as an intentional NXDOMAIN or empty zone, not a lookup failure; the tool keeps them visually separate.

• Compare A and AAAA results side by side for the same hostname to spot dual-stack gaps where IPv6 users cannot reach the site.
• Keep the amber no-records banner in mind as a feature, not a bug; an intentionally bled zone returns NOERROR with an empty table.
• Do an MX lookup on your own domain quarterly; mail routing that silently changed preferences is a classic outage that nobody notices.
• Use the Try chips to sanity-check your network first, so a failing manual lookup is clearly a domain issue and not a resolver problem.