DNS Lookup

Run professional DNS lookups from your browser using encrypted DNS-over-HTTPS (DoH) resolvers — Cloudflare 1.1.1.1, Google 8.8.8.8, or Quad9 9.9.9.9. Choose the record type (A, AAAA, CNAME, NS, MX, TXT, SOA, PTR, SRV, CAA) and inspect TTL, status, and answer data in a clear table. Ideal for verifying website DNS, mail routing, nameserver delegation, and certificate authority authorization records during migrations or troubleshooting. Results reflect what each public resolver returns at query time — not an authoritative zone editor and not a security audit.

How to Use the DNS Lookup

Enter a domain, pick a record type and resolver, then inspect TTL and answer data returned over DNS-over-HTTPS.

  1. Open DNS Lookup.
  2. Enter a domain name (for example example.com) in the domain field.
  3. Select the record type — A for IPv4, AAAA for IPv6, MX for mail, TXT for verification strings, and so on.
  4. Choose a resolver: Cloudflare, Google, or Quad9.
  5. Click Lookup and wait for the response time badge.
  6. Review status (NOERROR), record count, and the Name / Type / TTL / Data table.
  7. Copy values you need or switch resolver to compare cached answers during a migration.

How DNS-over-HTTPS lookups work

The tool sends an HTTPS request to your chosen public resolver's DoH endpoint. The resolver queries the global DNS hierarchy and returns JSON answers your browser displays. No ICMP or raw DNS socket access is required.

Worked example

  • Check website IP: type A on your apex domain — compare the A record to your hosting provider's expected address.
  • Verify email routing: type MX — lower priority numbers are tried first by sending servers.
  • Confirm a CAA record exists before requesting a new TLS certificate from a specific CA.

Common mistakes

  • Querying www when records live on the apex (or the reverse) — check both names during cutovers.
  • Expecting instant global consistency — TTL and resolver cache delay propagation.
  • Choosing the wrong type — SPF lives in TXT, not a dedicated SPF type on the public internet.

Limitations

Answers come from one resolver at a time and reflect cached public DNS — not your ISP's private resolver or split-horizon internal DNS. This tool cannot bypass DNSSEC validation failures or guarantee authoritative correctness.

FAQ

Which DNS record types can I query?

The tool supports A, AAAA, CNAME, NS, MX, TXT, SOA, PTR, SRV, and CAA lookups. Select the type before running the lookup.

What is DNS-over-HTTPS (DoH)?

DoH sends DNS queries over encrypted HTTPS instead of plain UDP/TCP. Your browser talks directly to public resolvers like Cloudflare, Google, or Quad9 — no local dig or nslookup install required.

Why might Cloudflare, Google, and Quad9 show different answers?

Resolvers cache TTL-based responses and may sit in different regions. During DNS changes, one resolver might still serve an old cached answer while another already has the update.

Can I look up reverse DNS (PTR)?

Yes — choose PTR as the record type and enter the special .arpa zone name, or use the dedicated Reverse DNS Lookup tool with an IP address for automatic PTR name construction.

Does this edit my DNS zone?

No. This is a read-only lookup. To change records you must use your domain registrar or DNS hosting provider's control panel.

Why do I see NOERROR with zero records?

NOERROR with an empty answer set usually means the name exists but has no records of the requested type — for example, no MX on a web-only domain.

Is the query sent from my browser or a server?

DNS-over-HTTPS requests go from your browser directly to the public resolver you select. The domain you query is visible to that resolver provider.

Can I use this for internal/private hostnames?

Only if those names are resolvable on the public internet. Private intranet zones (internal.corp) typically return no data from public resolvers.

What does TTL mean in the results?

TTL (time to live) is how long, in seconds, a resolver may cache the answer before asking authoritative nameservers again. Lower TTL speeds propagation during planned changes.

Is this suitable for unauthorized scanning?

Use it only for domains and hosts you own or have permission to investigate. Do not use DNS lookups to probe systems you do not administer.