CNAME Checker
Follow a host name's chain of aliases, hop by hop, to the records at the end, with the TTL of each step.
What this tool checks
A CNAME record makes one name an alias of another. Aliases can point to further aliases, forming a chain. This is common with content delivery networks (CDNs) and hosted services: www.example.com may point to example.cdn.example.net, which points to an edge host name, which finally has A and AAAA records.
The CNAME checker resolves the name step by step through Cloudflare’s resolver, over DNS over HTTPS, from our server. For each hop it records the alias, its target and its TTL. It stops when it reaches a name without a CNAME, after 10 hops, or when it detects a loop, and then shows the final records.
How to read the result
The chain lists each step:
| Name | Target | TTL |
|---|---|---|
www.example.com. |
example.cdn.example.net. |
3600 |
example.cdn.example.net. |
edge7.cdn.example.net. |
60 |
The final records are the records of the last name in the chain, typically A and AAAA, for example edge7.cdn.example.net. 60 IN A 198.51.100.77.
What to look for:
- The first target is what you configured. It should be exactly the host name your provider gave you.
- Later hops belong to the provider. You do not control them, and they may change over time. That is the point of using a CNAME: your record stays the same while the provider moves things around.
- TTLs. Each hop is cached separately. Your own CNAME often has a long TTL; the provider’s hops are often short so it can redirect traffic quickly.
- No chain at all. The name has no CNAME; the tool shows its records directly.
- Loop detected. Two or more names point at each other. Resolution fails with
SERVFAILuntil one of them is fixed.
When to use this checker
- After connecting a domain to a CDN or SaaS platform, to confirm the first hop is exactly the host name the provider asked for and that the chain ends in real addresses.
- Before cancelling a service, to find subdomains still pointing to it.
- When a site is slow to start loading, to see whether a long chain of aliases with short TTLs adds lookups to every first visit.
- When debugging certificate errors, to see which provider actually serves a host name.
Common problems and fixes
- CNAME at the bare domain. Not allowed, because the apex must hold SOA and NS records and a CNAME cannot share its name with other records. Use A and AAAA records at the apex, or your DNS provider’s flattening or ALIAS feature. An HTTPS record in AliasMode is a standardised alternative, but browser support is still limited.
- The target is wrong or misspelt. Copy it exactly from the provider’s instructions. A missing trailing dot in a zone file can turn
stores.example.netintostores.example.net.example.com. - The chain ends in NXDOMAIN. The service was deleted or renamed. Update or remove your CNAME. If it pointed to a cloud resource you no longer own, remove it now to avoid a subdomain takeover.
- Other records on the same name. A name with a CNAME cannot have MX, TXT or any other record. If a service asks for a verification TXT on a name that is a CNAME, use a different name or follow the provider’s alternative method.
- The certificate does not match. A CNAME does not change the name in the browser’s address bar. The service behind the chain must have a TLS certificate for your name, which most providers issue once you add the domain in their dashboard.
- MX or NS pointing to an alias. Not allowed by RFC 2181. Point them to names with address records.
Related
- CNAME record guide: rules, examples and pitfalls.
- DNS lookup: query any record type on any name in the chain.
- DNS propagation checker: see whether a changed CNAME has reached the public resolvers.
- A record guide and AAAA record guide: the records at the end of the chain.
Frequently asked questions
How many hops are too many?
There is no hard limit in the standards, but each hop adds a lookup and a point of failure, and resolvers stop after a certain number. One or two hops is typical for CDNs and SaaS platforms. This tool follows up to 10.
What is a dangling CNAME?
A CNAME that points to a name that no longer exists, often a cloud resource that was deleted. If someone else can create a resource with that name, they can serve content on your subdomain. Remove CNAMEs when you stop using a service.
The chain ends with no A or AAAA records. Is that a problem?
Yes, if the name is meant to be reachable. The last target exists but has no address records, or does not exist at all. Check the target with the provider whose name it is.