# SPF record for Constant Contact

URL: https://iblockspam.com/spf/constant-contact
Last updated: 2026-11-03

Include: None needed
Where it goes: Not needed
DNS lookups: 0 on your domain

You don't need to add anything to your SPF record for Constant Contact. Constant Contact says receiving servers check its domain's SPF record, not yours, because the bounce address is on its own server domain (in.constantcontact.com). SPF therefore can't align with your From address, and DMARC passes through DKIM self-authentication instead.

## Example records

- Your main domain on Microsoft 365 stays as it is (TXT, host @): `v=spf1 include:spf.protection.outlook.com -all`
- Your main domain on Google Workspace stays as it is (TXT, host @): `v=spf1 include:_spf.google.com ~all`

## Notes

- Constant Contact says all mail it sends gets basic authentication; self-authentication builds reputation under your own domain instead.
- After self-authenticating, use only From addresses on the authenticated domain, or Constant Contact says your emails are likely to bounce.

## How to add it

- Leave your SPF record as it is: Constant Contact says you don't need to add its IP addresses to it.
- In Constant Contact, click your profile name, choose **Settings**, open **Advanced settings** and click **Add self-authentication**.
- Pick the DKIM CNAME method (or the TXT method if several Constant Contact accounts share the domain) and copy the DKIM and DMARC records into your DNS host.
- Click **Check status**, then **Activate** once the domain is ready.

## DKIM and DMARC

Self-authentication publishes DKIM for your domain, either two CNAMEs (`ctct1._domainkey` and `ctct2._domainkey`) or a generated TXT key, plus a DMARC record (see our [Constant Contact DKIM page](https://iblockspam.com/dkim/constant-contact)). Constant Contact points out that SPF alignment isn't required for DMARC to pass, so the aligned DKIM signature is enough.

## Common mistakes

- Adding an include for Constant Contact because an older guide lists one. Its knowledge base says receivers check its SPF record, not yours.
- Expecting SPF to align in DMARC reports. The bounce address stays on Constant Contact's domain, so look at the DKIM result.

**Q: Do I need to add Constant Contact to my SPF record?**
No. Constant Contact says receiving servers check its domain's SPF record, not yours, because the bounce address is its own server address (`@in.constantcontact.com`). Set up DKIM self-authentication instead.

**Q: Why does SPF never align for Constant Contact mail?**
SPF alignment needs the bounce domain to match your From domain. Constant Contact's bounce address is always on its own domain, so it says SPF alignment can't pass, and that DMARC doesn't require it when DKIM aligns.

**Q: What does Constant Contact self-authentication add to DNS?**
DKIM records for your domain (two CNAMEs on `ctct1._domainkey` and `ctct2._domainkey`, or a TXT key) and a DMARC record. Nothing is added to your SPF record.

Sources:
- Constant Contact Knowledge Base: Understanding email authentication: https://knowledgebase.constantcontact.com/articles/KnowledgeBase/5865-overview-of-what-is-involved-in-the-authentication-process
- Constant Contact Knowledge Base: Constant Contact authentication: https://knowledgebase.constantcontact.com/guides/KnowledgeBase/5629-constant-contact-authentication?lang=en_US

---

Source: iBlockSpam, https://iblockspam.com/spf/constant-contact (this is a Markdown copy; the HTML page is canonical). Quote with attribution and a link. Site index for AI assistants: https://iblockspam.com/llms.txt