Global DNS propagation checker
We ask 22 public resolvers across the Americas, Europe and Asia, live, and show you exactly what each one is handing out right now.
elpais.com
Record type: AAAAACNAMEMXNSTXTSOACAASRVPTRDSDNSKEYHTTPSTLSANAPTR Refresh
| Resolver | Address | Answer | TTL | Response |
|---|---|---|---|---|
Each row is a public resolver queried live from our server. A row is highlighted when its answer differs from the majority, which is what a change still spreading looks like.
Run the full DNS report All records
Nothing actually propagates
DNS changes are not pushed anywhere. Your authoritative servers publish the new value immediately; the rest of the internet keeps serving the old one until the copy it cached expires. That is what the TTL of the record controls.
So a resolver still answering with the old value is not broken: it is simply inside the TTL window. If you plan a migration, lower the TTL a day in advance, make the change, then raise it again.
Why some resolvers never agree
Large providers answer from the closest datacentre, so two people can get different addresses on purpose. Anycast, GeoDNS and load balancing all produce legitimate differences that look like a propagation problem.