CNAME Record Lookup

Use the CNAME Record Lookup tool to check where a domain or subdomain points through a DNS CNAME record. If you are connecting a subdomain to a CDN, SaaS platform, email service, landing page builder, store platform, documentation system, or external hosting provider, this tool helps you verify whether the CNAME record is configured correctly.

A CNAME record does not point directly to an IP address. Instead, it points one hostname to another hostname. With IPMYP, you can enter a domain such as www.example.com or cdn.example.com and quickly see the canonical target, record type, and TTL returned by DNS.

If you first want to confirm the IP address currently visible from your own connection, you can check your public IP address before reviewing DNS records for a domain.

What Is a CNAME Record?

A CNAME record, short for Canonical Name record, is a DNS record that maps one hostname to another hostname. It is often used when a subdomain should behave as an alias of another domain or service endpoint.

For example, you may configure www.example.com as a CNAME that points to example.com, or configure docs.example.com to point to a hosted documentation platform.

In simple terms, a CNAME record tells DNS: “This hostname is an alias. Look up the target hostname instead.”

CNAME Record vs A Record

The main difference between CNAME and A records is what they point to.

• A Record: Points a domain or subdomain directly to an IPv4 address, such as 203.0.113.10.
• CNAME Record: Points a domain or subdomain to another hostname, such as service.example.net.

For example:

www.example.com → example.com
cdn.example.com → cdn.provider.com
app.example.com → app-hosting.provider.com

If the target hostname later changes its IP address, the CNAME alias can continue pointing to the same hostname without requiring you to manually update an IP address in multiple places.

How to Use the CNAME Record Lookup Tool

Using the IPMYP CNAME Record Lookup tool is simple and does not require command-line tools or DNS software.

1. Enter a domain or subdomain, such as www.example.com, cdn.example.com, or app.example.com.
2. Do not include http:// or https://; enter only the hostname.
3. Run the CNAME check.
4. IPMYP sends a DNS query for the hostname you entered.
5. Review the result, including the CNAME target, record type, hostname, and TTL when available.

For a broader check that includes DNS records, WHOIS, Reverse DNS, Ping, Traceroute, SSL, and other diagnostics, use the main DNS lookup tool and online network tools hub.

What Information Does a CNAME Report Show?

After running the check, the CNAME lookup report may show several important DNS details.

• Host: The domain or subdomain being checked.
• Type: The DNS record type, which should be CNAME.
• Target or Canonical Name: The hostname that the checked domain points to.
• TTL: The Time To Live value that tells DNS resolvers how long they may cache the record.

If no CNAME record exists for the hostname, the result may show that no CNAME was found. In that case, the hostname may use an A record, AAAA record, another DNS record type, or no DNS record at all.

When Should You Check a CNAME Record?

CNAME lookup is useful whenever you need to verify that a subdomain points to the correct external service, hosting endpoint, CDN, or canonical hostname.

Connecting a Subdomain to an External Service

Many SaaS tools, landing page builders, email platforms, documentation tools, store builders, and hosting services ask you to create a specific CNAME record. A CNAME check helps confirm whether the value was added correctly.

Setting Up WWW or Service Subdomains

A common use case is pointing www.example.com to another hostname. CNAME records are also common for subdomains such as cdn, app, docs, status, shop, and help.

Verifying CDN or Cloud Configuration

CDN and cloud platforms often provide a hostname that your subdomain should point to. Checking the CNAME record helps verify whether DNS is sending users to the correct provider endpoint.

Troubleshooting a Subdomain That Does Not Work

If a subdomain is not loading or a third-party service says verification failed, checking the CNAME record is one of the first steps. It helps you confirm whether the hostname exists and whether it points to the exact target required by the provider.

Can a Hostname Have Both CNAME and A Records?

In standard DNS behavior, a hostname with a CNAME record should not have other DNS records at the same exact name. That means you should not create both a CNAME and an A record for the same hostname.

For example, if www.example.com has a CNAME record, it should not also have an A record at the same hostname. Mixing records this way can cause DNS conflicts, provider errors, or inconsistent behavior.

Why Does a CNAME Not Show an IP Address Directly?

A CNAME record points to another hostname, not directly to an IP address. To find the final IP address, DNS resolvers must follow the CNAME target and then check the A or AAAA record of that target hostname.

For example, if app.example.com points to app.provider.com, the final IP address depends on the A or AAAA records of app.provider.com.

How Long Do CNAME Changes Take?

CNAME changes may appear quickly, but full visibility across the internet depends on DNS caching and TTL values. Some resolvers may update within minutes, while others may keep older records for longer.

If you recently changed a CNAME record and the service still does not work, wait for the TTL period, confirm the hostname is correct, and verify that the target value exactly matches the value required by your provider.

Common Use Cases for CNAME Lookup

• WWW setup: Check whether www.example.com points to the intended hostname.
• CDN configuration: Verify that a CDN subdomain points to the correct provider target.
• SaaS domain connection: Confirm DNS setup for hosted apps, landing pages, stores, dashboards, or documentation systems.
• Email service setup: Check CNAME records required by some email marketing or authentication services.
• Subdomain troubleshooting: Identify whether a broken subdomain points to the wrong destination.
• DNS audits: Review aliases and external service dependencies across important subdomains.

Best Practices for Managing CNAME Records

• Use CNAME records mainly for subdomains, not root domains, unless your DNS provider supports a special alias-style feature.
• Do not create other DNS records at the same hostname where a CNAME exists.
• Copy the provider’s CNAME target exactly, including spelling and dots when required.
• Check TTL values before and after DNS changes.
• Use an A record when you need to point directly to an IPv4 address.
• Remove outdated CNAME records when disconnecting old SaaS tools or third-party platforms.
• Document which subdomains depend on external providers.

Frequently Asked Questions

What does a CNAME Record Lookup do?

A CNAME Record Lookup checks whether a domain or subdomain has a CNAME record and shows the canonical target hostname it points to.

What is a CNAME record?

A CNAME record is a DNS record that maps one hostname to another hostname. It is commonly used for aliases such as www, cdn, app, docs, or service-specific subdomains.

What is the difference between CNAME and A records?

An A record points directly to an IPv4 address. A CNAME record points to another hostname, which may then resolve to an A or AAAA record.

Can I use a CNAME record for the root domain?

In standard DNS, CNAME records are usually not used at the root domain because the root domain often needs other records such as NS, SOA, MX, or TXT. Some DNS providers offer ALIAS, ANAME, or flattened CNAME-style features for root domains.

Can a hostname have both CNAME and A records?

No. A hostname with a CNAME record should not have an A record or other DNS records at the same exact hostname. Use either a CNAME or another record type, not both on the same name.

Why is my CNAME not working?

A CNAME may fail if the hostname is incorrect, the target value is misspelled, DNS cache has not expired, another conflicting record exists, or the third-party service has not verified the domain yet.

Does a CNAME redirect a website?

No. A CNAME is not an HTTP redirect. It only changes DNS resolution by pointing one hostname to another hostname. Browser redirects must be configured at the web server or application level.

Why does my provider ask for a CNAME record?

Providers use CNAME records to connect your subdomain to their infrastructure. This lets them route traffic for your custom domain to their hosted service while keeping your own domain visible to users.

Check CNAME Record Online With IPMYP

IPMYP’s CNAME Record Lookup tool gives you a fast way to check the canonical target of any domain or subdomain. Enter a hostname above, run the check, and review the DNS CNAME result to confirm where your subdomain points.