Squarespace
How to set up SPF, DKIM and DMARC in Squarespace DNS
Add SPF, DKIM and DMARC as custom records on a Squarespace domain, learn how Squarespace merges SPF, and authenticate Email Campaigns.
Check your current setup:
Before you start
SPF, DKIM and DMARC are DNS records that let receiving servers check who may send mail for your domain. Where you add them depends on how the domain reaches Squarespace:
- Registered with Squarespace, or connected with Nameserver Connect: use the Squarespace domains dashboard. This guide follows that path.
- Connected with DNS Connect, or using custom nameservers: add the records at your DNS provider. Records in the Squarespace panel do not apply.
- Bought through Google Workspace: manage the records in the Google Admin console.
Open the domains dashboard, select the domain, click DNS, then DNS Settings, and scroll to Custom Records. Each step below starts with Add record. Squarespace asks for your password or your two-factor method before it saves. Menu names appear here in English, as they do in Squarespace's help center.
Squarespace applies three default TXT records (DKIM, SPF and DMARC) to domains registered with it or connected by nameservers. They block spam from domains that send no mail. Squarespace removes them when you add any custom email record, and you cannot add them back by hand. To restore them, delete the email preset, then remove and re-add the Squarespace default records. Restore these blocking defaults only if the domain intentionally sends no mail. Do not remove an active email preset or authentication records merely to restore defaults.
Step 1: SPF
SPF lists the servers allowed to send mail for your domain. Choose Type TXT, enter @ in Name (or the host your provider gives you) and paste the value in Text. Google publishes this value for domains that send only through Google Workspace:
v=spf1 include:_spf.google.com ~all
Leave out quotation marks. Depending on your nameservers, they can stop an SPF record from working.
Add each SPF value as its own custom record, and Squarespace merges them into one. Refresh the page to see the result. If one value came from a preset, the panel may keep showing them apart, but they still work as one record.
Merging keeps you within the one-record rule. A domain with more than one SPF record returns permerror, under RFC 7208 section 4.5. An SPF check also allows at most 10 DNS lookups (section 4.6.4), so count them after each merge with the SPF Checker.
Step 2: DKIM
DKIM adds a signature to each message. Receivers check it with a public key in your DNS. A selector is the label that tells them which key to fetch.
Copy the records your email provider gives you:
- TXT: the Name is the selector plus
._domainkey, such asgoogle._domainkeyfor the default Google Workspace selector. Thev=DKIM1; …value goes in Text. - CNAME: enter the host your provider gives you in Name and the target in Data.
Squarespace accepts SPF and DKIM records up to 2048 bits, so you usually do not need to split the value. Enter only the host in Name, because Squarespace adds your domain.
If you use Essential Email by Titan, Squarespace says SPF and DMARC are added during setup. You add DKIM by following Titan's instructions.
Squarespace Email Campaigns
Squarespace includes DKIM signing in every campaign. What you do depends on the domain.
Domains registered with Squarespace or migrated from Google Domains are verified automatically. Create your sender details and Squarespace handles the records.
For a domain registered elsewhere, open the Email Campaign settings panel, add a sender name and address, and enter the code sent to that inbox. Under sender details, click Authenticate. Squarespace shows two records to add where your DNS is hosted:
- CNAME: host
squarespace._domainkey, datasquarespace-domainkey.squarespace-mail.com. This is the DKIM record, with the selectorsquarespace. - TXT: host
_dmarc. Inspect an existing record first and preserve its policy, alignment and report destinations; do not overwrite it with the suggested value. Only if no valid record exists, use the new-policy flow in Step 3.
Squarespace no longer requires an SPF record to verify a campaign domain, and it documents no SPF include for campaigns. It also does not publish the domain it signs with or its bounce domain. To confirm DMARC alignment, send yourself a test campaign and read the d= tag in the DKIM-Signature header. That domain must match your From domain or share its organizational domain, which is the name you registered without subdomains. The Email Header Analyzer reads this for you.
A domain with p=reject cannot use its sender details until you verify it. Gmail and other free addresses cannot be verified. When a sender uses a Gmail or Yahoo address, Squarespace generates a custom From address.
Step 3: DMARC
DMARC tells receivers what to do with mail that fails its checks and where to send reports. The current standard is RFC 9989, with aggregate reports in RFC 9990. Those documents, along with RFC 9991, replace RFC 7489.
Inspect _dmarc first. If a valid record exists, edit it and preserve its policy, alignment, subdomain settings and report destinations. Only if none exists, click Add record, choose Type TXT, enter _dmarc in Name and use this monitoring example in Text with your reporting address:
v=DMARC1; p=none; rua=mailto:dmarc@example.com
The p=none policy states no handling preference, so you can read reports before you enforce anything.
Keep one DMARC record: RFC 9989 §4.10 discards multiple policy records at one name. Merge compatible rua destinations with commas while retaining the established policy and alignment settings. Conflicting policies need an owner-reviewed decision based on legitimate mail; do not automatically choose the stricter value.
Email Campaigns presets cannot be edited. Deleting the preset also removes its DKIM CNAME, so schedule a change window, pause campaigns and keep an authenticated fallback if mail must continue. Save the complete existing records and prepare custom replacements before deletion. Recreate the DKIM CNAME immediately and publish one DMARC TXT with the preserved, owner-reviewed policy and reporting destinations. Verify public DNS and a test campaign before resuming.
An email-forwarding rule also adds DMARC. Squarespace documents deleting a conflicting record, but do not remove an established policy or its reporting destinations blindly. Inspect the proposed forwarding record first. Its Email forwarding records cannot be removed while a rule is active, and editability is undocumented. If the setup cannot preserve your policy and rua, stop and consult support or use a forwarding service compatible with them.
Step 4: Check
DNS changes can take 24 to 48 hours. Then run the SPF Checker, the DKIM Checker with your selector and the DMARC Checker.
Preserve your existing policy while authenticating these services. For a first deployment, collect representative reports at p=none; consider p=quarantine only after fixing every legitimate stream. Assess p=reject separately: it is optional, needs aligned DKIM, and RFC 9989 §7.4 advises against it for domains whose users post to Internet mailing lists. If you still choose it, compare at least a month of monitoring with an equally long quarantine period, including forwarding and infrequent mail. Receiving servers decide the final handling.
Common problems
Custom records not savedwhen adding SPF. Prefer editing the existing record. If a delete-and-recreate is necessary, prepare the complete merged record first, preserve every legitimate sender, use a change window and keep aligned DKIM as a fallback. Recreate one SPF immediately and verify DNS before resuming affected mail.Custom record not saved. We were unable to save this record because it conflicts with an existing record. Identify the duplicate and preserve the active authentication records. Prepare a compatible replacement before removing any SPF, DKIM or DMARC value; ask support if the conflict cannot be resolved safely.Enter valid dataon a TXT or DMARC record. The value is over 255 characters or has an extra character, such as a trailing period. A merged DMARC record with severalruaaddresses can reach this limit. Shorten therualist or split the value into smaller strings, as Squarespace describes.- The record will not save. Gray placeholder text left in Name or Data blocks the save. Replace it with real values.
- SPF does not resolve. Remove any quotation marks from the Text field.
- Full hostname in Name (
_dmarc.example.com). Enter_dmarconly. - Records saved, but nothing changes. The domain uses DNS Connect or custom nameservers, so the Squarespace panel does not apply.
Domain is unauthenticatedstays under sender details. Wait up to 48 hours and check the host and value at your DNS provider. If you deleted the records or verification fails, delete your sender details and create them again.- Two DMARC records from different tools. Merge them into one.
- Forwarding setup fails. Inspect the DMARC conflict. Keep the existing policy and
rua; if forwarding cannot preserve them, stop and consult support or choose a compatible alternative.