Reachability · Alias inspection
Alias trace
Inspect alias chains when a hostname points to another service.
Open the workspace with the right preset
This page keeps the explanation narrow and the action obvious: enter the target, run the preset check, then inspect the full workspace with the right tab context.
This entry point keeps the same DNS workspace but preloads the record family that matches this diagnostic path.
The lookup form preselects the record type below so the first result screen is already aligned with this use case.
Use one of these targets if you want to validate the flow quickly before testing a real hostname or IP.
You are not losing any resolver, propagation, health, registration, or developer views. This tool only gets you into the right context faster.
What this tool gives you
Same workspace, narrower starting point
The sections below explain what this preset optimizes, why you would choose it first, and what stays available after the scan.
When to use it
CNAME
Inspect alias chains when a hostname points to another service.
What you get
Reachability
Trace alias chains and see whether providers agree on canonical answers.
After the scan
The full diagnostic workspace still opens
You are not losing any resolver, propagation, health, registration, or developer views. This tool only gets you into the right context faster.
Google, Cloudflare, and Quad9 still run in parallel once the workspace opens.
DNSSEC, SPF, DMARC, CAA, TTL consistency, and other checks remain available.
RDAP or WHOIS fallback, nameservers, events, and export actions stay in the same flow.
Examples
CNAME
Use one of these targets if you want to validate the flow quickly before testing a real hostname or IP.
Quick checks
Narrow the lookup
Switch straight to a specific record family.