CNAME Lookup

Try Example Domains

Note

Results are retrieved in real time through public DNS resolvers (Google and Cloudflare). Cached TTL values may vary during active DNS propagation.

Frequently asked questions about DNS CNAME records and alias lookups.

CNAME Lookup FAQ

The Canonical Name record (also called CNAME record) is the DNS record that maps the domain or sub-domain to the domain name. The difference between the CNAME record and other DNS records such as A record is that CNAME does not refer to the IP address but maps the hostname to the target host.
To validate a CNAME record, all you have to do is enter your subdomain name such as www.yourdomain.com or shop.yourdomain.com and then click on Lookup CNAME. This will instantly fetch your canonical alias, its TTL value, and the corresponding target IP address.
According to the standards in the RFC 1912, CNAME cannot be created at the zone apex (naked root domain, such as example.com). The zone apex needs SOA and NS records, and according to the DNS standard, no other record can exist together with a CNAME. There are other options available for the zone apex, such as using A records, ALIAS records, and CNAME flattening.
The A record is used to map a domain name directly to an IP address (e.g., 192.0.2.1), while a CNAME record is used to map an alias domain name to a different domain name (e.g., shops.myshopify.com), which is then mapped to the IP address by your browser.
CNAME propagation usually completes within a few minutes to a few hours. The exact speed depends on your Time to Live (TTL) setting configured in your DNS zone file. Most modern cloud DNS providers propagate updates globally within 5 to 15 minutes.
Email providers such as SendGrid, Microsoft 365, and Mailchimp make use of DKIM CNAME record to automatically rotate the cryptographic keys. Simply enter your selector host in full (example: s1._domainkey.yourdomain.com, selector1._domainkey.yourdomain.com), and run the test using the tool below.
A dangling CNAME record occurs when your subdomain points to an external cloud resource (like an AWS S3 bucket, Azure App Service, or GitHub Pages site) that you deleted or no longer control. Attackers can register that abandoned resource name and claim control over your subdomain in an attack called subdomain takeover.
No, a CNAME record must always resolve to another domain name/hostname, and not to an IP address. In case you want your hostname to resolve to an IPv4 address, then you can use an A record. For IPv6 addresses, you can use the AAAA record.
Enter dig yoursubdomain.example.com CNAME +short at the terminal on macOS and Linux. Enter nslookup -type=cname yoursubdomain.example.com at the Command Prompt on Windows. The web-based CNAME lookup tool executes these commands automatically in your browser.
The absence of any result during the query can be attributed to the fact that the DNS server has not updated the information, you have used the root apex domain name rather than the sub-domain name, or the server is using the A record itself. Ensure that your DNS service provider has posted the record.

Disclaimer

CNAME records are retrieved in real-time from public DNS resolvers (Google & Cloudflare). There may be variations as DNS propagation and caching by providers is still ongoing. The application does not log any of your domain queries.