Guide

Squarespace DNS for Google Workspace and Microsoft 365, record by record

Every record Google or Microsoft asks for goes in your Squarespace domain's DNS Settings. Here is where that is, what to type in each box, and the few Squarespace habits that can quietly stop email working.

Facts checked

At Squarespace, every record for Google Workspace or Microsoft 365 goes in the same place: open your domains dashboard, select the domain, select DNS, then DNS Settings, and under Custom Records select Add record. Pick the type, type @ in the Name box for your main domain, paste the value Google or Microsoft gave you, and save. Squarespace's guide to adding DNS records for email walks the same screen.

That only works when Squarespace answers your domain's DNS. If the domain uses custom nameservers, or is registered elsewhere and connected with DNS Connect, records added in Squarespace do not apply, and they go at that company instead. Our free DNS lookup tells you which in a few seconds.

Adding a record at Squarespace

The same six steps for every record on this page. Only the type, the name and the value change.

  1. Check that Squarespace answers your DNS.

    Run your domain through our DNS lookup and read the nameserver lines. Squarespace's default nameservers may end in .googledomains.com, .nsone.net, .squarespacedns.com or .systemdns.com. If yours name another company, add every record below at that company instead. A Squarespace domain bought through Google Workspace is the one exception: Squarespace says its records are added in the Google Admin console.

  2. Open the domain's DNS Settings.

    Open your domains dashboard, select the domain, select DNS, then DNS Settings, and scroll to Custom Records. Each domain keeps its own records, so check you opened the right one.

  3. Select Add record and pick the type.

    Squarespace asks for your password, or your two-step sign-in, before it lets you add a record. Then choose TXT, MX or CNAME, whichever the tables below say. The box for the value is called Text for a TXT record, Mail Server for MX and Data for CNAME (Squarespace's email records guide).

  4. Type @ for the main domain, never the domain itself.

    Squarespace adds your domain after whatever you type in Name. So @ stands for the main domain, and for a record on a sub name, such as _dmarc or autodiscover, type only that part. A CNAME record cannot use @.

  5. Paste the value exactly, with nothing extra at the end.

    Paste with no quote marks around it, which Squarespace says can stop an SPF record working, and delete any period at the end, which Squarespace cannot save. Replace the gray example text in the boxes; a record left with it does not save.

  6. Save, then check it is public.

    Select Save. Squarespace says a change can take up to 48 hours, though most show sooner. Run the DNS lookup again: once the record shows there, Google and Microsoft can see it too.

Google Workspace records at Squarespace

Google gives you each value in the Google Admin console. Add them in this order: verification first, the mail record once the new mailboxes are ready, then the three records that keep your mail out of spam.

RecordNameValue
Verify the domainTXT@google-site-verification= followed by your code from the Admin console
Receive mailMX, priority 1, or the Google Workspace preset@smtp.google.com
SPFTXT@v=spf1 include:_spf.google.com ~all
DKIMTXTgoogle._domainkeyThe key starting v=DKIM1; that the Admin console generates for you
DMARCTXT_dmarcv=DMARC1; p=none; rua=mailto: followed by an address you read

Verifying the domain

In the Admin console, go to Account, Domains, Manage domains, and select Verify domain. Copy the whole value, including google-site-verification=, and add it as a TXT record with @ in Name and the value in Text. Leave it in place until Google confirms, which Google says can take up to 72 hours. This record proves you own the domain and does not change where your email goes, so it is safe to add while your current email keeps working. If Google still refuses, the usual causes are in Google Workspace domain verification failed.

Pointing mail at Google

Squarespace has a preset for this: on the domain's DNS page, select Add preset, confirm your password or two-step sign-in, choose Google Workspace and select Confirm (Squarespace's Google Workspace guide). It treats either Google's single smtp.google.com record or Google's five older aspmx records as correct. Adding smtp.google.com by hand at priority 1 does the same job. Either way, Google says to remove any other MX records, and Squarespace says leftover MX records stop mail being sent and received. Remove any email forwarding rules on the domain too; Squarespace lists them, beside old MX, SPF and DKIM records, as the cause of Google's Conflicting DNS record error. Make this change only when the new mailboxes exist.

One Squarespace warning before deleting anything: if you sign in to Squarespace with an address at this domain, change your Squarespace login address first. Otherwise the codes Squarespace sends you can stop arriving, and you can be locked out of the account that holds the records.

SPF, DKIM and DMARC

Squarespace gives a domain it registers, or connects by nameservers, three default anti-spam records, an SPF, a DKIM and a DMARC, and removes them automatically once you add records for an email provider. They cannot be added back by hand, so the domain has no protection of its own until you add Google's.

For SPF, Google's value when Workspace is your only sender is v=spf1 include:_spf.google.com ~all, and every other service that sends as you belongs in the same record (Google's SPF guide). Squarespace merges several SPF custom records into one, so delete the SPF entry of any service you are leaving rather than letting it merge in. Our free SPF checker shows the record the world actually sees.

For DKIM, wait 24 to 72 hours after Gmail is turned on. Then, in the Admin console, go to Apps, Google Workspace, Gmail, Authenticate email, and generate a new record. Add it as a TXT record with google._domainkey in Name, and only then select Start authentication (Google's DKIM guide). Squarespace takes SPF and DKIM values up to 2048 bits in one piece, so the key needs no splitting.

Add DMARC last. Google suggests waiting 48 hours after SPF and DKIM, then starting at p=none, which only reports and blocks nothing, and tightening it once the reports show your real mail passing (Google's DMARC guide). Squarespace allows one DMARC record per domain, and its Email Campaigns preset or an email forwarding rule may already have added one, so look for a _dmarc record and edit it rather than adding a second.

Microsoft 365 records at Squarespace

Microsoft's list of host by host guides does not include Squarespace, so the records below follow its guide for any DNS host. In the Microsoft 365 admin center, go to Settings, Domains, select your domain, then DNS records and Manage DNS, and select Continue. With Exchange and Exchange Online Protection selected, open the MX, CNAME and TXT lists to see the values for your domain. Microsoft adds records for you only at hosts that support Domain Connect; otherwise they go in by hand, with the six steps above.

RecordNameValue
Verify the domainTXT@MS=ms followed by the number the admin center shows you
Receive mailMX, priority 0@Your domain's own address ending in .mail.protection.outlook.com, from the admin center
Outlook setupCNAMEautodiscoverautodiscover.outlook.com
SPFTXT@v=spf1 include:spf.protection.outlook.com -all
DKIMCNAME, two recordsselector1._domainkey
selector2._domainkey
The two values the Microsoft Defender portal shows for your domain
DMARCTXT_dmarcv=DMARC1; p=none; rua=mailto: followed by an address you read

Microsoft says to add your users and mailboxes before you change the MX record, set its priority to the highest available, which is usually 0, and remove any MX record still pointing at the old email provider. The same Squarespace login warning applies before you delete one. Microsoft also says Exchange Online needs a TTL under six hours, and Squarespace's email records guide gives its default as 4 hours, inside that limit. If a value you copy ends in a period, delete the period, or Squarespace will not save it.

SPF, DKIM and DMARC

The SPF value above is Microsoft's for a domain that sends mail through Microsoft 365 only. Like Google, Microsoft allows one SPF record per domain; keep the part for any service that still sends as you, and at Squarespace delete the SPF entry of any service you are leaving so it does not merge into the new one. Squarespace's own default anti-spam records go away when you add Microsoft's, as above.

DKIM is turned on in the Microsoft Defender portal, under Email authentication settings, on the DKIM tab. Select your domain and Create DKIM keys, add the two CNAME records it shows, with each name in Name and each target in Data, then switch on Sign messages for this domain with DKIM signatures (Microsoft's DKIM guide).

Microsoft recommends DMARC after SPF and DKIM, starting at p=none and moving to quarantine and then reject as the reports confirm your real mail passes (Microsoft's DMARC guide). Edit an existing _dmarc record rather than adding a second.

Mistakes that stop email working

Each of these is quick to avoid and slow to untangle once mail has gone missing.

  • Adding records in Squarespace when Squarespace does not answer the DNS. Check the nameservers first. With custom nameservers or DNS Connect, Squarespace says records added in its panel do not apply to the domain.
  • Typing the domain in the Name box. Squarespace adds the domain itself. Use @ for the main domain and only the short part, such as _dmarc, for everything else.
  • Leaving a period or quote marks on the value. Squarespace cannot save a value that ends in a period, and quote marks can stop an SPF record working. Paste the bare value.
  • Deleting MX records while your Squarespace login is on the domain. If your Squarespace sign-in address is at this domain, change it first, or the codes you need to get back in can stop arriving.
  • Leaving old MX records or forwarding rules in place. Google and Microsoft both say to remove other MX records, and Squarespace names forwarding rules as a cause of Google's conflict error.
  • Switching MX before the new mailboxes exist. Incoming mail follows the MX record once the change spreads. Verify the domain, set up the accounts, then switch.
  • Counting on Squarespace's default anti-spam records. They are removed when you add an email provider's records. Add your own SPF, DKIM and DMARC straight after the switch.
  • Starting DMARC at reject. Google and Microsoft both start at p=none and tighten later, so real mail is not blocked by a setting nobody has watched yet.

Who this is for

  • Businesses whose domain and DNS are at Squarespace, setting up Google Workspace or Microsoft 365
  • Owners with a Squarespace website whose domain is connected through Nameserver Connect
  • Anyone whose Google or Microsoft setup is stuck at the verify your domain step
  • Owners who want to check the SPF, DKIM and DMARC records an earlier setup left behind

When this is not the right fit

  • Domains on custom nameservers or connected with DNS Connect. The records are the same, but they go on that company's DNS screen instead; for GoDaddy, see our GoDaddy DNS guide.
  • Moving existing mailboxes with years of mail in them. The records are the easy part of that job and the order is the hard part, covered in business email migration.

What TechTruePoint can help with

Adding the records takes minutes once you know where they go. Where owners ask for help is finding out who controls the DNS, the order of the switch, the Squarespace settings that quietly change records, and checking that mail really arrives afterwards.

Common questions

We bought Google Workspace through Squarespace. Do we need this guide?

Mostly not. Squarespace says it adds the mail records itself when you sign up for Google Workspace through your Squarespace account, and its Google Workspace preset puts them back if they were deleted. If Google will not verify a domain bought that way, Squarespace has its own verification fixes, starting from the Email panel of the domain.

This guide is for the other cases: Google Workspace bought straight from Google, Microsoft 365, or records that have gone missing and need checking one by one.

Do we have to move our domain or website away from Squarespace?

No. Google Workspace and Microsoft 365 both work with a domain and website that stay at Squarespace. All either one needs is a handful of records in the domain's DNS Settings, which is what this guide covers.

The website keeps running as before. Only the email moves.

Our domain is registered elsewhere and connected to our Squarespace site. Where do the records go?

It depends on how it was connected. Squarespace says a domain connected with Nameserver Connect gets its records in the Squarespace domains dashboard, and one connected with DNS Connect gets them at the domain provider. Our DNS lookup shows which: Squarespace nameservers mean Squarespace, anything else means the provider.

For a domain at GoDaddy or Namecheap, every screen is in our GoDaddy DNS guide and Namecheap DNS guide.

How long until Google or Microsoft sees the new record?

Often within the hour. Squarespace says Google may take 10 minutes to an hour to see a new verification record, and that any change can take up to 48 hours. Google says a new record can take up to 72 hours to be recognized.

Check rather than wait. When our free DNS lookup shows the new record, Google and Microsoft can see it too, and clicking Verify again is all that is left.

Get a Quote

Rather we added the records for you?

Tell us your domain and whether you are moving to Google Workspace or Microsoft 365. We check where your DNS is answered, add every record in Squarespace, and test sending and receiving before we hand it back.

Call now Request a quote