CNAME Record Lookup - Free Online Checker

This CNAME record lookup shows the CNAME records for any domain or subdomain, including the host, the target it points to and the TTL. It also traces the full resolution chain to the final IP address. Site owners, developers and SEOs can use it to verify aliases for CDNs, hosting platforms and custom domains.

What Is a CNAME Record in DNS?

A CNAME (canonical name) record is a DNS record that makes one hostname an alias of another hostname. It holds a target name instead of an IP address, and resolvers look up that target to find the real address.

Every result has three parts: the host (the alias you queried), the target (the canonical name it points to) and the TTL (time to live, in seconds, which tells resolvers how long they may cache the answer). In zone file format, a record looks like this: shop.example.com. 300 IN CNAME stores.hosting-example.net.

CNAME Record vs A Record

An A record maps a name straight to an IPv4 address, while a CNAME maps a name to another name. The table below shows when each one fits.

A CNAME adds one extra lookup step, but it saves you from editing DNS when the provider changes its IP addresses. You only maintain the alias, and the provider maintains the target. To see the address behind a name, use the A record lookup.

Where CNAME Records Are Not Allowed

A CNAME cannot sit on the root (apex) domain, because the root must carry SOA and NS records. A name that has a CNAME also cannot hold other record types such as MX or TXT. This is why CNAMEs normally live on subdomains such as www or shop.

How to Use the CNAME Record Lookup

You can check a CNAME record in a few seconds with one field and one button.

1. Type the hostname into the Domain or Subdomain field, for example www.example.com. You can also paste a full URL, and the hostname is pulled out for you.
2. Use a subdomain, not the bare root domain. The hint under the field reminds you that CNAME records usually exist on names like www.example.com or shop.example.com.
3. Click Lookup CNAME Records. The button changes to a short waiting message while the query runs.
4. Read the line that says how many CNAME records were found for your hostname, then check the Host, Target and TTL columns.
5. Scan the Resolution Chain below the table to follow each hop from your hostname to the final IP address.

Worked Example: Tracing a CDN Alias

Say you set up a CDN and pointed blog.example.com at it. You enter that hostname and click the button. The tool reports one CNAME record found.

• Host: blog.example.com
• Target: edge.cdn-provider.net
• TTL: 300s

The Resolution Chain then lists two steps. Step 1 shows blog.example.com pointing to edge.cdn-provider.net. Step 2 shows edge.cdn-provider.net resolving to an IP address such as 203.0.113.25.

This tells you three things. The alias exists and points where you intended. The target resolves to a working IP. A TTL of 300 seconds means resolvers may keep the old answer for up to five minutes after you change it. If the target had been a typo such as edge.cdn-provder.net, the final step would show N/A instead of an IP, which is your cue to fix the record.

How to Read and Act on the Results

A healthy result has the target you expect, a sensible TTL and a final step that ends in an IP address. Here is what each part means and what to do about it.

Host and Target

The target must match exactly what your provider told you to use. Compare it character by character with the provider's setup instructions. A single wrong letter or a leftover old hostname is the most common cause of a broken alias.

TTL

TTL is shown in seconds. Common values are 300 (5 minutes), 3600 (1 hour) and 86400 (24 hours). Use a low value such as 300 before a planned migration so changes spread quickly, and raise it afterward to cut repeat lookups.

Resolution Chain

A chain occurs when a CNAME points to another CNAME. It is valid, but each extra hop adds a lookup. One or two hops is normal for CDN setups. The tool follows up to 10 hops. If you see a hostname flagged as a circular reference, two records point at each other and the name will never resolve, so remove or correct one of them.

No Records Found

The message "No CNAME records found" means the hostname probably has a direct A record, or the subdomain does not exist. If you expected an alias, log in to your DNS host and confirm the record was saved on the exact name you typed.

NXDOMAIN and Lookup Errors

An NXDOMAIN message means the DNS name does not exist at all, so check spelling and whether the subdomain was ever created. If you see a notice that the lookup was unavailable, wait a moment and try again. A message asking for a valid name means the input has a format problem, such as spaces or invalid characters.

Who Uses a CNAME Lookup, and When?

A CNAME lookup is the right check any time a hostname should be an alias for something else. These are the common situations:

• CDN setup: confirm that your assets or www subdomain point to the CDN hostname you were given.
• Custom domains on hosted platforms: verify that a store, help center or landing page subdomain points to the platform's target.
• Site migrations: compare the current target with the new one before and after you switch.
• Email and service verification: some providers ask for CNAME records to prove ownership. Check that yours were added correctly, and use the TXT record lookup when a provider asks for a TXT value instead.
• Troubleshooting a broken subdomain: find out whether the problem is the alias, a dead target or a loop.

Best Practices, Common Mistakes and Troubleshooting

Most CNAME problems come from a handful of repeat mistakes, and each has a simple fix.

• Looking up the root domain: example.com normally shows no CNAME. Query www.example.com or another subdomain instead.
• Conflicting records: if a name already has an A or TXT record, adding a CNAME to the same name can cause errors. Remove the other record first.
• Typing the wrong name: make sure the host is the full subdomain you queried, not just the label, and that you did not add the domain twice (for example www.example.com.example.com).
• Expecting instant changes: after an edit, resolvers may serve the old answer until the TTL expires. Wait, then check again, or use the DNS propagation checker to compare resolver answers.
• Long chains: if a chain runs past two or three hops, ask whether you can point straight at the final canonical name.
• Stale records: an old CNAME pointing at a service you no longer use is a clean-up item. Remove it so the subdomain cannot be claimed by someone else.

If you need every record type for a name in one view, run the DNS lookup. To see who hosts the DNS zone itself, use the NS record lookup.

Limitations and Accuracy Notes

This tool reports what public DNS returns at the moment you click the button. Your own DNS provider's dashboard may show newer changes that have not spread yet. The chain view shows the first IP address found at the end of the chain, even if the final name has several. It only reads CNAME records and does not test whether the target server actually serves your content, so a working chain does not guarantee a working website.

Use the CNAME record lookup above to check any subdomain, confirm the target and TTL, and follow the chain to its final IP. For more DNS and network checks, browse the Network & IP tools collection.