See what Google, Cloudflare and Quad9 are answering for your domain right now — and how long they will keep answering before they refresh. No account needed.
Resolvers keep a copy of your record for as long as its TTL allows, and each one started its copy at a different moment. So a change is live on your nameservers straight away, and still the old value at a resolver that fetched it an hour ago.
This page shows how much of the old answer is still out there, and how long it has left. Planning a move? Lower the TTL a day before, not after.
Because each one cached your record at a different moment. When you change a record, resolvers keep serving the old answer until the TTL that was on it runs out, and they did not all fetch it at the same second. Watch the TTL column: when it reaches zero that resolver fetches again and picks up your change.
Time to live — how many seconds this resolver will keep serving the answer it has before asking again. It counts down. A record with a TTL of one hour can take up to an hour to change everywhere, which is why a change you have already made can still look wrong from somewhere else.
Almost certainly not. Your nameservers have the new record the moment you save it. What you are seeing is a resolver still inside the TTL of the old answer. Lower the TTL before you plan a change, not after, and the next change moves faster.
No, and that is deliberate. It shows what three public resolvers are serving, which is what your visitors actually get. A tool that asked our own nameservers would only confirm that we published what we published.
Every change is published to our nameservers in seconds, with a full history of what changed and a recycle bin for the days it goes wrong. Every zone is DDoS-protected, on every plan including the free one.
