Kit emails going to spam? Check your domain in 60 seconds.
Type your domain and we'll verify Kit's Verified Sending Domain records plus the foundation every sender needs — SPF, DMARC, MX and 24+ blocklists. No signup, no email required.
Free · no signup · unlimited checks · reads public DNS only
Kit (formerly ConvertKit) can only build your domain's reputation if your domain is actually vouching for it. That happens through Kit's Verified Sending Domain: two CNAME records — one at cka._domainkey (DKIM signing) and one at ckespa (envelope delegation) — that you add once in your DNS. When they're in place, every broadcast is cryptographically signed by YOUR domain. When they're not, Kit signs with its own shared domain, your emails inherit the reputation of thousands of strangers, and Gmail's 2024 bulk-sender rules start counting against you.
This checker reads your public DNS and tells you plainly whether Kit is authenticated on your domain — and whether the foundation underneath it (SPF, DMARC, MX records, blocklist status) will hold. Nothing to install, nothing to send.
How Kit setups actually fail
The Verified Sending Domain was never finished
It's optional-looking in Kit's settings, so many creators skip it. The newsletter still sends — but from Kit's shared infrastructure, which means your domain builds zero reputation and strict DMARC policies treat your own broadcasts as impostors. If our check shows cka._domainkey missing, this is you.
A DMARC policy without Kit alignment
Adding DMARC is now required by Gmail and Yahoo for bulk senders — but if you publish p=quarantine or p=reject while Kit is unverified, you've instructed every mailbox provider to junk your own newsletter. The order matters: verify the sending domain first, then tighten DMARC.
The DNS provider mangled the record name
Some DNS dashboards silently append your domain to what you paste, creating cka._domainkey.yourdomain.com.yourdomain.com. The record exists — at a name nobody asks for. Our check probes the exact name Kit's signing looks for.
No DMARC record at all
Kit sets up its records, not yours — no ESP creates DMARC for you. If we show DMARC missing, publish a TXT record at _dmarc.yourdomain.com starting with v=DMARC1; p=none and you're compliant today; tighten the policy once everything passes.
Fix anything above in your Kit dashboard following the official Kit 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 Kit's official documentation on 12 July 2026.
Questions, answered plainly
Why are my Kit emails going to spam?
The most common cause is an unfinished Verified Sending Domain: without Kit's cka._domainkey and ckespa CNAME records in your DNS, your emails are signed by Kit's shared domain instead of yours, and mailbox providers score them accordingly. Missing DMARC, a broken SPF record, or a blocklisted domain are the next suspects — this checker tests all of them in one pass.
How do I set up a Verified Sending Domain in Kit?
In Kit go to Settings → Email → Verified Sending Domains, click Set up, and copy the two CNAME records it shows you into your DNS provider exactly as given. Then click Validate. DNS can take up to a few hours to propagate; re-run this checker to confirm the records answer at the right names.
Does Kit set up DMARC for me?
No — no email tool can, because DMARC lives on your domain and covers all your senders at once. You publish it yourself: a TXT record at _dmarc.yourdomain.com, starting with v=DMARC1; p=none while you confirm everything aligns.
Do I need to add Kit to my SPF record?
No. Kit's ckespa CNAME delegates the envelope, so your root SPF record stays untouched. If a guide tells you to paste an include into SPF for Kit, it's outdated — and a malformed SPF edit can break authentication for everything else you send.
The full guide
Kit emails going to spam? The 10-minute fix (and the trap that makes it worse)
Most Kit spam problems trace back to two missing DNS records. The exact fix, in plain English, plus the DMARC mistake that quietly makes everything worse.
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.