include:emsd1.com lists ActiveCampaign’s sending servers. ActiveCampaign’s mail uses its own return-path by default (acems1.com), and once you add a Mailserver Domain — a CNAME that becomes your custom return-path — ActiveCampaign serves the SPF record for you: “you don’t need to create an SPF record or modify an existing one”.
v=spf1 include:emsd1.com ~all
| Belongs to | ActiveCampaign email marketing |
| Needed on your domain? | No — SPF checks a different domain for its mail, not this record on yours |
What it costs, and is it in your record?
We measure include:emsd1.com as the page opens. Enter a domain: we read its SPF record, follow every include and say whether ActiveCampaign’s is there and what it costs.
What it covers
ActiveCampaign campaigns and automations.
Do you need it?
Not for SPF to pass. “As long as you have set up the Mailserver Domain, SPF will be fully covered … you don’t need to create an SPF record or modify an existing one”, and the Mailserver Domain — available on every Marketing plan — makes SPF align with your domain.
ActiveCampaign says a manual include is “not required for SPF to pass” but has “some benefits”, since “some providers might ignore the industry standards and check the SPF on the Display From”.
Common mistakes
- More than one SPF record, or the include after -all.
- Leftover SenderID (spf2.0) records and legacy includes — ActiveCampaign says to remove them.
- A DMARC policy of quarantine or reject without ActiveCampaign’s DKIM: all its mail then fails.
Questions
Is emsd1.com the same as acems1.com?
acems1.com is ActiveCampaign’s default return-path domain; emsd1.com is the include it gives for your own record. Both list ActiveCampaign’s servers.
Sources
Checked on 26 September 2026 against these official sources:
- SPF DKIM and DMARC Authentication — help.activecampaign.com
- How to merge or update existing SPF records — help.activecampaign.com
- Domains and domain alignment — help.activecampaign.com