--
Checking…
Querying the resolvers.
How to read this. Each public resolver keeps its own cache of every record. When you change DNS, the change is instant at your authoritative nameservers, but each resolver keeps serving the old value until its cached copy expires (the record's TTL). So when every resolver here shows the same answer, your change has propagated; if some differ, they are still inside the old TTL. One honest limit: we query from a single network vantage point, so this compares resolver caches, not a worldwide geographic map. A resolver like 8.8.8.8 runs from many locations, and you may see a different cache from another country, for a full global view use a service like whatsmydns.net. For the registration, DNSSEC and CAA side of a domain, use our Domain & DNS Checker.
// What this means for your business
A small DNS change can take you offline
DNS is the quiet plumbing behind your website, email and apps, and a single wrong record or mistimed change can break all three at once. Planning migrations, setting sensible TTLs, and knowing how to roll back is everyday infrastructure work. That is the kind of behind-the-scenes IT we run for small Canadian businesses, as one team you can actually call.