DMARC, SPF and DKIM for Customer.io
Updated 2026-11-14
Customer.io is a messaging platform for marketing and transactional email. To send as your own domain, you add a sending domain in your workspace and publish the records it shows, either by hand or through automatic setup. You also need a DMARC record on your root domain. This guide follows Customer.io's own documentation. For background on each standard, see SPF explained, DKIM explained and DMARC explained.
What Customer.io sends from
The visible From address (Customer.io calls it the Display-From) is your domain, for example [email protected].
The envelope sender (Return-Path, also called MAIL FROM or Envelope-From) is a subdomain of yours. As of November 2026 Customer.io says: "your envelope's from domain will always be in the format: cio#####.mydomain.com where ##### is your account number." In this guide we use cio12345.example.com as that name, as Customer.io's own examples do.
The MX records on that subdomain "create a custom return-path using your subdomain", which Customer.io uses for "receiving bounce and spam feedback". Its Apple relay page adds that the feedback address is postmaster@cio#####.yourdomain.com.
DKIM is signed with a key published under the same subdomain. Customer.io says it "uses an account-specific subdomain of your verified domain (ex. cio#####.yourdomain.com) for signing the return-path, SPF, and DKIM headers".
Customer.io has US and EU account regions. The docs do not describe any difference in DNS records between them.
Unless you use a custom SMTP server, you must authenticate a sending domain before you can send from it. The docs say you need the records "for each domain you'll send from" and to repeat the process "for any other domains you want to send from". In our reading, a subdomain such as news.example.com gets its own set.
SPF
SPF is checked on the Return-Path domain, and for Customer.io that is the cio subdomain. Customer.io places its SPF record there on purpose, so that it "will not count towards the lookup limit of your existing SPF record". Its FAQ says the SPF record must be "placed inside of the Customer.io-specific subdomain, rather than your existing SPF record in your root domain", and that it must be a TXT record, not the old SPF record type.
The bounce subdomain also gets MX records. The docs describe "One MX record with two hostnames". Their Route 53 example shows the two values on one record, so we read the documented shape like this:
cio12345.example.com MX 10 mxa.mailgun.org.
cio12345.example.com MX 10 mxb.mailgun.org.
The docs do not print the SPF value for the subdomain. Copy the TXT record and the MX values exactly as your workspace shows them.
Your root domain does not need a Customer.io entry for normal sending. One case is different. Apple's Private Email Relay checks SPF on the From domain itself. For that case Customer.io documents this record on the From domain:
example.com TXT v=spf1 include:mailgun.org ~all
If example.com already has SPF, merge the include. Customer.io's own example for a domain that also uses Google Workspace:
example.com TXT v=spf1 include:_spf.google.com include:mailgun.org ~all
The first record uses 1 DNS lookup in the record itself and the second uses 2, because each include counts 1. Customer.io does not document how many nested lookups include:mailgun.org adds. The limit is 10 for the whole tree (RFC 7208), and the SPF lookup counter counts it. One name may only hold one SPF record (multiple SPF records).
Keep ~all. RFC 9989 warns that -all can get a message rejected in SMTP before DMARC is evaluated, even when DKIM would have aligned.
DKIM
Customer.io DKIM is one TXT record on the cio subdomain, with the selector cio. As of November 2026 the documented host name is cio._domainkey.cio#####.yourdomain.com:
cio._domainkey.cio12345.example.com TXT k=rsa; p=abcDEF123ghi456JKL
The value above is Customer.io's own placeholder. Copy the full value from your workspace.
Key length: "When you add a new domain, Customer.io generates a 2048-bit DKIM key by default." That value is longer than the 255 characters one TXT string can hold. Some DNS hosts, including Amazon Route 53, reject it unless you enter it as two or more quoted strings in one record, separated by a space and without line breaks. The docs do not say which key length older domains have, and they do not describe key rotation.
Customer.io requires both records. Its FAQ says "both SPF and DKIM are verified in order for us to send email from your domain".
DMARC alignment
DMARC passes when SPF or DKIM passes and the authenticated domain aligns with the From domain. SPF alignment compares the Return-Path domain with the From domain. DKIM alignment compares the signature's d= domain with the From domain. Relaxed alignment accepts the same organisational domain. Strict alignment (aspf=s, adkim=s) needs identical names.
With Customer.io's built-in delivery, the Return-Path is cio12345.example.com. The DKIM key sits under that name too, so the signature's d= is the cio subdomain. That last point is our reading of the records and the quote above; the docs do not print a sample DKIM-Signature header. Send a test message and check the headers yourself.
Both legs therefore align only under relaxed alignment. Customer.io says so: your DMARC policy must use "r (or relaxed) values for the aspf and adkim tags", and a strict policy "would result in your Customer.io emails failing to pass alignment". If you leave both tags out, they are relaxed by default.
One sentence in the docs swaps the terms: it calls the From address the "mail-from domain" and the return-path the "header-from subdomain". In standard terms it is the other way round. The conclusion, relaxed alignment, is the same.
Step by step to p=reject
- Add a sending domain. Go to Settings, Workspace Settings, Email, click Add sending domain, enter the domain, display name and email address, and click Add domain; the email address is optional at this stage, but Customer.io needs a From address to finish verification.
- Publish the records. Click Connect domain to let automatic setup (available since March 29, 2026) apply them through Entri, or click Set up manually and add the MX, SPF and DKIM records on
cio12345.example.comexactly as shown, then click Verify domain (verification can take up to 72 hours). - Publish DMARC with p=none and a report address. Add a TXT record at
_dmarc.example.comwithv=DMARC1; p=none; rua=mailto:[email protected], which meets Customer.io's minimum and asks receivers for aggregate reports. - Read the reports and fix other senders. Watch the reports for a few weeks, confirm that Customer.io mail passes aligned DKIM and SPF, and give every other legitimate sender aligned DKIM or SPF.
- Move to p=quarantine. Change the policy to
p=quarantineand keep reading reports, because failing mail now goes to spam and a sender you missed shows up quickly. - Move to p=reject. When the reports show only legitimate mail passing and nothing legitimate failing, change the policy to
p=reject.
The record for step 3:
_dmarc.example.com TXT v=DMARC1; p=none; rua=mailto:[email protected]
That record triggers our DMARC policy none note on purpose; it is the monitoring stage. The final record:
_dmarc.example.com TXT v=DMARC1; p=reject; rua=mailto:[email protected]
Customer.io says to publish _dmarc only on your root domain. When it verifies a domain it looks for _dmarc.<your sending domain> first and then falls back to the root record, so one root record covers your sending subdomains. As of Feb 1, 2024 it checks your DMARC policy against the Gmail and Yahoo sender requirements during verification.
Some receivers support pct (RFC 7489) or t=y (RFC 9989), but RFC 7489 says unknown tags must be ignored, so a receiver may apply p=reject; t=y as a full reject. Do not treat either tag as a safety net (partial pct).
Common mistakes
- Putting SPF on the root domain. The SPF record that verifies belongs on the
ciosubdomain. A root include alone does not verify the domain. - Strict alignment.
aspf=soradkim=smakes Customer.io mail fail DMARC, because both identifiers are a subdomain. - The domain typed twice. GoDaddy and similar hosts append your domain. Enter only
cio12345, notcio12345.example.com. - A DKIM value that is too long. Split the 2048-bit key into quoted strings within one TXT record.
- Deleting your own records. Customer.io warns that if you delete your domain's existing records while adding its records, you won't be able to receive email. It also checks records only when you click Verify domain, so if a record is removed later, mail can bounce or go to spam and Customer.io will not notice on its own.
- Counting the records. The page lists "four DNS records", calls the MX entry "One MX record with two hostnames", and a FAQ later mentions "all three required DNS authentication records". Go by what your workspace shows.
- No report address. Without
ruayou cannot see what fails (DMARC without rua).
How to check it
Run the email security check on example.com to read SPF, DKIM and DMARC together. Run the SPF lookup counter on cio12345.example.com and on your root domain to count every lookup. In the DKIM selector finder, enter the selector cio with the cio subdomain, since the key is not under your root domain. Build your policy with the DMARC record generator. Finally, send a test message and check that the Return-Path and the DKIM d= both end in example.com.
Frequently asked questions
Do I need to add Customer.io to the SPF record on my root domain?
Not for normal sending. Customer.io puts its SPF record on an account-specific subdomain such as cio12345.example.com, and says that record will not count towards the lookup limit of your existing SPF record. The exception is Apple's Private Email Relay: Apple checks SPF on the From domain, and for that case Customer.io documents v=spf1 include:mailgun.org ~all on the From domain, merged into any record you already have.
What does the Customer.io DKIM record look like?
As of November 2026 it is one TXT record at cio._domainkey.cio12345.example.com, where cio12345 stands for your account-specific subdomain. The value starts with k=rsa; p=. Customer.io generates a 2048-bit key by default for new domains, so some DNS hosts need the value split into two quoted strings.
Can I use aspf=s or adkim=s with Customer.io?
No. Customer.io says the return-path, SPF and DKIM all use the cio subdomain of your domain, so a strict policy would make your Customer.io mail fail alignment. Leave both tags out (relaxed is the default) or set them to r.
Are the records different for US and EU accounts?
Customer.io does not document any difference. Its region page says the region does not affect feature availability apart from a few listed exceptions, and 'Otherwise, the only difference between regions is where your data resides.' Copy the records your own workspace shows.
Sources
- Domain authentication, Customer.io documentation, fetched 2026-11-14.
- Domain authentication (Markdown version), Customer.io documentation, fetched 2026-11-14.
- Transitioning to Customer.io as a sender, Customer.io documentation, fetched 2026-11-14.
- Authenticating for Apple private email relay, Customer.io documentation, fetched 2026-11-14.
- Account regions (US and EU), Customer.io documentation, fetched 2026-11-14.
- Check your DMARC policy, Customer.io documentation, fetched 2026-11-14.
- Domain setup made easy, Customer.io documentation, fetched 2026-11-14.
- RFC 7208: Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1, RFC Editor, fetched 2026-11-14.
- RFC 9989: Domain-Based Message Authentication, Reporting, and Conformance (DMARC), RFC Editor, fetched 2026-11-14.
- RFC 7489: Domain-based Message Authentication, Reporting, and Conformance (DMARC), RFC Editor, fetched 2026-11-14.