DNS lookup & propagation
Enter a domain and record type — the tool queries two independent DNS resolvers (Cloudflare and Google) simultaneously. Matching answers mean the change has propagated; differing ones mean DNS is still spreading.
What each record type does
A/AAAA point to the website’s IP, CNAME aliases another name, MX defines mail servers, TXT carries verifications and policies (SPF, DKIM — check them here) and NS says who manages the domain.
How long DNS propagation takes
After a change, resolvers worldwide keep the old value for the TTL — typically minutes to hours, up to a day for NS changes. That is exactly what this tool shows: when independent resolvers agree, you are propagated. Moving your site to the EU? See the ordering walkthrough.
Frequently asked questions
I changed DNS but my site still loads from the old host. Why?
Your resolver (or browser) holds the old value for the TTL. Check the record with this tool — if the three big resolvers already return the new value, it is just local cache; restarting the browser or waiting helps.
What is the TTL shown next to answers?
Time To Live — how many seconds a resolver may cache the answer. Before a planned DNS change, lower the TTL a day ahead so the change spreads faster.
Why do resolvers return different answers?
Most often a change is still propagating. A persistent difference can mean geographically varied answers (GeoDNS/CDN) — normal for large services.