CNAME Lookup
Check CNAME records (DNS aliases) for any subdomain across 12 global resolvers. Free real-time DNS propagation checker.
What is a CNAME record?
A CNAME record ("canonical name") points one hostname to another hostname. When a resolver follows a CNAME, it then resolves the target name to get the actual IP. CNAMEs are commonly used to point custom subdomains at managed services (CDNs, SaaS apps, email providers).
When to check a CNAME
- Verifying that a custom domain is correctly pointed at a CDN or platform (Vercel, Netlify, Shopify, Cloudflare, etc.)
- Diagnosing why a SaaS connector says your domain isn't pointed correctly
- Confirming a CNAME has been removed after a migration
FAQ
Can the apex of a domain be a CNAME?
Strictly speaking, no — the DNS spec forbids CNAMEs at the zone apex (e.g., example.com itself). Some DNS providers offer "CNAME flattening," "ALIAS," or "ANAME" pseudo-records that mimic CNAMEs at the apex by resolving the target server-side and publishing the resulting A records.
Can a single hostname have a CNAME and other records?
No. The DNS rule is "if a name has a CNAME, it can't have any other records." That's why mail-record (MX) configuration on apex domains can't coexist with CNAMEs.
All record-type lookups
WhereIsDNS has dedicated pages for each common DNS record type. Each one defaults the tool to that record type and includes background on what the record means and what to look for.
- A Record Lookup — IPv4 addresses for a hostname
- AAAA Record Lookup — IPv6 addresses for a hostname
- MX Record Lookup — Mail servers for a domain (with priorities)
- NS Record Lookup — Authoritative nameservers for a domain
- TXT Record Lookup — SPF, DKIM, DMARC, and other text records
- SOA Record Lookup — Authority metadata for a DNS zone
- CAA Record Lookup — Which CAs may issue certs for the domain
- PTR (Reverse DNS) Lookup — Reverse DNS — IP back to a hostname
- Home (defaults to A records)