Start typing to search 227 tools.
CNAME Lookup
CNAME Lookup checks whether a hostname is an alias, shows its canonical target and TTL, and helps diagnose DNS redirects between hostnames.
What CNAME Lookup does
CNAME Lookup checks the canonical-name record published for a hostname and shows where that DNS alias points. It is useful when a subdomain should route through a CDN, SaaS platform, hosted service, verification endpoint, or another hostname and you need to confirm the live DNS answer.
The result is presented as a readable DNS report instead of a raw record dump. You can see whether a CNAME was found, the alias target returned by DNS, the TTL associated with the answer, and the original hostname that was checked.
How to use
Enter a hostname such as www.github.com without https://, a page path, or query parameters. Select Look Up CNAME. If a canonical-name record exists, the result shows the alias target and available TTL data. If no CNAME is published, the tool reports that clearly rather than treating a normal direct A or AAAA record as an error.
When troubleshooting a migration, compare the returned target with the exact hostname supplied by your provider. Even a small spelling difference, missing trailing domain label, or outdated provider target can prevent a service from working as expected.
Why use CNAME Lookup?
Focused controls, predictable output, and a workflow designed around this exact transformation.
See the live DNS alias target
Confirm which canonical hostname a CNAME currently points to from the resolver used by Trexmi.
Spot stale or incorrect aliases
Compare the returned target with the value required by your CDN, SaaS provider, hosting service, or verification workflow.
Review CNAME TTL context
Use the TTL as context when a recently changed alias is still appearing differently through cached DNS resolvers.
Questions about CNAME Lookup
Practical details about input, output, privacy, limits, and the best way to use this tool.
01 What does CNAME Lookup show?
It shows whether a hostname publishes a CNAME record, the canonical target returned by DNS, and available TTL information.
02 Is a CNAME the same as a redirect?
No. A CNAME is a DNS alias. HTTP redirects such as 301 and 302 happen after DNS resolution at the web-protocol layer.
03 Why does my root domain have no CNAME?
A zone apex normally needs SOA and NS records, so providers often use address records or DNS flattening instead of a traditional CNAME there.
CNAME Lookup for fast DNS alias troubleshooting
A CNAME record tells DNS that one hostname is an alias of another hostname. Instead of publishing an address directly for the alias, the resolver follows the canonical target and continues resolution there. This makes CNAME records common for www hostnames, CDNs, cloud applications, hosted storefronts, analytics endpoints, and many third-party integrations.
What a CNAME record actually does
A CNAME does not perform an HTTP redirect and it does not send a browser to another URL. It operates at the DNS layer. The alias hostname is associated with a canonical DNS name, and the resolver then obtains the address or other applicable records for that target. This distinction matters because an HTTP 301 redirect and a DNS CNAME solve different problems.
The core behavior of domain names and canonical aliases is documented in RFC 1034 and RFC 1035.
7 powerful CNAME checks before you finish
Confirm the hostname spelling, verify that a CNAME exists where expected, compare the canonical target with the provider documentation, review the TTL, check that the target itself resolves, look for an obsolete previous-provider target, and verify that the service is using the correct subdomain. These seven checks catch many common alias configuration problems quickly.
Why the root domain usually behaves differently
The zone apex normally needs records such as SOA and NS. Traditional DNS rules do not allow a CNAME to coexist at an owner name with other data, which is why providers often use ALIAS, ANAME, flattening, or provider-specific virtual records for root-domain behavior. If you are checking example.com and no CNAME is returned, that can be completely normal.
CNAME Lookup after a migration
When moving a site or service, the old alias can remain visible because recursive resolvers cache DNS answers. A correct update at the authoritative provider does not force every cache to refresh instantly. The TTL shown by CNAME Lookup helps explain why users on different networks may temporarily receive different answers.
How to interpret no CNAME result
No CNAME does not mean a hostname is broken. Many hosts publish A or AAAA records directly. Others use provider-specific flattening that returns an address rather than exposing a CNAME to recursive clients. Use DNS Lookup to inspect the wider record set when you need more context.
Related Trexmi DNS tools
Use NS Lookup to verify delegation, MX Lookup for mail routing, and TXT Record Lookup for SPF, verification, and policy text. The IANA root-zone resources provide additional authoritative DNS context.
CNAME Lookup summary
CNAME Lookup gives you a focused answer to a common DNS question: is this hostname an alias, and if so, where does it point? The visual result combines the canonical target, TTL, record status, and raw DNS data so developers, administrators, and site owners can verify an alias without reading an unformatted DNS response.