CNAME Lookup - Check DNS Alias Records
No logs stored • Server-side processing
Find canonical names and DNS aliases for any domain. Verify CNAME configuration for CDNs, subdomains, and hosting services. See where your domain aliases point.
Free Online CNAME Record Checker
Enter a domain above to get started
We'll show you A, AAAA, MX, CNAME, TXT, NS, SOA, and CAA records
What is a CNAME Record?
A CNAME (Canonical Name) record creates an alias from one domain name to another. Instead of pointing directly to an IP address like A records, CNAMEs point to another domain name. For example, 'www.example.com' might be a CNAME pointing to 'example.com', meaning both resolve to the same destination. CNAMEs are essential for subdomains, CDN configurations, and SaaS integrations.
What You'll Discover
Can Find
- CNAME records showing which domain a hostname aliases to
- TTL values in human-readable format (5m, 1h, 24h)
- CDN provider identification from CNAME targets
- DNSSEC status (signed or unsigned)
- All 8 DNS record types via tabs (A, AAAA, MX, TXT, NS, SOA, CAA)
Cannot Find
- CNAME for root domains (not allowed per DNS standards)
- Full CNAME chains in one lookup (query each hop separately)
- Real-time DNS propagation status (use DNS Checker)
- Historical CNAME record changes
How to Check CNAME Records
Find canonical names and DNS aliases in seconds
Enter the Hostname
Type the subdomain or hostname to check (e.g., www.github.com, blog.example.com). Note: Root domains cannot have CNAME records per DNS standards.
Click Lookup
We query DNS servers to retrieve all CNAME records plus 7 other record types. Results show the canonical name your hostname aliases to.
View Canonical Name
See which domain this hostname is an alias for, with TTL value. Identify CDN providers like Cloudflare, AWS CloudFront, Fastly from the CNAME target.
Check Final Destination
Switch to the A tab to see the final IPv4 address that the CNAME chain resolves to. This completes the full DNS resolution path.
Understanding Your CNAME Lookup Results
What each field in your CNAME records reveals
Canonical Name
The target domain name that this hostname is an alias for. This is where DNS resolution continues. For example, if www.example.com has a CNAME of example.com, the canonical name is 'example.com'.
example.com
TTL (Time To Live)
How long DNS resolvers cache this CNAME before checking for updates. We display TTL in human-readable format: '5m' = 5 minutes, '1h' = 1 hour, '24h' = 24 hours. Lower TTL means faster propagation of changes.
1h (3600 seconds)
CDN/Service Provider
CNAME targets reveal which services a domain uses. Look for patterns like *.cloudflare.net (Cloudflare), *.cloudfront.net (AWS CloudFront), *.fastly.net (Fastly), *.netlify.app (Netlify), *.vercel-dns.com (Vercel), *.github.io (GitHub Pages).
cdn.cloudflare.net
DNSSEC Status
Whether the domain has DNSSEC (DNS Security Extensions) enabled. DNSSEC adds cryptographic signatures to prevent spoofing and cache poisoning. Green indicator = enabled with DNSKEY and DS records.
Enabled ✓
Response Time
Time taken to query and return DNS records. Cached queries are faster (< 50ms) than fresh lookups (< 500ms). CNAME adds one extra resolution hop compared to A records.
145ms
Why Choose Our CNAME Lookup Tool
More than just CNAME records—complete DNS visibility
CNAME Focused
Opens directly on the CNAME records tab for instant alias visibility. No hunting through menus—see canonical names immediately.
CDN & Service Detection
Identify CDN providers (Cloudflare, CloudFront, Fastly) and hosting services (Netlify, Vercel, GitHub Pages, Heroku) from CNAME target patterns.
8 DNS Record Types
CNAME is the default, but A, AAAA, MX, TXT, NS, SOA, and CAA are available via tabs. Follow the full resolution chain from CNAME → A → IP.
Human-Readable TTL
TTL values displayed as '5m', '1h', '24h' instead of confusing seconds. Instantly understand cache duration without mental math.
One-Click Copy
Click any canonical name to copy it to your clipboard instantly. Perfect for pasting into DNS configurations or documentation.
Export to JSON/CSV/TXT
Download your CNAME lookup results in multiple formats. JSON for APIs and automation, CSV for spreadsheets, plain text for documentation.
When You Need CNAME Lookup
Common scenarios where checking CNAME records is essential
CDN Verification
Confirm your domain is properly configured to use CDN services. Check that www.yoursite.com points to *.cloudflare.net, *.cloudfront.net, or your CDN's domain.
Subdomain Configuration
Verify subdomains (www, blog, shop, app) point to correct destinations. Common for multi-site architectures and third-party service integrations.
Service Migration
Check CNAME changes when switching hosting providers, CDNs, or SaaS platforms. Verify the new target is correct before and after migration.
Domain Verification
Many services (SSL providers, email platforms, SaaS tools) require adding a CNAME for verification. Confirm your verification CNAME is correctly configured.
How CNAME Records Work
Understanding CNAME records helps you manage subdomains, CDN configurations, and DNS efficiently.
CNAME vs A Record
A records point directly to an IPv4 address (e.g., 93.184.216.34), while CNAME records point to another domain name (an alias). CNAME adds one extra DNS lookup step: browser queries CNAME → gets target domain → queries target's A record → gets IP address. Use A records for root domains and CNAMEs when the target IP might change (CDN, SaaS). Major benefit: when the target updates its IP, all CNAMEs automatically resolve to the new IP.
Why Root Domains Can't Have CNAME
DNS standards (RFC 1912) prohibit CNAME records on root domains (example.com without www). This is because CNAME records can't coexist with other record types at the same name, but root domains need MX records for email and NS records for nameservers. Workarounds: Use A/AAAA records for root domain, or use ALIAS/ANAME records (a non-standard extension supported by some DNS providers like Cloudflare's 'CNAME Flattening').
CNAME Chaining
CNAME records can point to other CNAMEs, creating a chain. Example: www.shop.com → shop.myshopify.com → shops.myshopify.com → IP. While valid, each hop adds latency to DNS resolution. Our tool shows the first target; to see the full chain, query each target separately. Most CDNs and SaaS platforms create short chains (1-2 hops) for performance.
Common CNAME Patterns
CDN providers: *.cloudflare.net (Cloudflare), *.cloudfront.net (AWS), *.fastly.net (Fastly), *.akamaiedge.net (Akamai). Hosting platforms: *.netlify.app, *.vercel-dns.com, *.github.io, *.herokuapp.com. E-commerce: *.shopify.com, *.squarespace.com. Email services: *.mailchimp.com, *.sendgrid.net. Recognizing these patterns helps identify what services a domain uses.
CNAME Lookup Specifications
- Record Types
- CNAME (default), A, AAAA, MX, TXT, NS, SOA, CAA
- Output Format
- Canonical name without trailing dot
- CDN Detection
- 15+ providers recognized
- TTL Display
- Human-readable (5m, 1h, 24h) + seconds
- DNSSEC Detection
- DNSKEY and DS record checking
- Response Time
- < 500ms (cached: < 50ms)
- Cache Duration
- 5 minutes (300 seconds)
- Export Formats
- JSON, CSV, Plain Text
- API Access
- REST API at /api/v1/dns-lookup
Frequently Asked Questions
What is a CNAME record?
A CNAME (Canonical Name) record creates an alias from one domain name to another. Instead of pointing to an IP address like A records, CNAMEs point to another domain name. For example, 'www.example.com' might be a CNAME pointing to 'example.com'. When you visit www.example.com, DNS first resolves the CNAME to example.com, then resolves that domain's A record to get the IP.
What is the difference between CNAME and A record?
A records point directly to an IPv4 address (e.g., 93.184.216.34), while CNAME records point to another domain name (an alias). Use A records for root domains and when you need to specify an exact IP. Use CNAMEs for subdomains, CDN setup, and when you want changes in the target to automatically propagate. CNAMEs cannot coexist with other record types at the same hostname.
Why does my root domain show no CNAME records?
Root domains (like example.com without www) cannot have CNAME records according to DNS standards (RFC 1912). This is because CNAME records can't coexist with MX or NS records, which root domains require. For root domains, use A/AAAA records, or use ALIAS/ANAME records if your DNS provider supports them (Cloudflare calls this 'CNAME Flattening').
How do I verify my CDN CNAME is configured correctly?
Look up your subdomain (e.g., www.yoursite.com). If your CDN is configured correctly, the CNAME should point to your CDN provider's domain: *.cloudflare.net for Cloudflare, *.cloudfront.net for AWS CloudFront, *.fastly.net for Fastly, *.netlify.app for Netlify, *.vercel-dns.com for Vercel.
Can I see the final IP address after the CNAME?
Yes! Our tool shows all 8 DNS record types. After viewing the CNAME (which shows the alias target), click the 'A' tab to see the IPv4 address that the chain ultimately resolves to. This lets you follow the complete DNS resolution path: CNAME → target domain → A record → IP address.
What is an example of a CNAME?
A common example is www.github.com, which is a CNAME pointing to github.com. Another example: blog.yoursite.com might point to yoursite.ghost.io if you're using Ghost for blogging. CDN setups often look like: cdn.yoursite.com → d1234567890.cloudfront.net (AWS CloudFront).
What is CNAME verification?
Many services require CNAME verification to prove domain ownership. You add a specific CNAME record (like _acme-challenge.example.com or _dmarc.example.com), and the service checks for it. This is common for SSL certificate issuance (ACME/Let's Encrypt), email authentication (DKIM), and SaaS platform custom domains.
Why is my CNAME not working?
Common causes: 1) DNS propagation not complete—wait 24-48 hours or use DNS Checker. 2) Typo in the target domain name. 3) CNAME on root domain (not allowed). 4) Conflicting record types at the same hostname. 5) TTL cache on your device—try flushing DNS. 6) Wrong DNS zone edited (registrar vs hosting provider).
What is CNAME chaining?
CNAME chaining occurs when a CNAME points to another CNAME. Example: www.shop.com → shop.myshopify.com → shops.myshopify.com → IP address. While valid, each hop adds latency. Our tool shows the first target; to see the full chain, query each subsequent target separately. Most CDNs keep chains short (1-2 hops).
How long does CNAME propagation take?
CNAME propagation typically takes 1-48 hours depending on the previous TTL value. If the old TTL was 24 hours, some DNS servers will cache the old record for that duration. To speed up propagation, lower the TTL to 5-10 minutes 24-48 hours BEFORE making changes. Use our DNS Checker tool to monitor propagation globally.
Check Any Domain's CNAME Records Now
Enter a subdomain above to find canonical names, verify CDN configuration, and check alias records. Free, fast, no registration required.
Try Another Lookup