All platforms
CRM-matched DNS
Klaviyo · 3 CNAME + 1 TXT · DKIM · LINK · VERIFY
Klaviyo DNS Checker
Klaviyo sends from your domain using its own required records
, 3 CNAME + 1 TXT covering DKIM, LINK, VERIFY. A generic SPF test
cannot see whether they match. We check your live DNS against
Klaviyo’s spec, host by host, character by character.
Free, no account.
domain only, we strip email and protocol automatically
What Klaviyo requires
Klaviyo: 3 CNAME for authentication + 1 TXT for domain ownership. This is the exact table our verifier checks
your DNS against, not a generic template.
| Type | Host | Required value | Purpose |
|---|
| CNAME | klaviyo1._domainkey | dkim1.klaviyomail.com | DKIM |
| CNAME | klaviyo2._domainkey | dkim2.klaviyomail.com | DKIM |
| CNAME | em.YOUR_SUBDOMAIN | sendgrid.klaviyomail.com | LINK |
| TXT | YOUR_DOMAIN | klaviyo-site-verification=YOUR_PUBLIC_API_KEY | VERIFY |
How Klaviyo authenticates
Klaviyo handles DKIM by delegation: you publish 2 CNAME records (selectors klaviyo1, klaviyo2) pointing into dkim1.klaviyomail.com, and Klaviyo hosts and rotates the actual signing keys on its side. You never see the public key, which also means a checker that only looks for TXT keys at _domainkey will wrongly report DKIM as missing here.
Note what is NOT in the table: Klaviyo does not ask for an SPF include on this hostname. Its mail passes SPF on its own return-path domain, so adding one anyway does nothing for Klaviyo and spends one of your ten SPF lookups.
The non-DKIM CNAME handle tracking or bounce domains. They carry no authentication themselves, but Klaviyo's setup screen will not verify the domain until they resolve.
Mistakes we see on Klaviyo domains
Publishing the CNAME target as a TXT record. The record type matters: a TXT with the right value still is not a delegation, and the key lookup dies at your zone.
Proxying the _domainkey CNAMEs through a CDN. They must resolve as plain DNS; an orange-clouded record answers with the CDN's addresses and the key disappears.
Why a generic checker misses this
A standard DNS tool tells you your SPF parses and your DMARC exists. It has no
idea Klaviyo is in the picture. It cannot tell you a required CNAME points at
the wrong target, a selector is missing, or the include chain never reaches
Klaviyo’s servers, which are precisely the failures that put
Klaviyo mail in spam while every generic check shows green.
Common questions
What DNS records does Klaviyo require?
Klaviyo requires 4 DNS records: 3 CNAME + 1 TXT, covering DKIM, LINK, VERIFY. The exact hosts and values are in the table above, they come from the same spec table our verifier checks against.
Why does a normal SPF checker pass my domain but Klaviyo mail still fails?
A generic checker only tests whether your SPF record parses. It does not know which include Klaviyo needs, which CNAME targets its DKIM keys live behind, or which selector names it signs with. We compare your live DNS against Klaviyo’s required records character by character, so a missing include or a typo in a CNAME target is called out by name.
Will adding these records break my existing email?
The DKIM CNAMEs and the DMARC record are additive. SPF is the one to be careful with: a domain must publish exactly one SPF record, so if you already have one, merge the new include into it rather than adding a second record, two SPF records is an automatic PermError.
Keep going