ctct1 and ctct2 are Constant Contact’s DKIM selectors when it self-authenticates your domain with CNAMEs to ccsend.com. Where several Constant Contact accounts share one domain it gives a TXT key at a numbered selector instead.
| Whose | Constant Contact — marketing email |
| Selector | ctct1, ctct2 |
| Published as | Two CNAMEs, to 100._domainkey.dkim1.ccsend.com and 200._domainkey.dkim2.ccsend.com; or a numbered TXT key |
| Key | The keys at ccsend.com are 2048-bit |
| Before you set it up | The From address is rewritten to name-domain.com@shared1.ccsend.com |
| Where to find it | Settings → Advanced settings → Add self-authentication |
| Can it go? | Remove self-authentication in Constant Contact first; with the records gone, the From goes back to the ccsend.com rewrite. |
Is Constant Contact’s key on your domain?
Enter a domain — or paste the DKIM-Signature header of a message it sent: we look for Constant Contact’s key under ctct1 and ctct2, check it, and name every other key the domain publishes.
The records
What Constant Contact asks you to publish, with its own values in place of the placeholders:
ctct1._domainkey.example.com CNAME 100._domainkey.dkim1.ccsend.com
ctct2._domainkey.example.com CNAME 200._domainkey.dkim2.ccsend.com
Common mistakes
- Entering ctct1._domainkey.example.com at a host that appends the domain.
- Putting the DKIM value inside the DMARC record.
Sources
Checked on 27 September 2026 against these official sources:
- Self-authenticate your emails using your own domain — knowledgebase.constantcontact.com
- Troubleshooting DKIM self-authentication using CNAME, TXT and DMARC — knowledgebase.constantcontact.com