CNAME Lookup
Type a hostname such as www.example.com to see its CNAME record, the alias that hands the name to another one, and the whole chain behind it: each hop with its TTL, then the IPv4 and IPv6 addresses the last name answers with. On 6 November 2026 www.github.com was a single hop to github.com, while www.apple.com passed through 3 names to an Akamai edge server. If the chain ends at a name that no longer exists, the lookup flags a dangling CNAME, the setup behind most subdomain takeovers. The root of a domain cannot have a CNAME, so a bare domain shows its own addresses instead.
Free, no sign-in, 20 lookups a minute. Answers are cached for 5 minutes. Also: DNS lookup, MX lookup, Nameserver lookup, TXT record lookup, SPF record checker, DMARC checker, DKIM checker, DNS propagation checker, reverse DNS lookup, MTA-STS checker, BIMI checker, email deliverability checker.
Where well-known www names point
Looked up on November 6, 2026 through Cloudflare's resolver, the same one this tool asks. Click a domain to run it live.
| Hostname | Hops | Points to | Ends at | A / AAAA |
|---|---|---|---|---|
| www.github.com | 1 | github.com | github.com | 1 / 0 |
| www.apple.com | 3 | www-apple-com.v.aaplimg.com | e6858.dsce9.akamaiedge.net | 1 / 2 |
| www.microsoft.com | 2 | www.microsoft.com-c-3.edgekey.net | e13678.dscb.akamaiedge.net | 1 / 3 |
| www.amazon.com | 2 | tp.47cf2c8c9-frontier.amazon.com | cf.47cf2c8c9-frontier.amazon.com | 1 / 2 |
| www.cnn.com | 1 | cnn-tls.map.fastly.net | cnn-tls.map.fastly.net | 4 / 4 |
| www.shopify.com | 0 | no CNAME | 2 / 0 |
www.apple.com and www.microsoft.com hand off to Akamai, www.cnn.com to Fastly. www.amazon.com sent IPv4 and IPv6 through different hops. www.shopify.com has no CNAME at all.
CNAME Lookup questions
What is a dangling CNAME?
A CNAME whose target was deleted: a subdomain still points at a cloud app, storage bucket or hosted page its owner shut down. If the service lets anyone claim that name again, an attacker claims it and serves their own content on your subdomain, under your domain's name and cookies. That is a subdomain takeover, and the fix is to delete the CNAME when you delete what it points to. This lookup flags a chain whose last name answers NXDOMAIN; a target that still exists but shows a provider's "no such app" page needs a check in a browser.
When should I use a CNAME instead of an A record?
Use a CNAME when someone else runs the server and may change its address: a CDN, a store platform, GitHub Pages or a help desk gives you a name to point at, and the CNAME keeps working when their IPs change. Use A and AAAA records when you control the addresses, and always at the root of a domain. On 6 November 2026 www.cnn.com was a CNAME to Fastly, while www.shopify.com answered with plain A records.
Can a CNAME point to another CNAME?
Yes, and large sites chain them: www.microsoft.com went through 2 hops and www.apple.com through 3 before reaching an address on 6 November 2026. Each hop is one more name a resolver must look up before the page loads (then caches for its TTL), and resolvers stop following after a limit, so keep your own chains short. Pointing at a CDN's name and letting the CDN add its own hops is normal.
Why can't I add an MX or TXT record next to a CNAME?
A CNAME says the whole name is an alias, so it may not carry any other record (RFC 1034 3.6.2, RFC 2181 10.1): a resolver asking for its MX or TXT follows the CNAME to the target instead. If help.example.com is a CNAME, it cannot also take a verification TXT or receive mail; use another name for those, or replace the CNAME with A records.
More free domain tools
The DNS lookup shows every record a domain publishes. The MX lookup shows which servers take a domain's email and who runs them. The Nameserver lookup shows a domain's nameservers and which company hosts its DNS. The TXT record lookup reads a domain's SPF and DMARC records. The SPF record checker validates a domain's SPF record and counts its DNS lookups against the limit of 10. The DMARC checker reads a domain's DMARC policy, reports and alignment, and flags what weakens it. The DKIM checker finds a domain's DKIM keys among 22 common selectors and checks each key's size. The DNS propagation checker shows whether 15 resolvers around the world return the same answer after a change. The reverse DNS lookup finds the hostname (PTR record) behind an IP address and checks that it resolves back. The MTA-STS checker fetches a domain's MTA-STS policy and checks that it covers every mail server. The BIMI checker checks a domain's BIMI record, SVG Tiny PS logo, mark certificate and whether DMARC lets the logo show. The email deliverability checker runs every DNS check that decides whether a domain's mail is trusted, with the failures first. For the website itself, the redirect checker follows a URL through every 301, 302, 307 and 308 to the page that answers, the HTTP header checker shows the response headers a URL sends and grades its six security headers and the website down checker checks from outside your network whether a site answers, and how fast. For who registered a name and when, use the WHOIS lookup, Domain age checker or Domain expiration checker. See which extensions a name is still free in with the domain availability checker, or price one in the domain value calculator.