See whether your A record change has spread: 12 public resolvers, queried live, side by side.
Map key: each dot is the country where a resolver's operator is headquartered (number = resolvers), coloured by result. It does not show where the query ran — most of these resolvers are anycast networks with servers in many cities.
These are 12 large public resolvers, queried live over encrypted DNS-over-HTTPS from our servers. Most are anycast networks with many locations, so we show which resolver answered — not a city. Two (CIRA Canadian Shield) are run by the organization that operates .ca. Your ISP's resolver may still show an older answer until its cache expires.
An A record maps a domain name to an IPv4 address (like 203.0.113.10). It is the record that decides which server answers when someone opens your website, so it is the one you change when you move hosting.
Type your domain in the box above, keep A selected and press Search. We ask 12 public DNS resolvers — including two run by CIRA Canadian Shield — at the same moment and show each answer side by side.
Every green row should show the same IPv4 address(es) — the new server's IP. If some rows show the old IP, those resolvers are still serving a cached copy. Several addresses on one row is normal when a site uses round-robin or a CDN.
www CNAME or a second A record is still pointing at the old server.Up to the old record's TTL — commonly 5 minutes to 4 hours. Resolvers that had not cached your domain see the new IP immediately.
Either propagation is still in progress, or your DNS host returns different answers by location (geo-DNS, load balancing, or a CDN).
Yes — enter the domain and read the current A record on all 12 resolvers; if they all agree, you are looking at the real, settled value.