SPF record for Constant Contact

Constant Contact sends campaigns and automated email from your contact lists. To send that mail as your domain and pass DMARC, publish the records below and check the alignment notes.

The SPF record

Constant Contact says you don't need an SPF include for it. Its self-authentication page, checked on 4 Sep 2026, says: "Receiving mail servers check our domain's SPF record, not yours, so you do not need to add Constant Contact IP addresses to your SPF record if you have one."

The bounce address on your campaigns sits at in.constantcontact.com, and SPF is checked against the bounce address rather than the one your reader sees. So an SPF pass belongs to Constant Contact and aligns with nothing of yours. The CNAME records they generate are what make DMARC pass.

Whatever you end up publishing, count the lookups afterwards. SPF allows ten DNS lookups across the whole chain of includes. Go over and receivers return a permerror, and SPF fails for every sender in the record. Our free SPF checker follows every include and gives you the count.

DKIM

Constant Contact generates the CNAME record names and values for your account, along with a DMARC record, and shows them once you start self-authentication. Copy them from that screen. A set copied from another account points at the wrong host and never verifies.

Confirm it afterwards by sending yourself a campaign and checking that the signature's d= is your domain rather than Constant Contact's. That check works whatever the records turn out to be called.

DMARC alignment with Constant Contact

DMARC passes when SPF or DKIM passes and the domain it authenticated matches the domain in your visible From address. A provider can pass both checks for its own domain while your mail fails DMARC.

• Constant Contact signs with its own domain until self-authentication is finished, which fails DMARC alignment under any enforcing policy.
• The bounce address stays at in.constantcontact.com after you authenticate. That is fine for DMARC, because alignment on DKIM alone is a pass.
• Lead Gen and CRM is a separate Constant Contact product with its own records, published as CNAMEs at _s1._domainkey and _s2._domainkey.

The DMARC alignment guide covers the general case, and the dmarc=fail page shows how to read the Authentication-Results header.

Verification

Substitute your domain, and run these after the TTL on anything you replaced has expired:

Then send one message through Constant Contact to a Gmail address you control, open Show original, and look for dkim=pass with your domain in header.i. A test message shows what a receiver does with your mail. A DNS lookup only shows what you published.

Our SPF checker gives you the lookup count. The DKIM checker shows whether a selector resolves and whether the key is long enough, and the DMARC checker reads your policy back to you. You can use them free, without an account.

I checked the values here against Constant Contact's own documentation, at Constant Contact knowledge base. Providers change their DNS requirements without much notice. If their screen shows something different from this page, follow their screen and tell us.

A record can be correct and still fail alignment once real mail goes through it. Receivers record that result in the reports they send. We read the reports for you, and on a paid plan we email you the day a new sender fails. See whether this sender passes. Your first domain is free.