What this check shows
A CNAME record makes one hostname an alias of another hostname. It is commonly used for CDNs, SaaS verification, hosted applications and service migrations.
DNSRadar compares the canonical target returned by each resolver so you can detect an old target, a missing alias or inconsistent provider configuration.
When to use it
- CDN and SaaS onboarding
- Changing an application hostname
- Verifying third-party service aliases
- Diagnosing stale CNAME targets
How to read the result
- The target is a hostname and must resolve through its own A or AAAA records.
- A CNAME normally cannot coexist with other record types at the same owner name.
- Different targets across resolvers usually indicate cached data or inconsistent authoritative servers.
Command examples
Use these dig commands when you need to compare DNSRadar with a terminal check or collect evidence for a DNS provider.
dig www.example.com CNAME +short
dig @1.1.1.1 www.example.com CNAME
dig www.example.com A +traceQuestions
Can a root domain use a CNAME?
Traditional DNS rules do not allow a CNAME at the zone apex when other required records exist; some providers offer ALIAS or ANAME behavior instead.
Why does the CNAME resolve but the website fail?
The target may resolve correctly while TLS, HTTP routing or the target service itself is misconfigured.
Related DNS tools
Check DNS records worldwide across independent public resolvers for A, AAAA, CNAME, MX, TXT, NS, SOA, PTR, SRV and CAA answers.
Check DNS propagation worldwide and compare record values, status and latency across independent global DNS resolvers.
Run a global A record lookup to check IPv4 addresses, TTL values and propagation across independent DNS resolvers.
Check AAAA records worldwide to verify IPv6 addresses, propagation, TTL behavior and resolver differences before or after a dual-stack change.
Check MX records worldwide, compare mail server hostnames and priorities, and diagnose email delivery or migration issues across global DNS resolvers.
Check TXT records worldwide for SPF, DKIM, DMARC and domain verification, and compare long DNS text values across independent resolvers.