RunTheTests

DNS Lookup (all records)

Query any DNS record type against two independent resolvers and compare their answers.

How this lookup works

Your browser sends the query directly to two public DNS-over-HTTPS resolvers, Cloudflare and Google, and their answers are compared. Nothing passes through our servers. Querying two resolvers rather than one is what makes a disagreement visible: if they return different records, a recent change has definitely not finished spreading.

What the results mean

TTL
How many seconds a resolver may keep serving this answer before checking again. After you change a record, expect the old value to persist for up to this long.
Resolvers agree
Both resolvers returned identical records. That means those two are consistent — it does not mean every resolver worldwide has the same answer.
NXDOMAIN
The domain itself does not exist. This is different from a domain that exists but has no record of the type you asked for.
No records found
The domain resolves but has no record of this type. Normal for most types — only a problem if you expected one.

Common problems and fixes

I just changed a record and still see the old value
Resolvers cache answers for the duration of the TTL shown against the previous record. Wait out that TTL before concluding the change failed.
The lookup fails entirely
Some corporate networks, privacy extensions and DNS-filtering tools block DNS-over-HTTPS requests. Try on another network to confirm whether the block is local.

Frequently asked questions

Can this tell me if my DNS change has propagated worldwide?

No, and nothing that queries a handful of resolvers can. This checks two resolvers. If they disagree, propagation is definitely incomplete; if they agree, it means those two are consistent and says nothing about the rest of the internet. Any tool claiming a global propagation check from a small sample is overstating what it measured.

Why do the answers differ from dig on my machine?

Your machine uses whichever resolver your network or router configured, which may be caching a different answer with a different TTL. That is normal, and it is the reason the same domain can work for one person and not another during a change.

Does my query go through your servers?

No. The request goes from your browser straight to the public resolvers, so we never see which domains you look up.

More in Connection