Do I need to add Constant Contact to my SPF or DMARC record?

Which address does Constant Contact send from?

Constant Contact will rewrite your 'From' address to our own domain ( @shared1.ccsend.com for paid accounts, @shared2.ccsend.com for trial accounts), which includes a DMARC record to meet authentication requirements.

Constant Contact says in its own documentation that this email comes from @shared1.ccsend.com for paid accounts, @shared2.ccsend.com for trial accounts. That is Constant Contact's own domain, so the email is checked against Constant Contact's records, not yours.

Why does my DMARC record not cover these emails?

Author Domain: The domain name of the apparent author, as extracted from the RFC5322.From field.

DMARC is read for the domain in the From address a reader sees. When that domain is Constant Contact's, the check uses Constant Contact's records.

So your policy, from p=none to p=reject, has no effect on these emails. There is nothing to add to your SPF record for them.

Can Constant Contact send from my own domain instead?

if you have your own domain, self-authentication is the best practice to improve your delivery reputation.

You can self-authenticate your own domain, which sets up DKIM with CNAME records in your account.

If you turn that on, the email is sent as your domain, and your SPF, DKIM and DMARC records then apply to it. Publish the records Constant Contact shows you before you raise your DMARC policy.

What should I watch for with Constant Contact email?

A forged email can copy the look of a Constant Contact message from any address. Read the address it came from, not the name shown, before you open a link or make a payment.