Free CNAME lookup. Enter a hostname and see its full CNAME alias chain, every hop from the name you queried to the canonical target it ultimately points at, plus the IPs that target resolves to. Resolved live from our London probe. The clean way to answer "what does this CNAME point to" and to catch broken or looping alias chains.
A CNAME (Canonical Name) record makes one hostname an alias for another. When a resolver looks up www.example.com and finds a CNAME pointing at example.com, it follows the alias and returns the target's address records. Aliases can chain, one CNAME pointing at another, which is common when a site sits behind a CDN or a managed platform, and this tool follows the whole chain to its final canonical target so you can see every hop.
A name that has a CNAME cannot also have other records, which is why you cannot put a CNAME on a root/apex domain (use ALIAS, ANAME, or CNAME flattening instead). Long chains add a little lookup latency. And a dangling CNAME, an alias pointing at a target that no longer exists, is a real risk: if someone can claim that target (an unclaimed cloud bucket or app hostname), they can take over your subdomain. Checking where a CNAME actually lands is the quickest way to catch these.
A CNAME (Canonical Name) record is a DNS record that makes one hostname an alias for another. Resolvers follow the alias and return the address records of the target name.
Enter the hostname in the tool above. It follows the full CNAME chain hop by hop to the final canonical target and shows the IP addresses that target resolves to.
No. The DNS standard does not allow a CNAME at the zone apex because it would conflict with the required SOA and NS records. Providers offer ALIAS, ANAME, or CNAME flattening to achieve the same effect at the root.
A dangling CNAME points at a target that no longer exists, often an unclaimed cloud or SaaS hostname. If an attacker can claim that target, they can serve content on your subdomain, which is known as a subdomain takeover.
