A subdomain should alias to another hostname and you need to confirm the live alias value.
CNAME Lookup
Check live CNAME alias records for a domain or hostname.
Use CNAME Lookup to inspect the public alias target currently returned for a hostname, compare it with the hostname you expected to publish, and decide what to check next if the result looks wrong.
Check CNAME records before moving to A, AAAA, propagation, or HTTPS troubleshooting.
Lookup result
www.example.com
NOERROR
Type Value TTL
No CNAME records were returned for this hostname by the resolver.
What this CNAME Lookup tool does
CNAME Lookup queries the public CNAME records for a domain or hostname and returns the alias target currently visible from the resolver used by this page.
Use it to confirm whether a hostname aliases to another hostname, inspect the returned canonical target, and compare the live answer with the configuration you intended to publish.
It does not confirm whether the destination website or service is healthy. It only confirms the DNS alias layer.
When to use this tool
A platform setup asks for a CNAME record for domain verification, CDN routing, or app onboarding.
A hostname resolves unexpectedly and you need to see whether a CNAME is redirecting DNS resolution elsewhere.
You changed a CNAME recently and want to compare the live alias value with the value you intended to publish.
A website works on one network but not another and you need to confirm whether the alias chain is visible publicly.
You want a focused alias lookup before moving to A, AAAA, propagation, or HTTPS checks.
How to use CNAME Lookup
- Enter the domain or hostname you want to check.
- Run the lookup to request public CNAME answers from a recursive resolver.
- Review the returned canonical target, TTL, and response status.
- Compare the live alias target with the hostname you expected to publish.
- If the result is wrong or missing, continue to A, AAAA, propagation, or nameserver checks.
How to interpret CNAME results
CNAME record found
Likely meaning: Public DNS returned a canonical hostname value for the hostname.
Common causes: This usually means the host is configured as an alias and the recursive resolver can see that alias record.
Next action: Compare the returned hostname value with the hostname or service endpoint you intended to publish.
No CNAME record found
Likely meaning: The hostname did not return a CNAME answer.
Common causes: The host may use direct A or AAAA records instead, the CNAME may be missing, or the query may be against the wrong name.
Next action: Check DNS Lookup for other record types, then confirm the exact hostname and zone.
Unexpected alias value
Likely meaning: The hostname aliases somewhere, but not to the hostname you expected.
Common causes: Common causes are stale DNS, provider-side misconfiguration, old onboarding records, or edits made in the wrong DNS provider.
Next action: Compare the live alias value with the intended configuration, then check propagation and nameservers.
CNAME chain or indirect resolution
Likely meaning: The alias points to another hostname, which may then resolve through A or AAAA records elsewhere.
Common causes: This is common with SaaS onboarding, CDNs, and managed hosting platforms.
Next action: Follow up with DNS Lookup or A/AAAA Record Lookup on the returned hostname.
NXDOMAIN
Likely meaning: The queried hostname does not exist in public DNS.
Common causes: Typos, missing subdomains, unpublished records, or the wrong zone are common causes.
Next action: Verify the exact hostname, then check nameservers and propagation.
SERVFAIL
Likely meaning: The recursive resolver could not complete the lookup successfully.
Common causes: This often points to DNSSEC failure, broken delegation, or upstream nameserver issues.
Next action: Run NS Lookup and DNSSEC Check next, then compare recursive results with propagation checks.
Common DNS issues this tool helps uncover
CNAME published with the wrong hostname value
Alias record created in the wrong DNS provider or wrong zone
Expected CNAME missing because the host uses direct A or AAAA records instead
SaaS verification or onboarding hostname changed and the old alias was left in place
Public resolvers still returning an older alias value during propagation
CNAME present on the wrong hostname label
Delegation or authoritative nameserver mismatch after DNS migration
Next steps after CNAME Lookup
Check A and AAAA records
If a CNAME value looks right, inspect the destination hostname to see where it finally resolves.
Check DNS propagation
If the alias was changed recently, compare how recursive resolvers are seeing it.
Verify nameservers
If the alias value looks wrong, confirm which DNS provider is authoritative for the zone.
Move to website checks
If the alias looks correct, continue to HTTPS Check or TLS Certificate Check.
Related tools
DNS Lookup
Query A, AAAA, CNAME, TXT, and other DNS records for a domain.
A Record Lookup
Check IPv4 A records for a domain or hostname.
AAAA Record Lookup
Check IPv6 AAAA records for a domain or hostname.
DNS Propagation Check
Verify whether recent DNS changes are visible across resolvers.
NS Lookup
Check authoritative name servers and delegation for a domain.
HTTPS Check
Verify HTTPS availability, response chain, and TLS handshake basics.
CNAME Lookup FAQ
What does CNAME Lookup check?
It checks the live public CNAME record for a domain or hostname and returns the canonical hostname currently published in DNS.
What input should I enter?
Enter a domain or hostname such as www.example.com, app.example.com, or verify.example.com. Do not enter a full URL.
Why does no CNAME record appear?
The hostname may use direct A or AAAA records instead, the alias may be missing, or you may be checking the wrong hostname label.
What should I check after CNAME Lookup?
Usually the next step is DNS Lookup or A/AAAA Record Lookup on the returned target, then propagation or HTTPS checks if needed.
Why does the returned target not match my expected provider hostname?
This often points to stale DNS, the wrong DNS provider, an old onboarding target, or edits made in the wrong zone.
How is CNAME Lookup different from DNS Lookup?
CNAME Lookup is focused only on alias records. DNS Lookup is broader and can inspect A, AAAA, CNAME, MX, TXT, NS, and other record types.