The DNS records
DKIM selector squarespace
Type: CNAME · Host: squarespace._domainkey
squarespace-domainkey.squarespace-mail.com
DMARC record
Type: TXT · Host: _dmarc
<unique value shown beside _dmarc in Squarespace>
A domain has one DMARC record; if you already publish one, merge rather than add.
Set it up and turn on signing
- Open the Email Campaigns settings panel, add a sender name and address on your domain, and enter the code Squarespace emails to it.
- Under Sender details, click Authenticate to open the window with the CNAME and TXT records.
- Find where your DNS lives. A domain connected to a Squarespace site with Nameserver connect is edited in the Squarespace domains panel (Domains managed by third-party > Edit > DNS settings > Add Record); with DNS connect, use your provider's dashboard.
- Add both records, matching Squarespace's Type, Host and Data values, and save.
- Records can take up to 48 hours to resolve. The domain is verified when "Domain is unauthenticated" no longer shows under it.
DMARC alignment
Verifying the domain is what lets Squarespace sign campaigns with your domain's selector, so DMARC can pass on DKIM. Squarespace dropped its old SPF record requirement, which means DKIM carries the alignment. If your domain's DMARC policy is p=reject, Squarespace won't let you use the sender details at all until verification succeeds.
Key length and rotation
The CNAME hands the key to Squarespace: squarespace-domainkey.squarespace-mail.com is a name it controls, so it can replace the key behind it without a change in your zone. Squarespace doesn't publish a key length or rotation schedule. When we looked it up on 22 October 2026, the target held a 2048-bit RSA key.
Common mistakes
- Adding records at the wrong place. With DNS connect, the records go at your domain provider, not in Squarespace.
- A second DMARC record. Merge Squarespace's suggestion into your existing
_dmarcrecord. - Mixing up the labels. Squarespace's Type, Host and Data may be called Record, Hostname or Alias, and Points To or Value at your DNS provider.
- Expecting it for a Squarespace domain. Squarespace-hosted and migrated Google Domains names need no records.
Check your Squarespace DKIM key
The selector is filled in for you; add your domain. Free, reads public DNS only.
Frequently asked questions
What is the Squarespace DKIM CNAME?
Host squarespace._domainkey, data squarespace-domainkey.squarespace-mail.com. It is the same for every account. Squarespace also asks for a TXT record at _dmarc with a value unique to you.
Where do I add Squarespace's records if my domain uses Nameserver connect?
In the Squarespace domains panel: click Domains managed by third-party, then Edit, then DNS settings, and under Custom Records click Add Record. With DNS connect, add them at your domain provider instead.
Can I send Squarespace campaigns from a domain with p=reject before verifying it?
No. Squarespace says that if your domain's DMARC policy is p=reject, you can't use your sender details until the domain is verified. Add the DKIM CNAME and _dmarc record first.
Sources
- Squarespace Help: Verify your third-party domain for use with Email Campaigns
- RFC 6376: DomainKeys Identified Mail (DKIM) Signatures
- RFC 8301: Cryptographic Algorithm and Key Usage Update to DKIM
Checked against Squarespace's documentation on October 22, 2026. Providers change their setup screens; if yours differs, follow the values your admin console shows.
DKIM records for other providers
- Microsoft 365CNAME: selector1, selector2
- Google WorkspaceTXT: google
- Zoho MailTXT: you choose (e.g. zoho)
- GoDaddyCNAME: secureserver1, secureserver2
- FastmailCNAME: fm1, fm2, fm3
- Proton MailCNAME: protonmail, protonmail2, protonmail3
- iCloud MailCNAME: sig1
- HostingerCNAME: hostingermail-a, hostingermail-b, hostingermail-c
- Private EmailTXT: privateemail, default (bought before 2 June 2026)
- IONOSCNAME: s1-ionos, s2-ionos, s42582890
- Rackspace EmailTXT: shown in the Cloud Office Control Panel
- Amazon SESCNAME or TXT: <token1>, <token2>, <token3> (Easy DKIM), your own (BYODKIM)
- SendGridCNAME or TXT: s1, s2
- MailgunTXT or CNAME: assigned by Mailgun (e.g. pic, krs, smtp), pdk1, pdk2 (Automatic Sender Security)
- PostmarkTXT: <timestamp>pm (e.g. 20131031155228pm)
- MailjetTXT: mailjet
- SMTP2GOCNAME: shown in SMTP2GO for your domain
- SparkPostTXT: scph<number> (generated, e.g. scph0316), your own (API)
- Elastic EmailTXT: api
- ResendTXT: resend
- MailerSendCNAME: ms1, ms2
- MailchimpCNAME: k2 and a second CNAME (Marketing), mte1, mte2 (Transactional)
- BrevoTXT or CNAME: mail (TXT), 2 CNAMEs from your account
- HubSpotCNAME: hs1-<number>, hs2-<number>
- KlaviyoCNAME: km1, km2 (marketing), kt1, kt2 (transactional), ks1, ks2 (service)
- ActiveCampaignCNAME: acdkim1, acdkim2
- Constant ContactCNAME or TXT: ctct1, ctct2 (CNAME), generated per key (TXT)
- Dynamics 365 Customer InsightsCNAME: CNAME1 and CNAME2 from the wizard (e.g. namkey1)
- MailerLiteCNAME: litesrv
- Campaign MonitorTXT: cm, your own (existing keys)
- KitCNAME: cka
- MarketoTXT: chosen by you in Marketo
- Account Engagement (Pardot)TXT: shown in Expected DNS Entries
- Customer.ioTXT: cio
- Zoho CampaignsTXT: numbered per account (e.g. 2232)
- SalesforceCNAME: you choose two (e.g. example-sf-a, example-sf-b)
- ZendeskCNAME: zendesk1, zendesk2
- Help ScoutCNAME: strong1, strong2
- IntercomCNAME: intercom
- OdooCNAME: odoo
Compare every provider's selectors in one table · SPF record for Squarespace
Related guides
How to find a domain's DKIM selector, and check its key
Find a DKIM selector from the s= tag in an email header, see the selectors Microsoft 365, Google Workspace and common senders use, then check the key.
8 min read SPF, DKIM & DMARCHow to rotate DKIM keys without breaking email
How often to rotate DKIM keys, which key length to use, how to name selectors, and how to rotate in Microsoft 365, Google Workspace and on your own server.
9 min read SPF, DKIM & DMARCDKIM "body hash did not verify" and other DKIM failures: causes and fixes
Fix DKIM failures: body hash did not verify, signature did not verify, no key for signature and short keys. Causes from mailing lists to broken TXT records.
9 min readLast updated