CNAME Lookup
Find the canonical name a host is aliased to.
Enter a value above to run CNAME Lookup
e.g. www.example.com
Quick answer
A CNAME lookup shows the canonical hostname an alias points to. If a result appears, the name is an alias that forwards to the target host; if it's empty, the name has no CNAME and resolves directly.
A CNAME (Canonical Name) record points one hostname at another hostname instead of at an IP address. This tool queries a host's CNAME record and shows you the canonical target it resolves to, so you can confirm that aliases like www, shop, or a vendor-provided subdomain point where they should.
It is the fastest way to verify CDN, SaaS, and email-provider setups that ask you to "create a CNAME." Instead of guessing whether your DNS change took effect, you see the exact alias chain the resolver follows.
How it works
When you look up a host, the tool asks a DNS resolver for that name's CNAME record. If one exists, the server returns the canonical target, for example www.example.com pointing to example.com or to a provider host like d1234.cloudfront.net. A CNAME can point to another CNAME, forming a chain that ends at an A or AAAA record. The lookup follows and reports each alias so you see the full path from the queried name to its final canonical name.
How to read the results
The result shows the queried host on one side and the canonical target on the other. Confirm the target string matches exactly what your CDN or SaaS provider gave you, including the trailing part of the domain. If the tool returns no CNAME, the name is either an A/AAAA host, a different record type, or not configured. A chain of several hops is normal but adds lookup latency, so keep chains short where you can.
Common problems & fixes
A classic mistake is putting a CNAME on the root domain (example.com); the DNS standard forbids a CNAME coexisting with the SOA and NS records that a zone apex must have, so use an A record, ALIAS, or ANAME there instead. Another is a stale answer after an edit, caused by the old record's TTL still being cached. Also avoid pointing a CNAME at a name that itself has no A record, which produces an unresolvable chain.
Frequently asked questions
- What is the difference between a CNAME and an A record?
- An A record maps a hostname directly to an IPv4 address, while a CNAME maps a hostname to another hostname. Use a CNAME when a provider controls the target's IP and may change it, since the alias keeps working automatically. Use an A record when you own the IP or need to point the zone apex.
- Why can't I add a CNAME on my root domain?
- A zone apex, such as example.com, must carry SOA and NS records. The DNS specification says a CNAME cannot exist alongside any other record for the same name, so it is invalid at the apex. Use an A/AAAA record, or your provider's ALIAS or ANAME feature, which mimics a CNAME at the root.
- How long until my new CNAME becomes visible?
- It propagates as fast as the previous record's TTL allows. If the old value had a one-hour TTL, resolvers may serve the cached answer for up to that long before fetching the new one. Lowering the TTL before a planned change, then raising it afterward, keeps switchovers quick and predictable.