CNAME Record (Canonical Name Record)

What Is a CNAME Record?

A CNAME record (Canonical Name record) is a type of DNS record that maps one domain name to another — its "canonical" name. Rather than pointing directly to an IP address like an A record does, a CNAME creates an alias. For example, mail.company.com might be a CNAME pointing to mailserver.hostingprovider.com. When a DNS resolver looks up mail.company.com, it first resolves the CNAME, then follows that to the final destination.

CNAME Records and Email Infrastructure

In email, CNAME records appear most often in DKIM (DomainKeys Identified Mail) configuration. When you use a third-party email platform (like Mailchimp, Klaviyo, or HubSpot), that platform often asks you to create CNAME records pointing to their servers. This allows the platform to manage DKIM signing keys on your behalf while keeping the authentication linked to your domain. Instead of directly publishing a long DKIM TXT record, you publish a CNAME that delegates management to the sending platform.

CNAME for Email Tracking Domains

Another common use of CNAME records in email is tracking domain configuration. ESPs use custom tracking domains for click and open tracking links. Instead of links going through a generic ESP domain (which can affect deliverability), you configure a subdomain of your own domain (e.g., click.yourcompany.com) as a CNAME pointing to the ESP's tracking server. This keeps branding consistent and improves deliverability by avoiding shared ESP tracking domains.

CNAME Limitations

CNAME records have an important limitation: you cannot use a CNAME for a root domain (also called an apex domain or naked domain). For example, you can create a CNAME for mail.company.com but not for company.com itself. This matters for email because SPF records must be at the root domain level — so you can't use a CNAME to delegate SPF. Some DNS providers offer a workaround called ALIAS or ANAME records that behave like CNAME records at the apex, but these aren't part of the official DNS standard.

How CNAME Records Relate to Email Verification

When EmailVerify.io verifies an email address, it performs DNS lookups as part of the domain validation process. A domain with properly configured DNS records — including appropriate CNAME records for DKIM and tracking — is a signal of a legitimate, actively managed domain. Malformed or missing DNS configurations, including broken CNAME chains, can cause verification failures or flag a domain as risky.

Checking and Troubleshooting CNAME Records

You can query CNAME records using the dig command: dig CNAME mail.yourdomain.com. Common issues include CNAME chains that are too deep (more than 5–10 hops), circular references, and CNAME records pointing to nonexistent hosts. EmailVerify.io's free DNS tools at emailverify.io/tools can help you inspect your domain's configuration and catch issues that could affect deliverability.