How to Add a DMARC Record in Squarespace
Step-by-step guide to adding a DMARC TXT record for domains managed by Squarespace Domains.
If your domain is registered through Squarespace Domains (formerly Google Domains), you can add a DMARC record directly from the Squarespace dashboard. This guide walks through every step so your domain is protected from email spoofing.
Why You Need DMARC
A DMARC record tells receiving mail servers what to do with email that claims to be from your domain but fails SPF or DKIM. Without one, attackers can send phishing mail in your name. With one, you block those messages and receive aggregate reports revealing every service sending mail as you.
Use the DMARC record checker below to confirm whether your domain already has a record before making changes.
Prerequisites
- A Squarespace account with access to the domain
- SPF and DKIM already configured (recommended)
- A mailbox to receive aggregate reports
dmarccreator.com will generate a ready-to-use DMARC record if you need help building one.
Step 1: Open DNS Settings
- Log in to your Squarespace account
- Click Domains
- Select your domain
- Click DNS or DNS Settings
You will see the list of existing DNS records.
Step 2: Add the DMARC TXT Record
- Scroll to the Custom Records section
- Click Add Record
- Fill in the fields
| Field | Value |
|---|---|
| Host | `_dmarc` |
| Type | TXT |
| Data | `v=DMARC1; p=none; rua=mailto:[email protected]` |
Important notes:
- Enter only
_dmarcin the Host field; Squarespace appends your domain - No quotes around the value
- Use a mailbox you actually monitor in the
ruatag
Save the Record
Click Save (or the check mark) to publish the record.
Squarespace Domains migration
If your domain originated at Google Domains and has just migrated, double-check the nameservers are pointing at Squarespace before troubleshooting.
Step 3: Verify the Record
Example DMARC Records
Monitoring Only (Start Here)
v=DMARC1; p=none; rua=mailto:[email protected]
Quarantine Policy
v=DMARC1; p=quarantine; rua=mailto:[email protected]
Reject Policy
v=DMARC1; p=reject; rua=mailto:[email protected]
Editing an Existing Record
- Find the
_dmarcTXT entry in Custom Records - Click the row to edit
- Update the Data value
- Click Save
Common Mistakes
Using @ Instead of _dmarc
@ points to the apex and will not work for DMARC. The host must be _dmarc.
Editing SPF by Mistake
Squarespace domains often already have an SPF TXT record. Make sure you are editing the DMARC record (the one starting with v=DMARC1) and not touching SPF.
Multiple DMARC Records
Two _dmarc TXT records cause receivers to ignore DMARC entirely. Delete older duplicates.
Forgetting to Publish
Some Squarespace DNS changes require confirming with Save. If you navigate away first, the change is lost.
What To Do After Publishing
p=none is only observation. To actually block spoofing:
- Collect aggregate reports for 2-4 weeks
- Fix any senders failing SPF or DKIM alignment
- Move to
p=quarantine - Advance to
p=reject
The DMARC enforcement guide covers the full rollout.
Complete Checklist
- [ ] Opened Squarespace DNS settings
- [ ] Added a TXT record with host
_dmarc - [ ] Used a valid
mailto:rua address - [ ] Saved the record
- [ ] Verified with the DMARC checker
Monitor Your DMARC Records
Checking once is good. Monitoring continuously is better. The Email Deliverability Suite watches your SPF, DKIM, DMARC, and MX records daily and alerts you when something breaks.
Never miss a DMARC issue
Monitor your SPF, DKIM, DMARC and MX records daily. Get alerts when something breaks.
Start Monitoring