🔗

CNAME Record Lookup

A Canonical Name (CNAME) record maps one domain name (an alias) to another (the canonical name).

RFC: RFC 1034
TYPE: Resource Record
TARGET: Must be a Domain Name

What is CNAME Record Lookup?

A CNAME record provides an alias for another domain name. It essentially tells resolvers, "If you are looking for this domain, look over there instead." It is often used to alias a subdomain to a root domain.

How it Works

When a DNS resolver queries a CNAME record, it receives the canonical domain name. The resolver must then perform a second query to look up the A/AAAA records of the newly returned canonical name.

Key Use Cases

Aliasing "www.example.com" to the root "example.com".

Pointing a custom domain to a SaaS service (e.g., Shopify, GitHub Pages).

Consolidating service endpoints so IP addresses only need updating in one root location.

Advanced Details

A CNAME record CANNOT be placed at the root (apex) of a domain (e.g., directly on "example.com"). It also cannot co-exist with any other DNS records (like MX or TXT) on the same hostname.

Cybersecurity Pros & Cons

Security Advantages
  • Centralises security updates — patching the canonical target propagates protection to all CNAME aliases.
  • Simplifies certificate management when multiple branded subdomains point to one secured canonical host.
  • CNAME chain analysis is a vital OSINT technique for discovering shadow IT and third-party dependencies.
Security Limitations
  • Dangling CNAME records pointing to decommissioned services are a primary vector for subdomain takeover attacks.
  • Long CNAME chains increase attack surface — each intermediate hop is a potential interception point.
  • CNAME to third-party CDNs introduces supply-chain trust dependency; a compromised CDN affects all aliases.
  • Security scanners may miss vulnerabilities on the actual server if they only resolve the CNAME alias surface.
Ready to Test?

Use our professional-grade tool to perform a real-time check for this module.

Run Module Now
Related Docs