Email senders
Constant Contact DMARC setup: DKIM, SPF and alignment
How Constant Contact signs your mail, why SPF cannot align and why a missing DMARC record rewrites your From address to ccsend.com.
SPF include for Constant Contact
Constant Contact does not need an SPF include on your domain.
DKIM for Constant Contact
- Selectors
- ctct1 ctct2
- How to enable it
- Enable self-authentication in Settings > Advanced settings and copy the generated records. CNAME names include ctct1._domainkey and ctct2._domainkey. The TXT method for multiple accounts uses an account-generated numeric selector. DMARC is also required. Without self-authentication, mail uses the shared ccsend.com domain.
Constant Contact can sign with your domain once you set it up
Envelope-from and SPF alignment
SPF counts for DMARC only when this domain matches the domain in your From address. If it is Constant Contact’s own domain, SPF can pass without aligning, and DMARC then depends on an aligned DKIM signature.
- Envelope-from (Return-Path)
- in.constantcontact.com
Sending ranges of Constant Contact
Use these to recognize Constant Contact in your reports. They change over time, so do not copy them into your SPF record.
Constant Contact does not document this.
Does your domain authorize Constant Contact?
Enter your domain. The SPF Checker reads your record and names the senders it authorizes.
Constant Contact documentation
- Constant Contact Knowledge Base: Understanding email authentication
- checked 2026-11-09
- Constant Contact Knowledge Base: Self-authenticate your emails using your own domain
- checked 2026-11-09
- Constant Contact Knowledge Base: Update your DNS records through your hosting provider
- checked 2026-11-09
- Constant Contact Knowledge Base: How your From email address may be impacted
- checked 2026-11-09
How it authenticates
Constant Contact DMARC alignment uses DKIM (DomainKeys Identified Mail), a message signature. Enable self-authentication in Settings > Advanced settings to generate your DNS records.
There are two methods. The CNAME method publishes DNS aliases with names like ctct1._domainkey, and Constant Contact calls it the simplest option. The TXT method publishes a key under a numeric selector, the label that identifies a DKIM key. It suits several Constant Contact accounts on one domain.
SPF takes a different path. Bounces go to an address at in.constantcontact.com, so SPF checks that domain and cannot align with yours. You do not need to add Constant Contact to your SPF record. DMARC alignment rests on DKIM alone.
Self-authentication also needs a DMARC record at _dmarc on your domain. Constant Contact recommends p=none.
That value requests no reports. Add a rua address you monitor to the same record to receive aggregate reports:
v=DMARC1; p=none; rua=mailto:dmarc@example.com
What to watch for
- No DMARC record. If you self-authenticate without a DMARC policy, Constant Contact rewrites your From address to its shared
ccsend.comdomain. Confirm yours with the DMARC checker. - A second DMARC record. If your domain already has one, keep it. With two records at the same name, receivers discard both. Unless a parent domain publishes a valid record, DMARC is not applied to the message.
- Doubled host names. Some DNS hosts append your domain automatically, so pasting the full name publishes
ctct1._domainkey.example.com.example.com. Enter onlyctct1._domainkey, then test the result with the DKIM checker. - Several accounts on one domain. The CNAME method stops with
This domain is already authenticated in another Constant Contact account. Use the TXT method instead. - Sending too early. After you generate a TXT key, sending fails until DNS updates, which can take 48 hours. The CNAME method lets you keep sending.
- Hardening too soon. Under
p=reject, mail without a DKIM signature from your domain can bounce. Review your reports underp=nonefirst.