What is a CNAME record?

A CNAME (Canonical Name) record is a DNS entry that points one hostname to another hostname instead of to an IP address, so the target name's records are used. It is commonly used to alias subdomains like www or a service host to a provider's domain.

How do I use this CNAME lookup tool?

Enter a hostname such as www.example.com and run the lookup, and the tool queries that name's CNAME record server-side and shows the canonical target it points to. Nothing you enter is stored.

Why do CNAME records matter?

They let you point a subdomain at an external service (like a CDN, email or hosting provider) so that if the provider changes its underlying IP, your subdomain keeps working without any edit on your side. This makes them essential for verifying that aliases and third-party integrations resolve correctly.

How do I read the result?

The result shows the canonical hostname your name points to; you can then look that target up to follow the chain to its final A or AAAA record. If no CNAME is returned, the name either has no alias or holds direct records instead.

Are there limits on where a CNAME can be used?

A hostname with a CNAME cannot also hold other records, so a CNAME must never be placed on a zone apex (the bare domain like example.com) alongside its required SOA and NS records. For the root domain use an A/AAAA record or a provider's ALIAS/ANAME feature instead.

CNAME Record Look Up

Related tools

Domain name

What do you want to look up?

Blacklist Look Up

Looks up whether this domain's IP address (or the IP address you entered) appears on common email blacklists (DNSBL) — being listed can cause outgoing mail to be rejected or sent to spam.

Also look up blacklist status when I run this search

What this is

A CNAME record makes one hostname an alias for another: the alias inherits whatever records the target has. It is the standard way to point subdomains at CDNs, SaaS platforms, and hosted services.

How to read your result

The result shows the target the name points at. Follow the chain mentally: your subdomain is only as healthy as its target. If the target is a service you no longer use, that is a problem worth fixing immediately.

Common problems and how to fix them

CNAME added on the bare domain alongside other records

How it shows up: DNS provider rejects the record, or mail/other services on the domain break mysteriously.

How to fix it: A CNAME cannot coexist with any other record on the same name, and the bare domain always has SOA/NS records — so a true CNAME there is invalid. Use your provider's ALIAS/ANAME/flattening feature, or point the bare domain via A record and CNAME only the www.

CNAME points at a retired or unclaimed service

How it shows up: The subdomain shows an error page from the platform — or worse, someone else claims the abandoned target and serves their own content on your subdomain (subdomain takeover).

How to fix it: Remove CNAMEs for services you cancelled, and do it before or immediately when the service is terminated. Audit all CNAMEs periodically; takeover via dangling CNAMEs is a real and common attack.

Long CNAME chains

How it shows up: Slower first lookups and harder troubleshooting; some old resolvers give up on deep chains.

How to fix it: Point the alias as directly as possible at the final target instead of chaining alias → alias → target.

Frequently asked questions

What is a CNAME record?: A CNAME (Canonical Name) record is a DNS entry that points one hostname to another hostname instead of to an IP address, so the target name's records are used. It is commonly used to alias subdomains like www or a service host to a provider's domain.
How do I use this CNAME lookup tool?: Enter a hostname such as www.example.com and run the lookup, and the tool queries that name's CNAME record server-side and shows the canonical target it points to. Nothing you enter is stored.
Why do CNAME records matter?: They let you point a subdomain at an external service (like a CDN, email or hosting provider) so that if the provider changes its underlying IP, your subdomain keeps working without any edit on your side. This makes them essential for verifying that aliases and third-party integrations resolve correctly.
How do I read the result?: The result shows the canonical hostname your name points to; you can then look that target up to follow the chain to its final A or AAAA record. If no CNAME is returned, the name either has no alias or holds direct records instead.
Are there limits on where a CNAME can be used?: A hostname with a CNAME cannot also hold other records, so a CNAME must never be placed on a zone apex (the bare domain like example.com) alongside its required SOA and NS records. For the root domain use an A/AAAA record or a provider's ALIAS/ANAME feature instead.