Email senders
Kit DMARC setup (ConvertKit): verified sending domain
How Kit, formerly ConvertKit, authenticates your domain with CNAME records, why DMARC needs a verified sending domain and what breaks alignment.
SPF include for Kit (ConvertKit)
Kit (ConvertKit) does not need an SPF include on your domain.
DKIM for Kit (ConvertKit)
- Selectors
- cka
- How to enable it
- Add a Verified Sending Domain under Settings > Email, then publish the CNAME records Kit generates. Kit's help shows cka._domainkey as a host. Copy every host and value from your account.
Kit (ConvertKit) signs with your domain
Envelope-from and SPF alignment
SPF counts for DMARC only when this domain matches the domain in your From address. If it is Kit (ConvertKit)’s own domain, SPF can pass without aligning, and DMARC then depends on an aligned DKIM signature.
- Envelope-from (Return-Path)
- A Kit address (kit.com) by default. After you verify the domain, Kit says your from-address goes in the return path. It does not say whether that is your exact domain or a subdomain.
Sending ranges of Kit (ConvertKit)
Use these to recognize Kit (ConvertKit) in your reports. They change over time, so do not copy them into your SPF record.
Kit (ConvertKit) does not document this.
Does your domain authorize Kit (ConvertKit)?
Enter your domain. The SPF Checker reads your record and names the senders it authorizes.
Kit (ConvertKit) documentation
- Kit Help: Verify your domain to optimize your deliverability
- checked 2026-11-09
- Kit Help: What you should know before setting up a Verified Sending Domain
- checked 2026-11-09
- Kit Help: How to add a DMARC record to your verified sending domain
- checked 2026-11-09
- Kit Help: DMARC: What is it and should you use it?
- checked 2026-11-09
- Kit Help: Inbox Placement Tests: How to Analyze the Results
- checked 2026-11-09
- Kit Help: Why are my emails going to spam?
- checked 2026-11-09
- Kit Help: Why are my confirmation emails going to spam?
- checked 2026-11-09
How it authenticates
Kit DMARC alignment depends on a Verified Sending Domain. Kit, formerly ConvertKit, keeps this setting under Settings > Email.
Without it, your From address is yours but the return path is a Kit address on kit.com. The return path is the hidden address that collects bounces, and SPF checks its domain. That domain differs from yours, so SPF cannot align.
After you verify the domain, Kit says it signs your messages with DKIM using your domain, authenticates SPF using your domain and puts your from-address in the return path. DKIM is a signature that receivers check against a key in DNS. One passing, aligned result, SPF or DKIM, is enough for DMARC to pass.
Kit generates CNAME records for you to publish, or configures them through Entri, a third-party setup tool. Its help shows ckespa and cka._domainkey as example hosts, so cka is the DKIM selector to try first. Copy every host and value from your account.
What to watch for
- DMARC before verification. Kit warns that mail from a domain with a DMARC policy will likely go to spam until you verify that domain. Kit also advises against starting at
p=reject. - Doubled host names. Some DNS providers expect the short host,
ckespainstead of the full name. Try both forms. Kit notes that Bluehost does not accept periods in its CNAME records. - Changed records. Kit says DKIM and SPF can fail if the CNAME records are changed or deleted. Confirm the key with the DKIM checker.
- Strict SPF alignment. Confirm the actual return-path domain in a DMARC report before changing the aspf tag to
aspf=s. - Free mailbox addresses. Kit says mail sent from addresses such as gmail.com will likely land in spam. Send from a domain you control.
- Open rates after the switch. Kit warns that rates can drop or rise for a while as mailbox providers reassess your reputation.