The DNS records
Copy every name and value from Advanced settings. Constant Contact's troubleshooting article gives the CNAME targets as 100._domainkey.dkim1.ccsend.com and 200._domainkey.dkim2.ccsend.com; check them against your account.
CNAME method: first record
Type: CNAME · Host: ctct1._domainkey
<Value shown in Constant Contact>
CNAME method: second record
Type: CNAME · Host: ctct2._domainkey
<Value shown in Constant Contact>
TXT method: generated key
Type: TXT · Host: 2020223150._domainkey
k=rsa; p=<public key shown after you click Generate key>
The selector is Constant Contact's example; yours is shown when you click Generate key.
DMARC policy
Type: TXT · Host: _dmarc
<DMARC value shown in Constant Contact>
If your domain already has a DMARC record, keep one record rather than adding a second.
Set it up and turn on signing
- Click your profile name in the upper right, choose Settings, then open the Advanced settings tab.
- Click Add self-authentication, select Self-authenticate using DKIM CNAME records, click Continue, choose the domain and click Continue again.
- Use the copy icons to copy each CNAME and DMARC name and value into your DNS host. Enter
ctct1._domainkeywithout your domain if the host appends it. - Wait: Constant Contact says propagation can take up to 48 hours. Then click Check status, and when the domain is ready, Activate.
DMARC alignment
Self-authentication is what lets Constant Contact sign campaigns with your domain, so DKIM can align with your From address under DMARC. Constant Contact stresses that the DKIM key works independently of DMARC: publishing the DMARC record doesn't create the key, and the key doesn't set a policy. Both have to be in place and activated.
Key length and rotation
With the CNAME method the keys sit on ccsend.com names that Constant Contact controls, so a key change needs no DNS edit from you. With the TXT method the public key lives in your zone, so a new key means a new record. Constant Contact doesn't document a key length or rotation schedule in these articles.
Common mistakes
- "Host name was not found". The record is missing or its name doesn't match. Check for a doubled domain.
- "Please enter correct value for host name". The name is right but the value differs from what Constant Contact gave you.
- Case changes in the DMARC record. Constant Contact says DMARC record information is case-sensitive.
- Activating too early. Allow 24 to 48 hours before troubleshooting errors.
Check your Constant Contact DKIM key
Enter your domain and the selector from your Constant Contact account. Free, reads public DNS only.
Frequently asked questions
What is Constant Contact self-authentication?
It is Constant Contact's name for publishing DKIM records for your own domain, plus a DMARC policy, so campaigns are signed with your domain. You set it up under Settings, Advanced settings, Add self-authentication, then activate it.
Where do Constant Contact's DKIM CNAMEs point?
To Constant Contact's DKIM hosts on ccsend.com; its troubleshooting article gives 100._domainkey.dkim1.ccsend.com and 200._domainkey.dkim2.ccsend.com. Copy the exact pairs from your account rather than from a guide.
Why does Constant Contact say my host name was not found?
The record isn't in your DNS yet, or its name doesn't match. Many DNS hosts add your domain automatically, so ctct1._domainkey.example.com becomes doubled. It can also take 24 to 48 hours before Constant Contact sees new records.
Sources
- Constant Contact Knowledge Base: Constant Contact authentication
- Constant Contact Knowledge Base: Set up the self-authentication DKIM key with your hosting provider
- Constant Contact Knowledge Base: Troubleshooting DKIM self-authentication using CNAME, TXT and DMARC
- RFC 6376: DomainKeys Identified Mail (DKIM) Signatures
- RFC 8301: Cryptographic Algorithm and Key Usage Update to DKIM
Checked against Constant Contact's documentation on October 22, 2026. Providers change their setup screens; if yours differs, follow the values your admin console shows.
DKIM records for other providers
- Microsoft 365CNAME: selector1, selector2
- Google WorkspaceTXT: google
- Zoho MailTXT: you choose (e.g. zoho)
- GoDaddyCNAME: secureserver1, secureserver2
- FastmailCNAME: fm1, fm2, fm3
- Proton MailCNAME: protonmail, protonmail2, protonmail3
- iCloud MailCNAME: sig1
- HostingerCNAME: hostingermail-a, hostingermail-b, hostingermail-c
- Private EmailTXT: privateemail, default (bought before 2 June 2026)
- IONOSCNAME: s1-ionos, s2-ionos, s42582890
- Rackspace EmailTXT: shown in the Cloud Office Control Panel
- Amazon SESCNAME or TXT: <token1>, <token2>, <token3> (Easy DKIM), your own (BYODKIM)
- SendGridCNAME or TXT: s1, s2
- MailgunTXT or CNAME: assigned by Mailgun (e.g. pic, krs, smtp), pdk1, pdk2 (Automatic Sender Security)
- PostmarkTXT: <timestamp>pm (e.g. 20131031155228pm)
- MailjetTXT: mailjet
- SMTP2GOCNAME: shown in SMTP2GO for your domain
- SparkPostTXT: scph<number> (generated, e.g. scph0316), your own (API)
- Elastic EmailTXT: api
- ResendTXT: resend
- MailerSendCNAME: ms1, ms2
- MailchimpCNAME: k2 and a second CNAME (Marketing), mte1, mte2 (Transactional)
- BrevoTXT or CNAME: mail (TXT), 2 CNAMEs from your account
- HubSpotCNAME: hs1-<number>, hs2-<number>
- KlaviyoCNAME: km1, km2 (marketing), kt1, kt2 (transactional), ks1, ks2 (service)
- ActiveCampaignCNAME: acdkim1, acdkim2
- SquarespaceCNAME: squarespace
- Dynamics 365 Customer InsightsCNAME: CNAME1 and CNAME2 from the wizard (e.g. namkey1)
- MailerLiteCNAME: litesrv
- Campaign MonitorTXT: cm, your own (existing keys)
- KitCNAME: cka
- MarketoTXT: chosen by you in Marketo
- Account Engagement (Pardot)TXT: shown in Expected DNS Entries
- Customer.ioTXT: cio
- Zoho CampaignsTXT: numbered per account (e.g. 2232)
- SalesforceCNAME: you choose two (e.g. example-sf-a, example-sf-b)
- ZendeskCNAME: zendesk1, zendesk2
- Help ScoutCNAME: strong1, strong2
- IntercomCNAME: intercom
- OdooCNAME: odoo
Compare every provider's selectors in one table · SPF record for Constant Contact
Related guides
How to find a domain's DKIM selector, and check its key
Find a DKIM selector from the s= tag in an email header, see the selectors Microsoft 365, Google Workspace and common senders use, then check the key.
8 min read SPF, DKIM & DMARCHow to rotate DKIM keys without breaking email
How often to rotate DKIM keys, which key length to use, how to name selectors, and how to rotate in Microsoft 365, Google Workspace and on your own server.
9 min read SPF, DKIM & DMARCDKIM "body hash did not verify" and other DKIM failures: causes and fixes
Fix DKIM failures: body hash did not verify, signature did not verify, no key for signature and short keys. Causes from mailing lists to broken TXT records.
9 min readLast updated