CNAME Record Lookup - Free DNS CNAME Checker

Instantly check CNAME records to see alias mappings for domains. Our CNAME checker helps verify DNS entries and resolve domain pointing issues

Global DNS propagation takes up to 48 hours!

Track global results with a DNS propagation checker!

A CNAME lookup shows which hostname a domain or subdomain is an alias of. A CNAME (canonical name) record says "this name is the same as that name": for example www.example.com → example.com, or shop.example.com → a hosted store's hostname. Resolvers follow the alias and use the target's own A or AAAA records.

How to check a CNAME record

  1. Enter the alias name, usually a subdomain such as www.example.com or blog.example.com.
  2. Choose a DNS server and click Search.
  3. To see where the alias finally points, run an A Lookup on the target.

From a terminal: dig www.example.com CNAME.

Understanding your results

  • Value is the target hostname the alias points to. It can itself be a CNAME, forming a chain.
  • No CNAME found means the name has its own records (for example an A record) rather than being an alias, or doesn't exist at all.
  • Targets reveal the service: CDNs, website builders and SaaS tools give you a hostname to point a CNAME at, so the target usually names the provider.

CNAME rules that cause problems

  • No other records next to a CNAME. A name with a CNAME can't also have MX, TXT or A records. Adding a TXT verification record to an aliased subdomain fails for this reason.
  • No CNAME on the bare domain. example.com needs SOA and NS records, so it can't be a CNAME. DNS providers work around this with ALIAS/ANAME records or "CNAME flattening".
  • MX and NS records must not point to a CNAME. They must point to a hostname with its own A/AAAA records.
  • Dangling CNAMEs are a security risk. If a CNAME points to a cloud or SaaS resource you've deleted, someone else may be able to claim that resource and serve content on your subdomain ("subdomain takeover"). Remove CNAMEs when you retire a service.

Frequently asked questions

When should I use a CNAME instead of an A record?

Use a CNAME when you point a subdomain at a hostname run by someone else, such as a CDN or hosted service, so their IP changes don't require you to update anything. Use an A record when you control the server's IP.

Can the root domain be a CNAME?

Not under the DNS standards, because the root of a zone must hold SOA and NS records and a CNAME can't coexist with other records. Use your DNS provider's ALIAS, ANAME or CNAME-flattening feature instead.

Does a CNAME slow down my site?

Slightly, the first time: the resolver needs an extra lookup to resolve the target. After that both answers are cached, so the effect is negligible in practice.

Why does SSL fail on my CNAME subdomain?

The service the CNAME points to must have a certificate for your subdomain, not just its own hostname. Check what certificate is served with the SSL checker, and add the custom domain in the service's settings.