How to add an SPF record on Squarespace

SPF (Sender Policy Framework) is a TXT record on your domain that lists the servers allowed to send email on its behalf. Receivers check it on every message that claims to come from your domain — no SPF record, and your legitimate mail becomes hard to tell apart from spoofed mail.

The record lives at the root of your domain as a single TXT record starting with v=spf1. Exactly one SPF record is allowed — publishing a second one breaks SPF entirely (RFC 7208 treats it as a permanent error).

The record you'll add

TypeTXT
Name@@ means the root of your domain.
Valuev=spf1 include:_spf.google.com ~allThis example authorizes Google Workspace. Your record must list the services that actually send your mail — run the checker below and it generates the exact record for your domain.
TTLThe default 4-hour TTL works; Squarespace says record changes can take 24–48 hours to fully propagate.

Steps on Squarespace

  1. Open your Squarespace Domains dashboard and select the domain.
  2. Go to DNS → DNS Settings and scroll to Custom Records.
  3. Click Add record and choose the record type.
  4. Enter @ (root) or the prefix shown above — Squarespace appends your domain automatically — paste the Value, and save.

Squarespace quirks worth knowing

  • If this domain migrated from Google Domains and still shows legacy "Google Domains DNS", its records are frozen — switch the domain to Squarespace DNS first, then add records.

Provider steps verified against Squarespace: Adding custom DNS records on 2026-07-12.

Get the exact record for your domain

The free SPF checker reads your domain's live DNS, flags what's wrong, and generates the precise SPF record to publish — then rechecks to confirm the fix took.

Run the SPF checker

Frequently asked questions

What goes in the Name field on Squarespace?
Enter @ for the root domain. For subdomains, enter just the prefix — Squarespace appends your domain automatically.
How long until the record is live?
The default 4-hour TTL works; Squarespace says record changes can take 24–48 hours to fully propagate. Receivers that cached your old DNS answers will pick the change up as the previous TTL expires.
Can I have more than one SPF record?
No. RFC 7208 requires receivers to treat multiple SPF records as a permanent error — the same as having a broken record. If you use several sending services, list them all in one record: v=spf1 include:serviceA include:serviceB ~all.