Free CNAME Checker — Lookup CNAME Records & Alias Chains
Instantly check any hostname's CNAME record, trace the full alias chain, and confirm the final resolution target.
Why CNAME Records Matter
What This CNAME Checker Returns
We perform a live DNS lookup and trace the complete alias chain from your hostname to its final target.
Common CNAME Use Cases
CNAME records power most modern infrastructure. Here is when you need to verify them.
CDN setup — verify your domain points to Cloudflare, Fastly, or Akamai correctly
Custom email domain — SendGrid, Mailgun, and Amazon SES all require CNAME validation records
SSL certificate issuance — ACME DNS challenges use CNAME records for domain control validation
Subdomain delegation — pointing tracking.yourdomain.com to an analytics provider
SaaS custom domains — customers using your product on their own subdomain need CNAME verification
Load balancer and health check — verifying CNAMEs before traffic cutover in production
How to Read CNAME Results
Understanding what each part of the result means helps you take the right action.
Check the Chain
The chain shows every alias hop in sequence. Step one points to step two, step two to the next, and so on. Follow the arrows to understand the full resolution path.
Verify the Final Target
The final target is the canonical hostname where an A or AAAA record ultimately lives. Confirm it matches the expected endpoint for your CDN, email provider, or SaaS.
Not Found Means No CNAME
If status is Not Found, the hostname uses an A record directly or does not exist. This is expected for root domains — only subdomains support true CNAME records.
Error Means DNS Resolution Failed
Check hostname spelling and confirm the record exists in your DNS provider's dashboard. Propagation delays (TTL) may also cause temporary failures after recent changes.
Who Uses CNAME Lookup
CNAME checking is common in development, DevOps, email, and security workflows.
Developers setting up custom domains for SaaS products
DevOps engineers verifying DNS changes before traffic cutover
Email marketers setting up sending domain CNAMEs for ESPs
Security researchers checking for subdomain takeover vulnerabilities
Domain administrators auditing DNS after infrastructure migrations
Frequently Asked Questions
What is a CNAME record?
A CNAME (Canonical Name) record maps one hostname to another hostname as an alias. Instead of pointing directly to an IP address like an A record, a CNAME says 'this hostname is an alias for this other hostname.' DNS resolvers follow the chain until they reach a record with an actual IP address.
What does this CNAME checker return?
Enter any hostname and the tool performs a live DNS query, traces the full CNAME chain (every alias hop in sequence), and returns the final target hostname. If no CNAME exists for that hostname, the tool returns a 'Not Found' status — the hostname may use an A or AAAA record directly.
Why would I need to verify a CNAME record?
CNAME verification is needed after setting up custom domains for CDNs (Cloudflare, Fastly), email providers (SendGrid, Mailgun, Amazon SES), SSL certificate issuance (ACME DNS challenges), SaaS custom domains, and subdomain delegations. Incorrect or missing CNAMEs cause service failures that are often silent and hard to diagnose without a direct DNS lookup.
What is a 'dangling CNAME' and why is it a security risk?
A dangling CNAME points to a hostname that no longer exists — for example, if you deprovisioned a service on Heroku, Azure, or AWS but left the CNAME in DNS. An attacker can register the deprovisioned service at that target hostname and take control of your subdomain. This is called subdomain takeover and is a critical security vulnerability. Use this tool to audit abandoned CNAMEs.
Can a CNAME chain have multiple hops?
blog.example.com → example.cdn-provider.net → edge.cdn-provider.com. DNS resolvers follow the chain automatically. Most resolvers limit chains to 8–10 hops to prevent infinite loops.
Can a root domain (apex) use a CNAME record?
No — the DNS specification (RFC 1912) prohibits CNAME records at the zone apex (e.g., example.com with no subdomain). This is because the apex must have SOA and NS records, which cannot coexist with a CNAME. Workarounds include ALIAS records (Route 53), ANAME records (some DNS providers), or CNAME flattening (Cloudflare). Only subdomains can have true CNAME records.
How do I set up a CNAME for SendGrid or Mailgun?
Both SendGrid and Mailgun require CNAME records for domain authentication. In SendGrid, go to Settings → Sender Authentication, add your domain, and copy the three CNAME records provided. In Mailgun, go to Sending → Domains, add your domain, and DNS records appear under 'DNS Records to Add.' Add them to your DNS provider, then use this CNAME checker to confirm they resolve correctly.
How long does it take for a new CNAME to propagate?
DNS propagation typically takes 1–15 minutes for most resolvers when TTL is set to 300 seconds (5 minutes) or lower. Legacy DNS configurations with TTLs of 3600–86400 seconds can take up to 24–48 hours to propagate globally. Use this checker immediately after making changes — if the record is not visible yet, wait for the old TTL to expire.
What is the difference between a CNAME and an A record?
An A record maps a hostname directly to an IPv4 address. A CNAME record maps a hostname to another hostname. CNAMEs are preferred when a service provider's IP addresses change frequently, as updating one CNAME target hostname updates all aliases that point to it. A records require direct IP management.
Does this tool store the hostnames I check?
No. All DNS lookups are performed in real time without retaining any hostname data after the query completes.