Skip to main content

DNS lookup, from two resolvers at once

Read any domain's records from Cloudflare and Google side by side and see where they disagree. One resolver tells you what one machine believes. Two tell you whether a change has finished spreading.

Record type

queries go from your browser straight to cloudflare and google · never through our servers · nothing stored

Enter a domain to read its records.

What each record type answers

typewhat it tells you
A IPv4 address the name points at
AAAA IPv6 address the name points at
CNAME Alias pointing this name at another
MX Mail servers, in priority order
NS Nameservers the zone is delegated to
TXT Free-form text: SPF, DMARC, domain verification
SOA Zone's start of authority and serial
CAA Which authorities may issue certificates

Why two resolvers

One resolver tells you what one machine currently believes. Two tell you whether the internet agrees with itself. Right after a change, the slower resolver keeps serving the old answer until its TTL runs out, and that gap is the reason a deploy looks fine to you and broken to a customer.

Addresses are the exception: behind a CDN or a geo-routed name, two resolvers are supposed to get different answers, because each is steered to a nearby edge. For NS, MX, TXT and CAA there is no such excuse, and a disagreement that outlasts the TTL means a filtering resolver, a captive network, or a zone that has been moved without its old delegation being cleaned up. That last one is common after a domain expires. The registrar parks the name, the parking page answers on port 80, and every uptime check stays green while MX records vanish and mail dies in silence. That failure has its own write-up: your domain can expire while your uptime monitor stays green.

FAQ

Why do two resolvers return different answers?
Usually you are seeing a change mid-flight: a record was edited and one resolver still holds the old answer until its TTL runs out. It can also mean a filtering or captive resolver is rewriting the answer, which is what makes a site look down from one network and fine from every other.
What is a TTL?
Time to live, in seconds: how long a resolver may cache the answer before asking again. A record with a TTL of 3600 can keep serving the old value for an hour after you change it, so lower the TTL before a planned migration, not after.
My site loads but mail stopped. What should I check?
Look at MX first, then TXT for the SPF record. A domain that expired and got parked keeps answering on port 80, so an uptime check stays green while MX records quietly disappear and mail dies. That failure is invisible to anything that only watches the homepage.
Does this send my domain anywhere?
The lookup runs in your browser and goes straight to the public resolvers at Cloudflare and Google. It does not pass through our servers, and nothing is stored.
Can I be told when these records change?
Yes. A DNS check watches a name and record type on a schedule and alerts when the answer changes or disappears. The button beside each result opens a monitor prefilled with what you just looked up.

Watch a record instead of checking it

A DNS check reads the same answer on a schedule and tells you the moment it changes or disappears.

start free

more free tools: uptime SLA calculator · error budget calculator · cron expression generator · the whole set