See whether your CNAME 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.
A CNAME record makes one name an alias of another (for example www.example.ca → example.ca, or a subdomain pointing to a hosting or SaaS provider). The resolver follows the alias and returns the final target.
Type your domain in the box above, keep CNAME 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.
Green rows should show the same target hostname. A red row means that resolver found no CNAME — either it has not seen the change yet, or the name has an A record instead. A CNAME cannot coexist with other records on the same name.
As long as the old CNAME's TTL. Lower the TTL to 300 seconds a day before the change to speed things up.
The name may use an A record, or the CNAME has not reached those resolvers yet. Check the exact subdomain you set.
Not under the DNS standard. Use an A record or a provider ALIAS/flattening feature.