Suped

How to set up DMARC/DKIM/SPF for Customer.io

Published 3 Jul 2026
Updated 4 Nov 2026
11 min read
Summarize with
Customer.io email authentication setup for SPF, DKIM, and DMARC.
Updated on 4 Nov 2026: We clarified Customer.io DNS setup, long DKIM keys, subdomain DMARC policies, and authentication-header checks.
For Customer.io built-in delivery, authentication needs a sending domain in Customer.io, the account-specific DNS records shown for that domain, and a DMARC record covering the visible From domain. Use the Customer.io record screen as the source of truth because the hostnames and values are generated per workspace.
Customer.io uses MX records to create a custom return-path on its generated subdomain. With the Customer.io SPF and MX records in place, SPF can pass DMARC alignment under relaxed matching. The Customer.io authentication docs confirm that Customer.io uses account-specific subdomains for its SPF-authenticated return-path and DKIM signing domain.
What must pass
  1. The sending domain must show verified in Customer.io before built-in delivery can send from it.
  2. Customer.io requires both SPF and DKIM records for its built-in delivery servers.
  3. A DMARC TXT record must cover the sending domain. Keep relaxed SPF and DKIM matching for Customer.io built-in delivery.

Choose built-in delivery or custom SMTP

Confirm the delivery method before editing DNS. Customer.io's generated authentication records apply to its built-in delivery servers. With custom SMTP, the SMTP provider controls the sending infrastructure and its authentication requirements.
Built-in delivery
  1. Add the MX, SPF, and DKIM values shown in Customer.io, plus a DMARC policy covering your From domain.
  2. Customer.io must accept the DNS records before this delivery method can send from the domain.
Custom SMTP
  1. Customer.io does not require its own domain authentication, so publish the SPF and DKIM records required by the SMTP provider.
  2. Keep the sending domain in Customer.io, then inspect a delivered message to confirm the SMTP provider passes DMARC alignment.

Add your sending domain in Customer.io

Add the domain you will use in the visible From address, then open the DNS records Customer.io generates for that domain. You need access to its authoritative DNS hosting provider to publish them. Do not guess SPF includes, DKIM selectors, MX targets, or priorities from another account.
Customer.io Sending Domains screen with an unverified domain and record actions.
Customer.io Sending Domains screen with an unverified domain and record actions.
  1. In Customer.io, go to Settings, Workspace Settings, then Email.
  2. Click Add sending domain, enter the domain, display name, and From address you plan to send from, then click Add domain.
  3. Click Show Records for the domain and keep that screen open while you edit DNS.
  4. Add Customer.io records only at the hostnames Customer.io gives you. Do not remove existing MX or TXT records that handle your normal inbox mail.

Record

Example DNS hostname

Purpose

MX (two targets)
cio12345.example.com
Receives bounce and spam feedback for the return-path
TXT
cio12345.example.com
SPF policy for the return-path domain
TXT
selector._domainkey.cio12345.example.com
DKIM public key
TXT
_dmarc.example.com
Root-domain DMARC policy, also used by covered sending subdomains
Illustrative hosts for example.com. Replace cio12345 and selector with Customer.io's generated values, and copy its MX targets and priorities exactly.
Branded link tracking has separate DNS settings in Customer.io's Link Tracking tab, including a CNAME record. Configure those separately from the SPF and DKIM TXT records used for email authentication.
Automatic setup
  1. Use it when Customer.io can connect to your DNS host and you are comfortable approving record changes.
  2. Review each applied record after setup, especially MX priority and the final DNS owner name.
Manual setup
  1. Use it when DNS changes need approval or your DNS host is not supported by automatic setup.
  2. Paste the host, type, MX priority, and value from Customer.io without converting record types.

Set up SPF

Customer.io SPF belongs on the Customer.io-specific subdomain, not in your root SPF record. This avoids adding Customer.io lookups to your root SPF record, which has a 10-lookup limit, and gives Customer.io a return-path domain that matches your From domain under relaxed DMARC alignment.
Customer.io authentication screen showing SPF and return-path records.
Customer.io authentication screen showing SPF and return-path records.
  1. Copy the SPF hostname exactly, usually a Customer.io-generated subdomain such as cio12345.example.com.
  2. Create a TXT record. Do not use the old DNS SPF record type.
  3. Do not merge the Customer.io SPF value into your root SPF record unless Customer.io explicitly shows the root hostname, which is not the normal setup.
  4. Publish each MX target at the generated return-path hostname with the priority Customer.io shows. These MX records receive bounce and spam feedback; SPF authenticates the envelope-sender domain.
  5. Check the saved fully qualified hostname so a DNS host that appends your domain has not created the domain twice.

SPF checker

Find SPF syntax issues, lookup limits, and weak records.

?/16tests passed
Common SPF mistake
A common cause of failed SPF verification is a duplicated domain suffix. If your DNS host appends the domain automatically, enter only the left side that Customer.io shows before your root domain.

Set up DKIM

DKIM signs the message itself and can satisfy DMARC when the signing domain passes relaxed alignment with the visible From domain. Publish the TXT record exactly as Customer.io shows it, including the selector, hostname, and public key.
Customer.io DKIM record row with selector, host, value, and pending status.
Customer.io DKIM record row with selector, host, value, and pending status.
  1. Create the TXT record currently documented by Customer.io. Do not convert it to CNAME.
  2. Keep the full _domainkey hostname unless your DNS host appends the root domain for you.
  3. Do not overwrite an active record at the generated selector. Stop and review the DNS owner if another record already uses it.
  4. Do not trim or edit the DKIM value. If the DNS host splits a long TXT value, confirm it still returns as one logical value.
  5. Save the DNS record, then return to Customer.io and run Verify domain after the record answers publicly.
Long DKIM values need one TXT record
Customer.io documents 2048-bit DKIM keys as the default for new domains. If your DNS editor rejects the length, split the value into quoted strings of at most 255 characters each within one TXT record. The strings must join into the unchanged public key. Do not create separate TXT records for the pieces.

Set up DMARC

Customer.io recommends publishing DMARC on the root domain to cover your sending subdomains. Keep it separate from the Customer.io-generated return-path subdomain. If your domain has no DMARC record, start with p=none and aggregate reporting. If your domain already has p=quarantine or p=reject, keep that policy and fix Customer.io until it passes.
For a From address at mail.example.com, Customer.io's authentication checks first look for _dmarc.mail.example.com, then fall back to _dmarc.example.com if no direct record exists. Review an existing sending-subdomain policy before editing. When the root policy is inherited, its sp tag controls the subdomain policy if present; otherwise p applies.
Starter DMARC recorddns
Host: _dmarc Type: TXT Value: v=DMARC1; p=none; rua=mailto:dmarc@example.com
  1. Look for an existing TXT record at _dmarc.example.com before adding a new one.
  2. Publish one DMARC policy record at each DNS owner. Under RFC 9989, receivers discard multiple DMARC policy records returned for the same owner.
  3. Leave aspf and adkim absent, or set both to r, for Customer.io built-in delivery. Relaxed matching is the default.
  4. Replace dmarc@example.com with the aggregate-report address you actually monitor. For a destination on another domain, confirm that the report destination authorizes external reporting under RFC 9990.
  5. Use the DMARC record generator if you need a clean record with reporting and policy tags.

DMARC checker

Look up a domain's DMARC record and catch policy issues.

?/7tests passed
Use relaxed SPF and DKIM matching
Customer.io uses an account-specific subdomain for its return-path and DKIM signing domain. Strict matching requires identical domains, so it prevents the affected method from satisfying DMARC when the From domain differs. DMARC still passes if the other method passes with domain alignment. Keep both matching settings relaxed for the documented built-in delivery setup.
RFC 9989 policy staging
RFC 9989 makes the pct tag historic. Stage enforcement by reviewing aggregate reports and making explicit policy changes instead of relying on percentage sampling.

Verify Customer.io DNS and test delivery

Verification has two layers. Customer.io must verify the DNS records before built-in delivery can send, and a real delivered email must show passing authentication with a domain that matches the visible From domain under DMARC. Passing authentication does not guarantee inbox placement.
Customer.io verified sending domain with green checks for authentication records.
Customer.io verified sending domain with green checks for authentication records.
  1. In Customer.io, click Verify domain after saving DNS records.
  2. If the status stays pending, check that the records answer publicly at the exact hostnames Customer.io shows, then allow DNS caches to expire and retry. Customer.io says verification can take up to 72 hours.
  3. Send a new test email through the same workspace, sending domain, From address, and delivery method used in production.
  4. In trusted receiver headers, compare Authentication-Results, the SPF mail-from domain, and the DKIM signing domain with the visible From domain.
  5. The delivered message should show SPF pass, DKIM pass, and DMARC pass. DMARC needs at least one passing method with domain alignment.
  6. Test each From domain and any materially different campaign, transactional route, or custom SMTP configuration.

Email tester

Send a real email to this address. Suped shows a results button when the test is ready.

?/43tests passed
Customer.io check
  1. Customer.io verification confirms that it can find the expected DNS records.
  2. Customer.io does not continuously check the records after you click Verify domain.
Message check
  1. A delivered-message check confirms that the email passes authentication and DMARC alignment at the receiving system.
  2. One test does not prove every production route is clean or that the message will reach the inbox.
Fast fixes
  1. Confirm that exactly one TXT value beginning v=spf1 exists at the Customer.io return-path hostname. Unrelated TXT records can coexist there.
  2. Confirm the TXT owner includes the required underscore and the returned public key matches Customer.io.
  3. Compare the SPF mail-from and DKIM signing domains with the visible From domain. Remove strict matching tags when Customer.io's generated subdomains need relaxed alignment.
  4. Escape semicolons only if your DNS host requires it. Otherwise paste values exactly.

Read Customer.io authentication headers

Open the raw headers of a delivered test message and use the Authentication-Results field added by the receiving mail system, as defined in RFC 8601. These illustrative headers show the domains to compare; your account-specific values will differ.
Illustrative Customer.io authentication resultstext
From: Example <news@example.com> Return-Path: <bounce@cio12345.example.com> Authentication-Results: mx.example.net; spf=pass smtp.mailfrom=cio12345.example.com; dkim=pass header.d=cio12345.example.com; dmarc=pass header.from=example.com
The SPF smtp.mailfrom domain and DKIM header.d domain are children of example.com, so both satisfy relaxed matching with the visible From domain. A passing SPF or DKIM result for an unrelated domain does not satisfy DMARC. RFC 9989 defines these domain-matching rules.
Forwarding can break SPF even when the original Customer.io delivery was configured correctly. If DKIM survives forwarding and its signing domain still satisfies DMARC matching, DMARC can pass through DKIM.

Monitor Customer.io authentication

Customer.io checks records when you click Verify domain, but it does not keep polling your DNS. A later DNS edit, missing DKIM value, or strict DMARC change can break authentication after the initial verification.
Suped is our DMARC reporting and email authentication platform. For this workflow, DMARC monitoring turns aggregate reports into Customer.io source status, alerts, and fix steps without requiring you to read raw XML.
  1. Suped alerts your team to DMARC failures seen in aggregate reports for Customer.io traffic.
  2. Suped groups failures by source and shows whether SPF or DKIM lost alignment.
  3. Suped keeps the evidence needed to compare authentication before and after DNS changes.
  4. Suped's MSP and multi-tenancy dashboard helps teams manage Customer.io authentication across customer or brand domains.
Monitoring rule
Use Customer.io verification as the setup gate and Suped monitoring as the ongoing control. Recheck delivered headers after a routing change, then use DMARC reports to watch the production traffic that follows.

Secure your domain with p=reject

Move to p=reject only after Customer.io and every other legitimate sender passes DMARC in real traffic. For a domain without DMARC, p=none with reporting is the safe start. For a domain already at quarantine or reject, keep enforcement and fix any Customer.io failure before sending volume.
  1. Collect reports long enough to cover normal Customer.io transactional messages, journeys, broadcasts, and low-frequency sends. Keep existing enforcement while validating a new Customer.io route.
  2. Confirm which report rows belong to Customer.io using the return-path and DKIM signing domains as well as sending IPs. A shared sending IP alone does not reliably identify Customer.io traffic.
  3. Resolve Customer.io SPF, DKIM, and DMARC failures before raising policy.
  4. Move through quarantine first if you need a controlled rollout, then move to reject once legitimate traffic is clean. Do not rely on the historic pct tag for sampling.
  5. After reject, review reports after DNS and routing changes, and keep authentication alerts active.
DMARC rollout gates
Use policy changes as readiness gates, not calendar dates.
Monitor
p=none
All legitimate sources found and Customer.io visible in reports.
Contain
p=quarantine
Customer.io passes and unknown traffic is understood.
Block
p=reject
Legitimate traffic stays clean under enforcement.
Mature DMARC recorddns
Host: _dmarc Type: TXT Value: v=DMARC1; p=reject; rua=mailto:dmarc@example.com
Suped's Hosted DMARC can manage policy changes without repeated DNS edits after the initial setup. Suped also keeps Customer.io traffic visible while you move toward reject.
Best practical target
Keep the Customer.io domain verified with SPF and DKIM passing on real mail. After reaching p=reject, use aggregate reports to investigate production failures; these reports arrive after receiving systems evaluate messages and cannot prevent an initial rejection.

FAQ

Yes. For Customer.io built-in delivery, Customer.io requires both SPF and DKIM to verify the sending domain. If you use custom SMTP, authenticate with the SMTP provider instead and validate the delivered message from that route.

No, not in the normal Customer.io built-in delivery setup. Customer.io places SPF on its generated return-path subdomain, such as cio12345.example.com, so it does not add lookups to your root SPF record. Keep the SPF policy at the hostname shown for your workspace.

A verified status proves that Customer.io accepted the expected public DNS records for that sending domain. It does not prove that every production route passes DMARC, that the records will stay unchanged, or that a message will reach the inbox.

Customer.io uses an account-specific subdomain for its return-path and DKIM signing domain. Strict matching requires those domains to be identical to the visible From domain. If both methods use strict matching and the domains differ, neither can satisfy DMARC. One passing method with domain alignment is enough for DMARC, but Customer.io documents relaxed settings for both methods.

Yes. Customer.io can work with p=reject after SPF, DKIM, and DMARC pass on real Customer.io mail. Move there only after aggregate reports show Customer.io and your other legitimate senders are clean, then keep monitoring for DNS or routing changes.
DMARC monitoring

Start monitoring your DMARC reports today

Suped DMARC platform dashboard
What you'll get with Suped
Real-time DMARC report monitoring and analysis
Automated alerts for authentication failures
Clear recommendations to improve email deliverability
Protection against phishing and domain spoofing