CNAME Lookup
Check CNAME (canonical name) records for any domain to see where it is aliased to.
Did this tool work for you?
How to use this calculator
- 1
Enter the subdomain or domain whose CNAME you want to resolve.
- 2
Click "Check Now" to query the CNAME record.
- 3
Results show the CNAME chain — what the domain ultimately points to.
- 4
If no CNAME exists, the tool will report no record found.
Frequently asked questions
What does a result look like?
A table titled "CNAME chain for <name>" with the columns Name, Points to and TTL, one row for each CNAME record the resolver returns. Trailing dots are removed. If there is none, the page says either "No CNAME record found for <name>" or, when the name does not exist at all, "Domain does not exist (NXDOMAIN)" in red.
Why does my root domain show no CNAME?
Because a root (apex) domain normally cannot have one. A CNAME means "this name is an alias for another" and cannot coexist with other records at the same name, while the apex always carries NS and SOA records and usually MX and TXT. Some DNS providers offer an ALIAS, ANAME or flattening feature (Cloudflare calls it CNAME flattening) that behaves like a CNAME at the apex; to the outside world it returns plain address records, so this tool reports no CNAME.
Does the tool follow the alias to its final IP address?
No. It requests the CNAME type only, so it shows the alias and its target, not the address the target resolves to. A name that points straight to an IP address through an A record also shows "No CNAME record found". To see the final addresses, run the DNS Lookup with type A or AAAA on the same name.
Can I see a whole chain with several hops?
It lists whatever CNAME records the resolver includes in its answer, one row each, so a chain can appear as several rows. Each hop adds a lookup for resolvers, and long chains slow resolution and are best kept short. If only the first hop is returned, look up the target as a name of its own to continue.
Does it detect a dangling CNAME?
No. It displays the target but does not check that the target exists or still belongs to you. A CNAME pointing to a deprovisioned hosting or SaaS name is a known security risk because someone else may be able to claim that name, so check the target by looking it up separately and confirming the service is still active.
Why can’t I add a CNAME next to other records?
DNS rules (set out in RFC 1034) say that a name with a CNAME may have no other record types. If your provider refuses a CNAME for a name that already has an MX, TXT or A record, that is why: remove the other records or use a different name, for example a subdomain.
Is the name case-sensitive, and can I include https://?
DNS names are not case-sensitive, and the tool lowercases what you type. You can paste a full address; it keeps just the host name. It does not remove a leading www, so check the exact name your service asked you to alias, such as www.example.com or shop.example.com.
Checking CNAME aliases in DNS
What a CNAME record does
A CNAME record makes one name an alias of another. When a resolver reaches a CNAME, it restarts the lookup for the target name and returns the final answer for the original query. This is how www.example.com can follow a hosting service’s changing addresses without you editing anything. This tool asks Cloudflare’s public resolver for the CNAME record at the exact name you enter and shows the alias target and its TTL.
| Outcome | Message shown | Meaning |
|---|---|---|
| Alias exists | Table: Name, Points to, TTL | The name is an alias for the target |
| No alias | No CNAME record found for <name> | The name exists but has other records, or none of this type |
| Name missing | Domain does not exist (NXDOMAIN) | Nothing is published at that name |
Example inputs and what to look for
Typical inputs are a subdomain you pointed at a service: www.example.com, shop.example.com or a custom host such as docs.example.com. A good result shows one row whose Points to value matches exactly what the service told you to enter. Common mistakes are visible straight away: an extra suffix such as the domain name repeated at the end, a typo in the target, or a target that belongs to a different service. These are generic descriptions; the result is read from live DNS each time.
Why aliases cannot sit at the root
RFC 1034 requires that a name with a CNAME has no other data, but the root of a domain must hold NS and SOA records and usually has mail records too. That is why custom-domain instructions for hosting services tell you to use a CNAME for www and something else, such as address records or a provider-specific ALIAS or flattened record, for the bare domain. Looking up the bare domain here will always report no CNAME when a provider flattens it.
Following and checking the target
The lookup stops at the alias, so verification is a second step: enter the target hostname in the DNS Lookup with type A or AAAA to confirm that it has an address. If the target does not resolve, visitors get errors even though your alias is correct. Also confirm that the service still exists, since an alias to a removed service can be taken over by another party. Keep chains short; every hop is another lookup.
Limits of this check
It queries one resolver, so a change made minutes ago may not show, and the TTL displayed may be a counted-down value. It does not test HTTP or certificates, does not check that the target belongs to you, and does not expand ALIAS or flattened records, which look like ordinary address records from outside. For a quick overview of everything published at a name, run several record types in the DNS Lookup.
Learn more from an authoritative source:
MDN Web DocsTXT Record Lookup
View all TXT DNS records for a domain — including SPF, DKIM, DMARC, domain verification, and ownership tokens.
SPF Record Checker
Validate the SPF (Sender Policy Framework) record for any domain and understand its email authentication policy.
DKIM Record Checker
Look up and validate the DKIM (DomainKeys Identified Mail) public key record for a domain and selector.
DMARC Record Checker
Check and analyse the DMARC policy for any domain to understand how email authentication failures are handled.
DNS Propagation Checker
Check whether your DNS changes have propagated across Cloudflare, Google, and Quad9 resolvers worldwide.
SSL Certificate Checker
Inspect the SSL/TLS certificate for any domain — view issuer, expiry date, SANs, and days remaining.
Results are estimates for informational purposes only and do not constitute professional financial, medical, legal, or technical advice. Read full disclaimer →