How to Add an SPF Record in Squarespace

Squarespace handles your website beautifully, but it won't set up email authentication for you. If you're using a domain registered through Squarespace (or pointing nameservers to Squarespace) and sending email with Google Workspace, Microsoft 365, or any other provider, you need to add an SPF record manually.

Without an SPF record, receiving mail servers can't verify that your emails are actually coming from you. The result: your messages land in spam, or get rejected entirely.

This guide walks you through adding an SPF record in Squarespace DNS, including the quirks you should know about.

What You Should Know About Squarespace DNS

Before diving into the steps, there are a couple of things worth understanding about how Squarespace handles DNS.

Squarespace offers basic DNS management. It supports A records, AAAA records, CNAME records, MX records, and TXT records -- which covers everything you need for email authentication. However, the interface is more limited than dedicated DNS providers like Cloudflare or Route 53.

Key limitations to be aware of:

• Squarespace doesn't support all DNS record types (no SRV records, for example)
• There's no bulk import or export for DNS records
• TTL values are fixed and can't be customized
• If you need advanced DNS features, consider pointing your domain's nameservers to Cloudflare while keeping your site on Squarespace

For SPF, DKIM, and DMARC records specifically, Squarespace's DNS works fine. You just need TXT records, and those are fully supported.

Step-by-Step: Adding an SPF Record in Squarespace

SPF Record Examples for Squarespace Domains

Since Squarespace doesn't provide email hosting, your SPF record depends on which email provider you use with your domain.

Squarespace + Google Workspace

v=spf1 include:_spf.google.com -all

The most common setup for Squarespace users. Google Workspace handles all email for the domain. If you're still testing, use ~all instead of -all until you've confirmed deliverability.

Squarespace + Microsoft 365

v=spf1 include:spf.protection.outlook.com -all

For domains using Outlook or Exchange Online through Microsoft 365.

Squarespace + Google Workspace + Mailchimp

v=spf1 include:_spf.google.com include:servers.mcsv.net -all

Google for team email, Mailchimp for newsletters and marketing campaigns. This is a popular combination for small businesses running on Squarespace.

Squarespace + Google Workspace + SendGrid

v=spf1 include:_spf.google.com include:sendgrid.net -all

If your Squarespace site has a contact form or e-commerce functionality that sends transactional email through SendGrid.

Squarespace + Zoho Mail

v=spf1 include:zoho.com -all

Zoho Mail is a common choice for Squarespace users looking for affordable business email.

Common Mistakes with Squarespace SPF Records

Adding Two SPF Records

This is the most frequent error. You follow Google's setup instructions and add their SPF record. Then you set up Mailchimp and add another SPF record. Now you have two TXT records starting with v=spf1, which causes a permanent error.

# WRONG: Two separate TXT records
v=spf1 include:_spf.google.com -all
v=spf1 include:servers.mcsv.net -all

# CORRECT: One combined record
v=spf1 include:_spf.google.com include:servers.mcsv.net -all

Always combine all your email providers into a single SPF record.

Confusing Squarespace Email Forwarding with Email Hosting

Squarespace offers email forwarding for domains, but this is not the same as email hosting. Email forwarding redirects incoming messages to another address. It doesn't send email from your domain. You still need an SPF record for whatever service actually sends your outbound email.

Using the Wrong Host Value

For a root domain SPF record, the host should be @. Some users enter their full domain name or leave the field blank (which may or may not work depending on the Squarespace interface version). Stick with @ to be safe.

Not Considering Cloudflare as an Alternative

If you're finding Squarespace's DNS management too limited -- maybe you need SRV records, custom TTLs, or more advanced features -- you can point your domain's nameservers to Cloudflare. Your Squarespace site will still work (you'll add the appropriate A and CNAME records in Cloudflare), and you'll get a much more powerful DNS management interface.

Squarespace E-Commerce and SPF

If you run a Squarespace online store, your order notifications, shipping confirmations, and receipt emails are sent by Squarespace itself. These emails come from Squarespace's own infrastructure and don't use your domain's SPF record -- they're sent from Squarespace's email addresses.

However, if you've set up a custom email address for customer communication (like support@yourdomain.com through Google Workspace), those emails do need SPF. Make sure your SPF record covers every service that sends email as your domain.

Complete Email Authentication for Squarespace

SPF alone isn't enough. For full email authentication on your Squarespace domain, set up all three protocols:

• DKIM -- Cryptographic signatures that prove your emails haven't been altered. Use DKIM Creator to generate your DKIM keys, then add the CNAME or TXT record in Squarespace DNS.
• DMARC -- The policy that ties SPF and DKIM together and tells receiving servers how to handle failures. Use DMARC Creator to build your policy, then add it as a TXT record with the host _dmarc.

All three records are managed in the same Squarespace DNS settings panel. Together, SPF, DKIM, and DMARC give receiving servers full confidence that your emails are legitimate.

Monitor Your New SPF Record

You've created your SPF record — now make sure it keeps working. The Email Deliverability Suite watches your SPF, DKIM, DMARC, and MX records daily and alerts you when something breaks.