You will learn
Learn how to diagnose verification issues when setting up your dedicated sending domain in Klaviyo.
A dedicated sending domain enables you to send emails that appear from your brand, rather than from Klaviyo’s shared domain. For setup instructions, visit our guide on how to set up a dedicated sending domain.
Before you begin
Before starting the troubleshooting steps below, confirm that you have attempted to verify your sending domain in Klaviyo and are seeing the following error:
Note that Klaviyo will not automatically apply your domain after verification, as we want to ensure that you are ready to warm your sending infrastructure first if applicable. Once verified, you will need to click Apply domain. We also recommend giving time for the DNS to propagate and for the cache to clear. Depending on your DNS provider, this process could take up to 48 hours.
Troubleshooting using 3rd party tools
Klaviyo requires 3 CNAME records for email authentication, and one TXT record for domain ownership verification. When setting up a dedicated domain in Klaviyo, you’ll see similar records presented based on your subdomain choice:
In an example where the intended sending domain is send.klaviyo.com, with “send” as the subdomain and “klaviyo.com” as the root domain, the expected DNS records would be the following:
| Host | Value | Record Type |
| send.klaviyo.com | u161779.wl030.sendgrid.net | CNAME |
| kl._domainkey.klaviyo.com | kl.domainkey.u161779.wl030.sendgrid.net | CNAME |
| kl2._domainkey.klaviyo.com | kl2.domainkey.u161779.wl030.sendgrid.net | CNAME |
| klaviyo.com | klaviyo-site-verification=public_API_key | TXT |
A helpful set of tools to check if your records are propagating correctly are MxToolbox's DNS lookups:
You can use the CNAME tool to lookup the host for each of the CNAME records, and the TXT lookup tool for the TXT record.
CNAME lookup examples
send.klaviyo.com:
kl._domainkey.klaviyo.com:
kl2._domainkey.klaviyo.com:
TXT lookup example
klaviyo.com:
Based on whether you are seeing values returned by the queries, there are some common errors that may be the source of the issue.
If queries are returning values
In order for your sending domain to be successfully verified in Klaviyo, the values returned by your queries must match those presented in Klaviyo exactly. Ensure that there are not any discrepancies between the values you are seeing returned, and those in Klaviyo.
Root domain being appended to values automatically
Some DNS providers expect a period (.) at the end of the added value. Without this period, the DNS provider assumes that the entire value field is a subdomain of the domain being configured, and will automatically add the root domain. For example, if you entered u161779.wl030.sendgrid (with no period at the end), this would make the value u161779.wl030.sendgrid.net.rootdomain.com instead of just u161779.wl030.sendgrid.net.
If queries are not returning values
Root domain duplicated in the hostname
We also recommend checking if your DNS provider expects only the subdomains in the host name fields, and automatically appends the root domain. For example, if you add the CNAME record send.domain.com it would automatically become send.domain.com.domain.com.
Instead, you might need to only add the “send” subdomain in this instance for the record’s host name to be send.domain.com. Compare your other DNS records to see if you need to append it or if your provider automatically does this.
Records being proxied
If your DNS provider allows you to proxy records, you will see issues with the setup of the dedicated domain in Klaviyo if this feature is enabled. This commonly happens with Cloudflare but is possible with other DNS providers too. You’ll need to disable the proxying of your records for them to resolve over the internet, and so their presence can be verified by the sending domain set up tool in Klaviyo. Record proxying will need to stay disabled after the set up process as well for emails to authenticate as expected.
Other DNS provider issues
DNS provider does not support @ symbol
In cases where a DNS provider does not support the symbol “@”, the root domain would need to be set as the hostname for the site verification record. The “@” symbol is the shorthand for the root domain (business.com), so you can use either option depending on what your DNS provider supports.
DNS provider does not support underscores
Some DNS providers do not support underscores for CNAME records. However, in order for your sending domain to be functional within Klaviyo, these underscores are necessary.
If your DNS provider does not support underscores in your CNAME, we suggest first reaching out to your DNS provider’s support team and seeing if they can create the record for you. Often DNS providers will be able to manually adjust your CNAME to include the underscore if you reach out to them.
If your DNS provider ultimately cannot support underscores, consider using another provider as these will be necessary to your domain setup in Klaviyo.
A TXT value already exists on the root domain
If there is an existing TXT record on your root domain, you can append the Klaviyo value to your existing field. As long as the Klaviyo requested value is present, the record will be successfully validated when setting up your dedicated domain in Klaviyo.
DMARC
For emails to be DMARC compliant, the root domain on your account needs to align with the from-address domain of your emails.
For example, if you send an email using sales@example.com as the from-address, where example.com is protected by DMARC, your account will need to use a dedicated sending domain like send.example.com for all emails sent from Klaviyo to meet DMARC authentication requirements.
Additional resources
- How to set up a dedicated sending domain
- Understanding what a dedicated sending subdomain is
- Understanding dedicated vs. shared sending domains