DNS Lookup Tool - Professional Domain Name Resolution

About this tool

Perform comprehensive DNS lookup queries to resolve domain names to IP addresses. Check A, AAAA, MX, CNAME, TXT, and other DNS records using Google DNS and Cloudflare DNS. Perfect for network troubleshooting and domain analysis.

Two public recursive views at this time; agreement does not verify every network or the authoritative zone.

Domain name: Type:

Google DNS Result

Raw response / error

Cloudflare DNS Result

Raw response / error

Usage guide

When This Is Useful

This page is intended for practical troubleshooting rather than deep authoritative analysis. It is useful when a hostname resolves from one network but not another, when mail delivery depends on MX or TXT correctness, when a service cutover is waiting on public DNS visibility, or when you want a quick sanity check before opening command-line tools on a jump host.

How To Read Resolver Differences

Cache timing, recent changes, GeoDNS/CDN routing or resolver policy can produce different answers. Different IPs alone do not prove a fault. Compare with the authoritative DNS configuration and your local resolver. For a recent change, repeat after the relevant cache TTL; check the intended record type.

Things To Watch For

Record type matters. A missing A record does not mean the zone is broken if the service is intentionally IPv6-only, and an unexpected CNAME may be valid if traffic is being handed off through a CDN or verification platform. The ANY type is also not a reliable universal diagnostic because many providers intentionally limit or synthesize responses to it. Treat this page as a public-recursive view, not as the final source of truth.

Tool reference

Inputs

A domain name (e.g. google.com)
Record type: A, AAAA, MX, CNAME, TXT, NS, SOA, SRV, PTR, CAA, ANY

Outputs

Raw JSON response from Google DNS
Raw JSON response from Cloudflare DNS
Side-by-side comparison helpful for spotting resolver divergence

Use Cases

DNS troubleshooting across two independent resolvers
Verifying propagation of new records
Quick sanity check during migration

Data Sources

Google Public DNS (DoH)
Cloudflare DNS (DoH)

Limitations

Uses public DoH endpoints; not your recursive resolver
Single-domain per query

Example Input

google.com (type A)

Example Output

Google DNS:     Answer: 142.250.x.x
Cloudflare DNS: Answer: 142.250.x.x
(Full JSON shown in the UI for each resolver)