CNAME Lookup — CNAME Records for Any Domain

Returns the canonical alias target and TTL (seconds) for any domain or subdomain, via Google, Cloudflare, Quad9, OpenDNS, or authoritative name servers.

More Tools

CNAME Lookup — What Is a CNAME Record?

A CNAME (Canonical Name) record, defined in RFC 1035, maps an alias domain name to a canonical domain name rather than directly to an IP address. When a DNS resolver encounters a CNAME record, it restarts the lookup using the canonical name as the new query target, continuing until a domain with an A or AAAA record is reached. CNAME records are used for subdomains and third-party service integrations — CDN endpoints, SaaS platforms, and email infrastructure — allowing IP addresses to change without requiring DNS updates to every aliased subdomain.

Fact	Value
RFC Standard	RFC 1035 (defined 1987), RFC 2181 § 10.1 (restrictions clarified)
Record Format	Alias name → Canonical domain name (not an IP address)
Allowed at zone apex	No — cannot coexist with SOA or NS records at the root domain per RFC 1035
Points to IP address directly	No — must ultimately resolve to an A (IPv4) or AAAA (IPv6) record
Maximum CNAME chain depth	8–10 hops (resolver-dependent); chaining is discouraged per RFC 2181
Coexists with other record types	No — exclusive at its owner name (DNSSEC records excepted)

How to Use the CNAME Lookup Tool

Find the canonical name alias for any domain or subdomain in seconds.

Enter a Domain or Subdomain

Enter the domain or subdomain whose CNAME record you want to check — for example, www.example.com or mail.company.com.

Select a DNS Resolver

Choose a resolver from the dropdown. Select Authoritative DNS to query the domain's own name servers directly, bypassing any recursive cache.

Run the Lookup

Click "Lookup CNAME Record" to send the query via UDP to the selected resolver.

Read the Canonical Target

The result shows the canonical name the alias resolves to and its TTL in seconds — how long downstream resolvers cache this record before re-querying.

Trace the Full Resolution Chain

Use the canonical target hostname in DNS Lookup to retrieve its A or AAAA record and trace the complete resolution chain to an IP address.

What Do CNAME Lookup Results Mean?

Field	Meaning	Example
DNS Record Type	Always CNAME — the canonical name record type as defined in RFC 1035	CNAME
DNS Record Value	The canonical domain name this alias resolves to — the next target in the DNS chain	company.pages.dev
TTL (seconds)	Time-to-live — how long DNS resolvers cache this record before re-querying the authoritative server	300 (5 minutes)

The canonical target returned is not necessarily the final destination. If the target domain has its own CNAME record, the resolution chain continues until a domain with an A or AAAA record is reached. Use DNS Lookup on the returned target to trace the full chain.

How CNAME Lookup Works

CNAME records were defined in RFC 1035 (1987) as a core DNS resource record type. When a resolver returns a CNAME in response to a query, DNS clients are required to restart resolution using the canonical name as the new query target. This process — CNAME chasing — continues until the chain terminates at a domain with an A or AAAA record that maps to an IP address.

RFC 2181 (section 10.1) clarified the key restriction: a name with a CNAME record cannot coexist with any other DNS record type at the same owner name, with the exception of DNSSEC records (RRSIG, DNSKEY). This is the reason CNAME records cannot be placed at the zone apex — the root domain always carries SOA and NS records, making a coexistent CNAME a protocol violation. DNS providers work around this restriction using proprietary ALIAS or ANAME records, which are not part of the DNS standard.

This tool sends UDP queries via dnsjava directly to the selected resolver — Google (8.8.8.8), Cloudflare (1.1.1.1), OpenDNS (208.67.222.222), Quad9 (9.9.9.9), or Yandex (77.88.8.8) — with no caching, so results reflect the live state of the DNS record. Authoritative DNS mode first queries Google 8.8.8.8 to discover the domain's NS records, then queries each authoritative name server directly to return an answer untouched by recursive resolvers.

Do it yourself

How to Run a CNAME Lookup Without an Online Tool

All major operating systems include command-line DNS tools that can query CNAME records directly. The online tool queries from a neutral external resolver — results may differ from your local resolver due to caching or split-horizon DNS configuration.

Windows Command Prompt

nslookup -q=CNAME www.example.com
nslookup -q=CNAME www.example.com 8.8.8.8
nslookup -q=CNAME mail.example.com 1.1.1.1

Use -q=CNAME to restrict the query to canonical name records only. Append a resolver IP after the domain name to specify which DNS server to query.

Windows PowerShell

Resolve-DnsName www.example.com -Type CNAME
Resolve-DnsName www.example.com -Type CNAME -Server 8.8.8.8
Resolve-DnsName mail.example.com -Type CNAME -Server 1.1.1.1

Mac / Linux dig

dig www.example.com CNAME
dig www.example.com CNAME @8.8.8.8
dig www.example.com CNAME @1.1.1.1

dig returns the full DNS response including TTL, response flags, and the authority section — making it the preferred tool for diagnosing CNAME chains. On macOS, dig is pre-installed. On Ubuntu/Debian, install with apt install dnsutils.

Common Uses for CNAME Lookup

CDN integration verification. A DevOps engineer deploys a web application on Cloudflare Pages and configures www.company.com with a CNAME pointing to company.pages.dev. After updating the CDN configuration, CNAME lookup confirms the canonical target has propagated and the TTL is short enough for fast failover if the CDN endpoint changes.

Third-party SaaS onboarding. A marketing team provisions a help center at support.company.com by pointing it to a CNAME target provided by their helpdesk platform. CNAME lookup confirms the record is live and resolves to the platform's edge hostname before routing production traffic to the subdomain.

Email DKIM delegation. A sysadmin configures DKIM authentication by adding a CNAME record at mail._domainkey.company.com, delegating cryptographic key management to the email provider's infrastructure. CNAME lookup verifies the record resolves to the correct provider target before enabling the DKIM signing policy and testing delivery.

Frequently Asked Questions

What is a CNAME record and what does it do?

A CNAME (Canonical Name) record, defined in RFC 1035, maps an alias domain name to a canonical domain name rather than directly to an IP address. When a DNS resolver encounters a CNAME, it restarts the resolution process using the canonical name as the new query target — a process called CNAME chasing. CNAME records are used for subdomains and third-party service integrations such as CDN endpoints, SaaS platforms, and email infrastructure.

What is the difference between a CNAME record and an A record?

An A record maps a domain name directly to an IPv4 address. A CNAME record maps an alias domain name to another domain name — not to an IP address. CNAME resolution requires at least one additional DNS lookup to follow the alias to its canonical name's A or AAAA record. Per RFC 1035, a name with a CNAME record cannot coexist with any other DNS record type at the same owner name, which is why CNAME records cannot be placed at the zone apex.

Why is my CNAME lookup returning no result?

If no CNAME record is returned, the queried name likely does not have one configured. Root domains (example.com) use A records directly — CNAME records cannot be placed at the zone apex because RFC 1035 requires SOA and NS records there, and a CNAME cannot coexist with other record types at the same name. Verify you are querying a subdomain (www.example.com, mail.example.com) rather than the root domain, and select the Authoritative DNS resolver to confirm the record's live state independent of recursive cache.

How current is the CNAME data this tool returns?

Results are fetched live from the selected DNS resolver via UDP with no caching applied. The TTL value in the result indicates how long downstream resolvers cache the record — a TTL of 300 means the record refreshes every 5 minutes. For the most authoritative result, select Authoritative DNS, which queries the domain's own primary name servers directly rather than a recursive public resolver.

Can a CNAME record point to another CNAME record?

Technically yes — a CNAME can point to another CNAME, creating a chain. RFC 2181 section 10.1 discourages CNAME chains because each hop requires an additional DNS lookup, increasing resolution latency for every client that accesses the domain. Most resolver implementations cap chain depth at 8 to 10 hops to prevent infinite loops. Best practice is a single CNAME pointing directly to the canonical domain that holds the A or AAAA record.

Do you store or log the domains I look up?

CNAME queries are processed in real time and not stored or logged. The domain name you enter is sent to the selected DNS resolver and discarded immediately after the response is returned. No query history is retained.

Related Guides

Guide What Is an IP Address?

CNAME records do not hold IP addresses directly; the alias chain must ultimately resolve to an A or AAAA record. Understanding IP addresses explains what the final CNAME resolution returns and why the lookup involves multiple DNS queries.

Guide What Is IPv4?

IPv4 A records are the most common target at the end of a CNAME chain. Understanding the IPv4 address format clarifies how CNAME aliases ultimately resolve to routable network addresses.