All platforms
CRM-matched DNS
ConvertKit · 4 CNAME + 1 TXT · DKIM · SPF · DMARC
ConvertKit DNS Checker
ConvertKit sends from your domain using its own required records
, 4 CNAME + 1 TXT covering DKIM, SPF, DMARC. A generic SPF test
cannot see whether they match. We check your live DNS against
ConvertKit’s spec, host by host, character by character.
Free, no account.
domain only, we strip email and protocol automatically
What ConvertKit requires
Kit: 3 CNAME for DKIM rotation + 1 CNAME for return-path. Kit manages SPF on their side via envelope sender. This is the exact table our verifier checks
your DNS against, not a generic template.
| Type | Host | Required value | Purpose |
|---|
| CNAME | cka._domainkey | cka._domainkey.YOUR_ACCOUNT.convertkit-mail2.com | DKIM |
| CNAME | ckb._domainkey | ckb._domainkey.YOUR_ACCOUNT.convertkit-mail2.com | DKIM |
| CNAME | ckc._domainkey | ckc._domainkey.YOUR_ACCOUNT.convertkit-mail2.com | DKIM |
| CNAME | ckespa | spf2.convertkit-mail.com | SPF |
| TXT | _dmarc | v=DMARC1; p=none; rua=mailto:[email protected] | DMARC |
How ConvertKit authenticates
ConvertKit handles DKIM by delegation: you publish 3 CNAME records (selectors cka, ckb, ckc) pointing into cka._domainkey.YOUR_ACCOUNT.convertkit-mail2.com, and ConvertKit 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: ConvertKit 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 ConvertKit and spends one of your ten SPF lookups.
The non-DKIM CNAME handle tracking or bounce domains. They carry no authentication themselves, but ConvertKit's setup screen will not verify the domain until they resolve.
DMARC is yours, not the platform's: one record at _dmarc governs every sender on the domain. If another tool already publishes it, do not add a second; the spec row above shows the minimum this platform expects to find.
Mistakes we see on ConvertKit 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 ConvertKit 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
ConvertKit’s servers, which are precisely the failures that put
ConvertKit mail in spam while every generic check shows green.
Common questions
What DNS records does ConvertKit require?
ConvertKit requires 5 DNS records: 4 CNAME + 1 TXT, covering DKIM, SPF, DMARC. 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 ConvertKit mail still fails?
A generic checker only tests whether your SPF record parses. It does not know which include ConvertKit needs, which CNAME targets its DKIM keys live behind, or which selector names it signs with. We compare your live DNS against ConvertKit’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