Klaviyo emails going to spam? Check your sending domain in 60 seconds.
We verify Klaviyo's DKIM records (km1/km2._domainkey → klaviyodns.com), DMARC and your domain foundation. Tip: if you set Klaviyo up on send.yourstore.com, check that exact subdomain.
Free · no signup · unlimited checks · reads public DNS only
A Klaviyo branded sending domain usually lives on a subdomain — send.yourstore.com or similar — and that detail decides whether any check tells you the truth: the records exist on the subdomain you configured, not on your apex domain. With static routing, Klaviyo issues CNAME records at km1._domainkey and km2._domainkey pointing into klaviyodns.com, and provisions SPF through the same records — you never paste a Klaviyo include into your root SPF record.
Enter the exact domain you configured in Klaviyo (subdomain and all) and we'll verify the DKIM records answer with klaviyodns.com targets, DMARC covers what you send, and the domain is clean on 24+ blocklists.
How Klaviyo setups actually fail
Checking the apex when the setup lives on a subdomain
The classic Klaviyo confusion: records were added to send.yourstore.com, but every check — and sometimes the DMARC policy — gets pointed at yourstore.com. They're separate zones. Check the exact name from your Klaviyo settings; if we find nothing on your apex, try the subdomain before concluding anything is broken.
The auto-appended CNAME value
Klaviyo's own troubleshooting calls this out: some DNS providers append your domain to the CNAME target, producing something.klaviyodns.com.yourstore.com. Our check shows you the observed target, so this mismatch is visible instantly. The fix is a trailing period on the value or your provider's fully-qualified-name syntax.
A pasted SPF include that shouldn't be there
Klaviyo provisions SPF through the CNAMEs on a branded sending domain — hand-adding a Klaviyo include to your root SPF does nothing for alignment and pushes you toward SPF's 10-DNS-lookup limit, which can break SPF for every sender on your domain.
Fix anything above in your Klaviyo dashboard following the official Klaviyo setup guide, then re-run the check — DNS changes usually show within minutes.
Record names and provider behavior on this page were last verified against Klaviyo's official documentation on 12 July 2026.
Questions, answered plainly
Why are my Klaviyo emails going to spam?
First confirm your branded sending domain is fully verified: the km1._domainkey and km2._domainkey records must answer on the exact (sub)domain you configured, with klaviyodns.com targets. Then DMARC — required for bulk senders — then the foundation: SPF validity, MX, blocklist status. An e-commerce domain on a blocklist is more common than most store owners expect.
What DNS records does Klaviyo need?
For a branded sending domain with static routing: up to three CNAMEs (km1._domainkey, km2._domainkey and a return-path record) plus a TXT for ownership verification — all shown in Klaviyo's setup wizard with your account's exact values. Dynamic routing uses NS records on the subdomain instead.
Should I check my main domain or my sending subdomain?
The one you configured in Klaviyo — usually a subdomain like send.yourstore.com. Records live where they were added; checking the apex for a subdomain setup reports 'missing' for records that are actually fine.
Do I add Klaviyo to my SPF record?
No — with a branded sending domain the necessary SPF is provisioned through the records Klaviyo gives you. Adding an include manually is at best redundant and at worst pushes your SPF record over the 10-lookup limit.
The full guide
Klaviyo emails going to spam? You're probably checking the wrong domain
Klaviyo setups live on a subdomain like send.yourstore.com, and that detail breaks more diagnoses than any missing record. Where to actually look, and what to fix.
Read the guide →More free checkers
A passing check is a snapshot: records that are right today drift, expire and get overwritten, and nobody gets notified. That slow rot is what we call deliverability decay, and it has its own curriculum in Decay University.