Customer.io signs with a key at krs._domainkey on an account subdomain — cio12345.example.com — not on your domain itself. Because it signs as that subdomain, DMARC passes only with relaxed alignment.
| Whose | Customer.io — messaging automation |
| Selector | krs on a cio subdomain |
| Published as | A TXT with the key at krs._domainkey.cio<number>.<your domain> — a subdomain, not the domain itself |
| Before you set it up | You cannot send from the domain on Customer.io’s servers until it is verified |
| Where to find it | Settings → Workspace Settings → Email → Add Sending Domain |
| Can it go? | Customer.io warns that removing records after verification leads to bounces and spam placement. |
Is Customer.io’s key on your domain?
Customer.io makes a selector for each account. Enter a domain and the selector it gave you — or paste the DKIM-Signature header of a message it sent — and we check the key, and name every other key the domain publishes.
The records
With your account number — plus the MX and SPF records it gives for the same subdomain:
krs._domainkey.cio12345.example.com TXT k=rsa; p=<public key>
How it works
The key is on the cio subdomain, so a finder looking at your domain’s own _domainkey does not see it: check krs._domainkey.cio<number>.<domain> itself.
Common mistakes
- Strict DMARC alignment (adkim=s): the signature is for the subdomain, so it fails.
- GoDaddy doubling the domain in the name.
Sources
Checked on 27 September 2026 against these official sources:
- Customer.io Docs — docs.customer.io