All platforms
CRM-matched DNS
Constant Contact · 2 CNAME + 1 TXT · DKIM · DMARC
Constant Contact DNS Checker
Constant Contact sends from your domain using its own required records
, 2 CNAME + 1 TXT covering DKIM, DMARC. A generic SPF test
cannot see whether they match. We check your live DNS against
Constant Contact’s spec, host by host, character by character.
Free, no account.
domain only, we strip email and protocol automatically
What Constant Contact requires
Constant Contact: 2 CNAME for DKIM. Constant Contact selectors are random numbers per-customer, so we detect them by the CNAME target containing ccsend.com. This is the exact table our verifier checks
your DNS against, not a generic template.
| Type | Host | Required value | Purpose |
|---|
| CNAME | NNNNNNNN._domainkey | NNNNNNNN.dkim.ccsend.com | DKIM |
| CNAME | NNNNNNNN._domainkey | NNNNNNNN.dkim.ccsend.com | DKIM |
| TXT | _dmarc | v=DMARC1; p=none; rua=mailto:[email protected] | DMARC |
How Constant Contact authenticates
Constant Contact handles DKIM by delegation: you publish 2 CNAME records (selectors NNNNNNNN) pointing into NNNNNNNN.dkim.ccsend.com, and Constant Contact hosts and rotates the actual signing keys on its side. You never see the public key, which also means a checker that only looks for TXT keys at _domainkey will wrongly report DKIM as missing here.
Note what is NOT in the table: Constant Contact does not ask for an SPF include on this hostname. Its mail passes SPF on its own return-path domain, so adding one anyway does nothing for Constant Contact and spends one of your ten SPF lookups.
DMARC is yours, not the platform's: one record at _dmarc governs every sender on the domain. If another tool already publishes it, do not add a second; the spec row above shows the minimum this platform expects to find.
Mistakes we see on Constant Contact domains
Publishing the CNAME target as a TXT record. The record type matters: a TXT with the right value still is not a delegation, and the key lookup dies at your zone.
Proxying the _domainkey CNAMEs through a CDN. They must resolve as plain DNS; an orange-clouded record answers with the CDN's addresses and the key disappears.
Why a generic checker misses this
A standard DNS tool tells you your SPF parses and your DMARC exists. It has no
idea Constant Contact is in the picture. It cannot tell you a required CNAME points at
the wrong target, a selector is missing, or the include chain never reaches
Constant Contact’s servers, which are precisely the failures that put
Constant Contact mail in spam while every generic check shows green.
Common questions
What DNS records does Constant Contact require?
Constant Contact requires 3 DNS records: 2 CNAME + 1 TXT, covering DKIM, DMARC. The exact hosts and values are in the table above, they come from the same spec table our verifier checks against.
Why does a normal SPF checker pass my domain but Constant Contact mail still fails?
A generic checker only tests whether your SPF record parses. It does not know which include Constant Contact needs, which CNAME targets its DKIM keys live behind, or which selector names it signs with. We compare your live DNS against Constant Contact’s required records character by character, so a missing include or a typo in a CNAME target is called out by name.
Will adding these records break my existing email?
The DKIM CNAMEs and the DMARC record are additive. SPF is the one to be careful with: a domain must publish exactly one SPF record, so if you already have one, merge the new include into it rather than adding a second record, two SPF records is an automatic PermError.
Keep going