CNAME lookup. The alias chain.
Type a hostname. The tool follows every CNAME hop until it reaches a terminal A or AAAA record. Catches alias loops, missing terminal records, and the over-deep chains that trigger DNS resolver timeouts.
Type a hostname. The tool walks every CNAME hop until it reaches a terminal A or AAAA record. Catches loops + missing terminals. Same data as dig CNAME + chained recursion.
Use a sub-domain like www.* or app.* — apex domains usually have A/AAAA, not CNAME.
// no query yet
Sources used by this tool
- RFC 1034 — DNS concepts (CNAME spec)
- Cloudflare CNAME flattening (apex CNAME workaround)
- Standard limit: 8 hops before resolver refusal. Aim for ≤2 hops in practice.
Privacy: queries go to Cloudflare DoH; Digital Heroes doesn't log.
Six questions users ask.
What is a CNAME record?
CNAME (Canonical Name) is a DNS alias pointing one hostname at another hostname. SaaS providers use CNAMEs to connect custom domains.
Can CNAMEs chain?
Yes. Each hop adds latency. Standard limit is 8 hops; aim for ≤2 in practice.
What's a CNAME loop?
A CNAME pointing back at one of its own predecessors. Resolvers detect and refuse, returning NXDOMAIN.
Why does the apex refuse CNAMEs?
RFC 1034 disallows it because apex has implicit SOA + NS records. Use ALIAS/ANAME or 301 redirect to www.
CNAME or A record?
CNAME for SaaS-hosted (Vercel, Netlify, etc.). A record for direct-hosted with stable IP.
Does this tool log my queries?
Digital Heroes doesn't log. Cloudflare DoH logs anonymized queries per their privacy policy.