Free CNAME Lookup
Enter a hostname to read its CNAME record, follow each alias to the name it finally lands on, and see whether that name returns an address.
Following the chain...
Could not check
-
points to
TTL
No A or AAAA address came back for this name.
What a CNAME Lookup Tells You
A CNAME lookup asks which name a hostname is an alias for. A CNAME record says "this name is really that name", so a resolver restarts its query at the target. It is how www, shop or status get pointed at a hosting platform, a CDN or a SaaS product.
One hop rarely tells the whole story, because the target is often an alias too. This tool follows the chain hop by hop, shows the TTL at each step, and reads the addresses at the end, so a target that no longer exists is named. For every other record on the name, run a full DNS lookup.
- Enter the exact hostname, such as www.example.com. A CNAME belongs to one name, so the subdomain matters.
- We ask a public resolver for the CNAME at that name, then repeat at each target.
- Read the chain, the final name and the addresses it returns.
- If you just changed the record, confirm it across resolvers before you rely on it.
What this check settles
- Where a name really points: the last name in the chain, not just the first alias.
- Whether the target is still there: an alias whose target returns no address is a broken link, and sometimes a claimable one.
- Whether the setup is legal DNS: a CNAME on the bare domain, a loop, or a chain too long to trust are all named.
CNAME Patterns Explained
Most lookups end in one of four shapes. Here is what each one means for the hostname.
| Pattern | What the chain does | What it means | State |
|---|---|---|---|
| Single alias | One hop to an address | The usual setup: www.example.com points at a host your platform gave you, and that host returns an address. | Healthy |
| Chain | Several hops to an address | Common with CDNs and SaaS platforms, which alias to their own infrastructure. It works, and every hop is another party you depend on. | Normal |
| Apex CNAME | A CNAME on the bare domain | Not allowed by the DNS standard, because the apex must hold SOA and NS records and a CNAME cannot coexist with anything else. | Risky |
| Dangling | Ends with no address | The target no longer returns an address, usually after a service was cancelled and the record left behind. It is the classic setup for subdomain takeover. | Broken |
How to Read the Result
The verdict comes first, then the chain as it was followed.
The verdict
The headlineWhether the name is an alias at all, and whether the chain reaches an address. A loop, a dangling target and a CNAME on the bare domain each get their own verdict.
The chain
The hopsEach alias in the order a resolver follows it, from the name you entered to the last target, up to 8 hops.
TTL at each hop
The timingHow many seconds a resolver may cache that step. Resolvers count this down, so the number can be lower than the value set at your DNS provider.
Final name and addresses
The endThe name the chain lands on and the A and AAAA addresses it returns. These can change without any CNAME changing, because the target belongs to the platform.
What a CNAME Record Is
A CNAME, or canonical name record, maps one hostname to another. It holds a name, never an IP address. When a resolver finds one, it starts again at the target and returns whatever lives there.
That indirection is the reason platforms ask for it: they can move your site between servers by changing their own records, and yours never has to change.
The Rules a CNAME Must Follow
A few rules from the DNS standards catch people out, and most DNS providers refuse to save a record that breaks them.
In short:
- A name with a CNAME can hold no other record, so TXT and MX cannot sit beside it.
- The bare domain cannot be a CNAME, because it needs SOA and NS records.
- The target is a hostname, never an IP address or a URL.
- MX and NS records must point at a real hostname, not at an alias.
Where CNAME Records Go Wrong
A CNAME usually fails long after it was added. The common cases:
- A service is cancelled and the alias stays behind. If someone else can claim the target on that platform, your subdomain serves their content.
- A TXT record is needed on a name that already has a CNAME. The two cannot coexist, so verification fails. A TXT record lookup shows what that name actually returns.
- The record was saved with the zone name appended, giving www.example.com.example.com. Check the raw target in the chain above.
- A flattened apex looks like a plain A record. ALIAS and ANAME are features of the DNS provider, so a lookup shows the addresses and no CNAME.
Why CNAME Records Matter
Subdomain takeover
A dangling alias to a claimable service lets a stranger publish under your domain, cookies and reputation included.
Outages you did not cause
Every hop is a third party. When a platform retires a hostname, your subdomain stops resolving with no change on your side.
Hidden dependencies
The chain shows which CDN, host or SaaS really serves a name, which is often not what the team remembers.
Clean migrations
Before moving a site, the chain and its TTLs show exactly what has to change and how long the old answer can linger.
Who Runs CNAME Lookups
The same chain answers a different question depending on who is reading it.
IT & DNS Admins
Confirm an alias after a change, and find out why a hostname stopped resolving.
For DNS monitoringMarketers & SEOs
Check that a landing page, tracking or email link subdomain points where the vendor said it should.
For marketersAgencies
Verify a client's records during a launch, and clean up aliases left by old platforms.
For agenciesRelated DNS Tools
A CNAME is one record on one name. These cover what sits around it.
Full DNS lookup
See every record type on a name when the alias is not the whole answer.
Run a DNS lookupCheck propagation
Just changed the target? Confirm that public resolvers see the new answer.
Check propagationCheck the certificate
A subdomain pointed at a new platform also needs a valid certificate for its name.
SSL certificate checkerFrequently Asked Questions
Common questions about CNAME records and how to look them up.
How do I look up a CNAME record?
Enter the exact hostname in the tool above, for example www.example.com. It asks a public resolver for the CNAME, follows each target, and shows the chain and the addresses it ends at. On the command line, dig CNAME www.example.com does the first hop.
Why does my domain show no CNAME?
Either the name uses A or AAAA records directly, or you looked up a different name from the one that holds the alias. A CNAME belongs to one exact hostname, so www.example.com can have one while example.com does not.
Can I put a CNAME on my root domain?
Not under the DNS standard. A CNAME cannot share a name with other records, and the root domain must hold SOA and NS records. Many DNS providers offer ALIAS, ANAME or CNAME flattening, which behaves like an alias but answers with plain addresses.
What is the difference between a CNAME and an A record?
An A record maps a name to an IPv4 address. A CNAME maps a name to another name, and the resolver then looks up that name. Use an A record when you control the address, and a CNAME when a platform owns it and may change it.
What is a dangling CNAME?
An alias whose target no longer returns an address, usually because the service behind it was cancelled. If that target can be claimed on the platform, someone else can serve content on your subdomain. Remove the record if you no longer use the service.
How many CNAMEs can be chained?
The standards set no firm number, but each hop adds a lookup and resolvers do limit how far they follow. Chains of two or three are common with CDNs. This tool stops at 8 hops and says so.
Can a CNAME point to an IP address?
No. The value must be a hostname. To point a name at an IP address, use an A record for IPv4 or an AAAA record for IPv6.
Can a name have a CNAME and a TXT record?
No. A name with a CNAME can hold no other records. If a service asks for a TXT record on a name that already has a CNAME, use a different name or remove the alias.
I changed a CNAME. Why does the tool show the old target?
Resolvers cache the old answer until its TTL runs out. The TTL at each hop tells you how long that can take. Use the propagation checker to compare what different public resolvers currently return.
Start Monitoring & Catching Domains Today
Join founders, agencies, and domainers already protecting their portfolio. Your first 5 domains are free.
No credit card required • Cancel anytime
Guides for domain operators
Deep dives on domain names, DNS, SSL, acquisitions and portfolio management.
All guides →
4 Letter Domains: The Complete LLLL Investing Playbook
4 letter domain names represent one of the most liquid segments of the domain aftermarket. All 456,976 possible .com combinations are registered.
.SI Domain: Slovenia's 30-Year-Old ccTLD Is Suddenly Super Intelligence
What is the .SI domain? Learn how Slovenia's country-code TLD went from 10 registrations in 1992 to a 2,199% surge in September 2026, and why 'super intelligence' made .SI the new .AI.
Infringing Domains: Detecting, Monitoring, and Recovering
Your domain is your storefront. Every day, someone registers a lookalike of it, to skim your traffic, phish your customers, or hold it for ransom. This guide covers what infringing domains are, how to find them before they hurt you, and exactly what to do when you do.