Suped

How to set up DMARC/DKIM/SPF for Epsilon

Published 9 Jul 2026
Updated 10 Nov 2026
13 min read
Summarize with
Epsilon SPF, DKIM, and DMARC setup with DNS records and email authentication.
Updated on 10 Nov 2026: We clarified Epsilon's account-specific setup, added DNS publishing checks, and tightened DMARC rollout guidance.
Set up Epsilon by adding your sending domain in Epsilon, publishing the account-specific Return-Path and DKIM DNS records Epsilon gives you, then publishing DMARC on the visible From domain. Start with p=none only when the domain is not already protected. Verify aligned SPF and DKIM in direct Epsilon messages, then move to enforcement after Epsilon and every other approved sender passes DMARC consistently. DMARC requires at least one passing method with domain alignment.
Epsilon DNS values are account-specific. Do not guess an SPF include, DKIM selector, or CNAME target from another domain. Copy the records shown in your Epsilon account or provided by your Epsilon implementation team.

Add your Epsilon sending domain

Add the domain Epsilon will use in the visible From address, then ask your implementation team about a branded Return-Path under the same organizational domain. This setup gives Epsilon an SPF identity that can match the From domain under relaxed alignment and avoids reliance on an Epsilon-owned bounce domain.
  1. Use a dedicated marketing subdomain such as email.example.com when your main domain already has several senders.
  2. Ask your Epsilon implementation team which domain authentication controls apply to your product and account; menu names and self-service options vary.
  3. Provide the From domain and default From address, and confirm which business unit or sender profile will use them.
  4. If your Epsilon setup supports a custom Return-Path, request a bounce host such as bounces.email.example.com.
  5. Obtain the account-specific DNS checklist for authentication and bounce handling, plus any separate tracking-link records, before editing DNS.
  6. After DNS publishes, run the verification available for your account or ask your Epsilon implementation team to confirm activation.
Illustrative Epsilon sending-domain setup with a custom Return-Path and DNS verification status.
Illustrative Epsilon sending-domain setup with a custom Return-Path and DNS verification status.
A dedicated marketing subdomain makes Epsilon DNS ownership and DMARC investigation easier to manage. It does not guarantee separate reputation or prevent the parent domain's DMARC policy from applying.
  1. Use only when marketing and corporate mail are already governed together.
  2. Use when Epsilon has separate teams, templates, reply handling, or sender reputation needs.

Set up SPF

SPF (Sender Policy Framework) checks the envelope sender, also called the MAIL FROM or Return-Path domain. Publish the SPF or CNAME record Epsilon supplies for that bounce host, then confirm SPF passes with DMARC alignment to the visible From domain. If Epsilon uses its own bounce domain, adding Epsilon to your root SPF record will not create SPF alignment; configure custom DKIM for the DMARC pass path.
  1. Use the exact bounce host supplied by Epsilon, such as bounces.email.example.com, including any MX records required for bounce handling.
  2. If Epsilon gives you a CNAME for the bounce host, publish that CNAME and do not add a TXT SPF record on the same host.
  3. A hostname can have only one TXT record beginning v=spf1. If that host already has SPF, confirm the combined authorization with its DNS owner before replacing it.
  4. Keep each SPF evaluation within 10 DNS-querying terms, including nested include and redirect processing. Exceeding this limit returns permerror, not an SPF pass.
  5. Send one Epsilon test message and confirm SPF passes against the Return-Path domain.
SPF pattern for an Epsilon bounce hostdns
bounces.email.example.com. TXT "v=spf1 include:spf.epsilon.example -all"
The .example include host is a nonworking placeholder. Copy the full value and final all mechanism supplied by Epsilon, or publish the assigned CNAME instead. Do not copy illustrative DNS values into production.
Illustrative Epsilon SPF setup for a branded Return-Path; DNS values are placeholders.
Illustrative Epsilon SPF setup for a branded Return-Path; DNS values are placeholders.

SPF checker

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

?/16tests passed
After publishing the record, check the exact bounce host, not only the root domain. If your Epsilon Return-Path is bounces.email.example.com, that is the host that needs the SPF check.
Good SPF setup
  1. The Return-Path shares the From domain's organizational domain for relaxed SPF alignment.
  2. The bounce host resolves to the SPF authorization Epsilon requires, directly or through its assigned CNAME.
  3. The full SPF chain stays within the lookup limit.
Risky SPF setup
  1. SPF was added to the root, but Epsilon sends with a bounce subdomain.
  2. Two SPF TXT records exist on the same hostname.
  3. The record ends in +all or uses a broad IP range.

Set up DKIM

DKIM (DomainKeys Identified Mail) is a durable DMARC pass path because a valid signature often survives forwarding when the signed content stays intact. Require Epsilon to sign with a domain that meets your DMARC alignment settings, then confirm DKIM authentication and domain alignment before tightening policy.
  1. Request DKIM for the sending domain and ask Epsilon for 2048-bit RSA keys when supported. Epsilon manages the signing private key; publish only its supplied public-key TXT record or CNAME.
  2. Add the exact CNAME or TXT selector records Epsilon provides under _domainkey. Publishing DNS alone does not activate signing; confirm activation for the sender profile used by your campaign.
  3. Publish both active and standby selectors when Epsilon provides two records for rotation.
  4. Send a test message and inspect d= and s= in DKIM-Signature. The public key must resolve at s._domainkey.d, and the passing d= domain must meet the From domain's DMARC alignment settings.
  5. Delete retired Epsilon DKIM selectors only after Epsilon confirms signing has stopped and queued messages signed with the old key have cleared.
DKIM CNAME patterndns
eps1._domainkey.email.example.com. CNAME eps1.epsilon.example. eps2._domainkey.email.example.com. CNAME eps2.epsilon.example.
The selector names and reserved .example targets are nonworking placeholders. Epsilon must supply the live selector names and target hosts for your account.
Illustrative Epsilon DKIM selector CNAME records pending DNS verification.
Illustrative Epsilon DKIM selector CNAME records pending DNS verification.
Track every Epsilon selector through rotation. Keep the old public key available for messages still in transit, then remove the retired record after the sending team confirms it is safe to do so.

Set up DMARC

DMARC is published in DNS for the visible From domain, not inside Epsilon. If the domain has no DMARC policy, start with this monitoring record and replace the reporting address with a mailbox or reporting destination that can process aggregate XML reports.
Starter DMARC recorddns
_dmarc.email.example.com. TXT "v=DMARC1; p=none; rua=mailto:dmarc@example.com"
If your domain already uses p=quarantine or p=reject, keep that policy. Authenticate Epsilon before sending, then watch aggregate reports for unexpected failures.
  1. Publish DMARC at _dmarc on the exact From domain, such as _dmarc.email.example.com.
  2. When the From domain differs from the organizational domain, publish an explicit DMARC record at both, such as _dmarc.email.example.com and _dmarc.example.com. Preserve any existing enforcement policy.
  3. Use a monitored aggregate report destination. If the rua address uses another organizational domain, confirm that destination authorizes reports in DNS.
  4. Relaxed alignment is the default: authenticated domains share an organizational domain with From. With aspf=s or adkim=s, the corresponding domain must match From exactly; bounces.email.example.com does not meet strict SPF alignment for email.example.com.
  5. For SPF alignment, compare the Return-Path domain with the From domain. For DKIM alignment, compare the d= domain with the From domain.
Use the DMARC record generator when you need a record with reporting, subdomain policy, or test-mode fields.
Illustrative Epsilon domain verification results for SPF, DKIM, and DMARC.
Illustrative Epsilon domain verification results for SPF, DKIM, and DMARC.

DMARC checker

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

?/7tests passed
Check the domain to the right of @ in the From address that subscribers see, not the bounce domain. If Epsilon sends from news@email.example.com, its explicit DMARC record belongs at _dmarc.email.example.com. Without an explicit subdomain record, an applicable parent policy still provides coverage; sp governs existing subdomains, falling back to p when absent.

Apply the current DMARC standard

RFC 9989 defines the core DMARC protocol, while RFC 9990 and RFC 9991 define aggregate and failure reporting. Keep v=DMARC1; review obsolete rollout tags rather than changing the version string.
  1. The pct tag is historic, so do not use pct=25 or similar values to stage Epsilon enforcement.
  2. The t=y tag requests one policy level lower for failing mail: quarantine becomes none, and reject becomes quarantine. Reporting continues; t=y has no effect on p=none.
  3. A receiver that does not recognize t=y ignores it and can apply the published p=quarantine or p=reject policy in full. Publish a test-mode record only when the domain is ready for that enforcement level.
  4. Forwarding often breaks SPF, while mailing lists can also alter content and break DKIM. Confirm these paths before considering reject.
A dedicated Epsilon marketing subdomain has a clearer path to p=reject than a domain used by people who post to mailing lists. RFC 9989 advises against p=reject for general-purpose user domains unless indirect-mail effects have been reviewed and accepted.

Publish and verify the DNS records

Make changes at the authoritative DNS provider for your domain. Match each record's name and type to Epsilon's checklist. If the editor automatically appends example.com, enter _dmarc.email rather than _dmarc.email.example.com to avoid a duplicated domain suffix.
  1. Publish CNAMEs as DNS-only records when your DNS provider offers web proxying. Keep other records off the same CNAME name.
  2. If Epsilon requires NS delegation, delegate only the agreed subdomain and confirm who manages its authentication records. Keep corporate mail routing intact.
  3. For a DKIM TXT key, preserve the full public key. Multiple quoted character strings within one TXT record are valid; separate TXT records are not a way to split one key.
  4. Compare authoritative answers with resolver results after a change. Cached old answers and cached missing records can delay verification; check TTLs before repeatedly changing correct records.
Example DNS verification commandsbash
dig +short NS example.com dig +short TXT bounces.email.example.com dig +short CNAME eps1._domainkey.email.example.com dig +short TXT eps1._domainkey.email.example.com dig +short TXT _dmarc.email.example.com dig +short TXT _dmarc.example.com
Replace the domain and selector with your actual values. Query each authoritative nameserver with dig @NAMESERVER NAME TYPE when results disagree. CNAMEs point to another name, and DNS caches retain answers for their TTL, as described in RFC 1034.

Verify and troubleshoot

Verification is not complete when DNS says the records exist. Send a real Epsilon test campaign, inspect the received headers, and compare those results with DMARC aggregate reports after live traffic starts.
  1. Create a low-risk Epsilon test campaign with the final From domain, final template, and final sender profile.
  2. Use the Authentication-Results header added by the receiving mailbox provider. Confirm spf=pass for smtp.mailfrom and check that domain against the visible From domain's SPF alignment setting.
  3. Confirm dkim=pass for the signing domain shown in header.d and check its DMARC alignment with From. Match the signature's s= selector to the published DNS record.
  4. Confirm dmarc=pass appears for the visible From domain.
  5. After the first live send, confirm Epsilon appears as an approved source and both authentication paths remain healthy.

Symptom

Likely cause

Fix

SPF fail or permerror
Unauthorized sending IP, duplicate SPF, or excess DNS lookups
Check the actual MAIL FROM host and its full SPF evaluation
DKIM fail or missing signature
Wrong selector, incomplete public key, or signing not activated
Check d= and s=, DNS key content, and the active sender profile
DMARC fail
Authentication passes without alignment
Correct the Return-Path or DKIM d= domain
No aggregate reports
No reported traffic yet, invalid rua, or missing external authorization
Allow for the receiver's reporting cycle, then verify report delivery and authorization DNS
Policy block
Unapproved source or failed alignment
Pause the rollout and remediate the source
Common Epsilon authentication fixes
Send a real Epsilon email to the diagnostic address in Suped's email tester to check DNS-derived results and message headers together.

Email tester

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

?/43tests passed
A message can pass DMARC through aligned DKIM when SPF fails, which often happens after forwarding. A direct Epsilon test should still pass SPF and DKIM, so investigate a direct SPF failure before launch. Before p=reject, ensure aligned DKIM signing is active rather than relying only on SPF.
Illustrative Epsilon campaign test with sender-domain authentication checks.
Illustrative Epsilon campaign test with sender-domain authentication checks.

Monitor Epsilon authentication changes

Epsilon DNS can break after a key rotation, Return-Path change, new business unit, DNS migration, or campaign team change. Suped's DMARC monitoring helps your team review source data and SPF/DKIM results and route authentication issues to the responsible owner.
  1. Alert when a new Epsilon IP range or host starts sending for your domain.
  2. Alert when Epsilon DKIM pass rate falls after a selector or DNS change.
  3. Alert when the branded Return-Path stops passing SPF.
  4. Review DMARC failures before tightening policy; aggregate-report alerts cannot prevent the first affected campaign.
  5. Monitor Epsilon sending IPs for blocklist (blacklist) listings during high-volume sends.
Notification settings page with DMARC alerts, weekly summary, toggles, and preview buttons
Notification settings page with DMARC alerts, weekly summary, toggles, and preview buttons
In Suped's product, set alert thresholds for authentication drops and review new sources. Aggregate reports arrive on receiver reporting cycles, often daily, as described in RFC 9990. Use direct test messages before each important Epsilon campaign; report-based alerts are not a live pre-send check.
Use Suped's issue detection to review affected sources and authentication failures, then inspect the relevant DNS record and verify a fresh Epsilon test message after the fix.
  1. Route Epsilon alerts to marketing operations and DNS owners.
  2. Raise severity when failures affect a domain already on enforcement.
  3. Use source, IP, selector, and policy data before changing DNS.

Move to DMARC enforcement safely

Move a dedicated Epsilon marketing domain toward enforcement only after direct Epsilon tests pass SPF and DKIM and every approved sender passes DMARC. DMARC requires one passing method with alignment; configuring both for Epsilon provides a second pass path. Review forwarding and mailing-list effects before reject, and keep a rollback record ready for the DNS owner.
Policy readiness checks
Use evidence from representative Epsilon traffic before tightening policy.
Ready
Proceed
Epsilon passes SPF and DKIM in direct tests, every approved source passes DMARC, and reports cover representative traffic.
Investigate
Hold
An approved source fails one authentication path or the reporting period has gaps.
Stop
Do not tighten
A critical source fails DMARC or indirect-mail effects have not been assessed.
Suped's Hosted DMARC lets your team manage policy in Suped's product after the DNS owner publishes the assigned CNAME. Use either that delegation or a direct TXT record at the DMARC host, not both.
  1. Observe enough traffic to include normal Epsilon campaigns and triggered sends. For a general-purpose user domain, keep p=none for at least a month before enforcement.
  2. Approve Epsilon only after direct messages pass aligned SPF and DKIM.
  3. When ready for full quarantine at receivers that ignore test mode, publish p=quarantine with t=y and continue monitoring. Otherwise, retain p=none while fixing approved sources.
  4. Remove t=y after approved traffic stays clean through representative sends. For a general-purpose user domain being considered for reject, observe enforced quarantine for at least a month, matching the preceding monitoring period, and compare dispositions.
  5. Assess p=reject only after legitimate failures are resolved and indirect-mail effects are understood. A reject test with t=y still requests quarantine, and receivers ignoring t=y can reject failing mail.
Alternative DMARC rollout values; publish one recorddns
Host: _dmarc.email.example.com Monitoring: "v=DMARC1; p=none; rua=mailto:dmarc@example.com" Quarantine test: "v=DMARC1; p=quarantine; t=y; rua=mailto:dmarc@example.com" Quarantine enforced: "v=DMARC1; p=quarantine; rua=mailto:dmarc@example.com" Reject test: "v=DMARC1; p=reject; t=y; rua=mailto:dmarc@example.com" Reject enforced: "v=DMARC1; p=reject; rua=mailto:dmarc@example.com"
Hosted DMARC configuration dialog showing policy controls, CNAME setup, and expanded advanced options

FAQ

Yes. Direct Epsilon messages should pass DKIM with an aligned signing domain and SPF with an aligned branded Return-Path. DMARC needs one aligned method to pass, but both methods should be healthy.

Use v=DMARC1; p=none; rua=mailto:dmarc@example.com if the domain has no policy. If it already uses quarantine or reject, keep that policy and fix Epsilon authentication before sending.

Yes. DMARC passes when either SPF or DKIM passes with domain alignment to From. Configure branded Return-Path SPF when your Epsilon setup supports it so direct traffic has both authentication paths.

Reverse DNS suffixes are clues to sending infrastructure, but they do not prove a campaign is authorized. Confirm the source IPs and authentication domains against your Epsilon account details and the campaign owner before approving the source.

DNS verification does not prove that the active sender profile signs with your domain. Check for a passing DKIM signature with DMARC alignment or a passing SPF identity with alignment. Also check strict aspf/adkim settings and the policy discovered for the actual From domain.

Consider reject after direct Epsilon messages pass SPF and DKIM, every approved sender passes DMARC, and forwarding and mailing-list effects have been reviewed. RFC 9989 advises against reject for general-purpose user domains; domains still considering it should compare at least a month of monitoring with an equally long quarantine period.
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