CNAME Lookup
Follow a hostname from its first alias to the final IPv4 and IPv6 addresses. Compare every authoritative server, inspect TTLs, and catch loops, broken targets, DNSSEC failures, and inconsistent answers.
- Direct authoritative queries
- Complete alias chain
- Dual-stack destination
- Same-origin analysis API
Result
CNAME result
How to read this result
- Alias hop is one CNAME pointing to the next hostname. More hops add DNS work and more places for failure.
- Terminal addresses are the A and AAAA records reached after every alias is followed. A CNAME alone does not guarantee a working destination.
- CNAME TTL is the authoritative cache lifetime configured on that hop. It is not the remaining lifetime in a resolver cache.
- Authority agreement means the delegated nameservers returned the same RCODE and canonical data. Disagreement can expose users to different results.
- DNSSEC secure means the validation chain was verified. Insecure means unsigned; indeterminate means the evidence was not sufficient.
- NODATA means the name exists but has no requested address type. NXDOMAIN means the queried name does not exist.
Alias chain
Each arrow is an authoritative CNAME record. The final box shows where address resolution ended.
Findings and next steps
Problems include the evidence behind them and a practical correction.
Terminal A and AAAA evidence
| Type | Result | Values | Endpoints | TTL range | Latency |
|---|
Authoritative server evidence
| Hop | Nameserver | Endpoint | Result | TTL | DNS time |
|---|
Delegation and DNSSEC
UDP, EDNS and TCP diagnostics
| Type | Nameserver | Endpoint | UDP | EDNS + DO | TCP |
|---|
Raw API evidence
This is the complete timestamped evidence returned by the same-origin analyzer for support tickets and independent review.