Squarespace Domain & Email Rescue

Who this is for

Squarespace users whose email stopped working or site went down after a domain transfer, renewal, or DNS change.

You'll fix:

Workspace / MX Issues

If your Google Workspace or other email inbox suddenly stops working, it's often because your MX records were deleted or changed during a domain move. We'll show you how to restore them so your email can flow again.

Nameserver Changes

Your nameservers control which company manages your DNS settings. If these are changed incorrectly, your website and email can go offline. We'll cover how to switch nameservers safely.

Auth / EPP Codes & Transfers

When you move a domain between companies, you'll need a secret passcode called an EPP/Auth code. We'll explain how to get it, use it, and avoid delays when transferring your domain.

DNSSEC & Lockouts

Extra security settings like DNSSEC or account locks can block changes or break your domain if left on at the wrong time. We'll explain how to temporarily turn these off during a transfer and re-enable them safely.

Propagation Myths

You may have heard "it takes 48 hours for DNS to update." That's only partly true. With the right settings, most changes are visible in minutes or hours. We'll clear up the myths so you know what's normal and when something is really broken.

1) Fast triage (2-5 minutes)

Check domain status

Make sure your domain is still active and hasn't expired or been suspended. If it has lapsed, your site and email will stop working until it's renewed.

Check Squarespace dashboard

Log in to your Squarespace account and confirm that the domain is visible under your domains. If it's missing entirely, skip ahead to Section 6 on ownership issues.

Look up WHOIS

A WHOIS lookup should show your registrar (the company managing your domain) and the expected nameservers. If these are wrong, your website or email may not work properly.

Check email records

If email has stopped, check that MX records exist and point to your provider (such as Google Workspace).

2) Keep email online during changes

Lower your TTL

Reducing the TTL before making DNS changes means updates spread faster across the internet, helping you avoid long delays if something goes wrong.

Stage email records in advance

Add your SPF, DKIM, and DMARC records before cutting over. This ensures email delivery isn't interrupted during a domain move.

Validate changes

Use tools like dig or online DNS checkers to confirm records are live and correct before switching nameservers.

3) Google Workspace Records

MX (Mail Exchange)

Confirm that your MX records exist and point to Google's mail servers. Without these, email won't arrive in your inbox.

SPF (Sender Policy Framework)

Have a single TXT record that lists which services can send email for your domain. Multiple SPF records break email validation.

DKIM (DomainKeys Identified Mail)

Publish the DKIM key provided by Google Workspace so outgoing mail is signed and trusted by receiving mail servers.

DMARC (Domain-based Message Authentication, Reporting & Conformance)

Start with a monitoring policy (p=none) so you can receive reports. Once you're confident, tighten to reject suspicious mail.

4) Nameserver changes without downtime

Pre-stage records

Before switching nameservers, create the full set of records (A, CNAME, MX, TXT) at the new host to avoid outages.

Reduce TTL

Lowering TTL ahead of time ensures your changes spread quickly when the switch happens.

Verify transition

Check at the registry that both old and new nameservers are in place before removing the old ones to avoid downtime.

5) Transfers & Auth Codes

Unlock your domain

Domains are usually locked to prevent theft. Unlock it before starting a transfer.

Disable privacy & DNSSEC

Turn these off temporarily - otherwise the transfer may fail. You can re-enable them afterwards.

Get the EPP/Auth code

This code is required to authorise the move at your new registrar.

.UK IPS tag

If your domain ends in .uk, the registrar must set the IPS tag to the new provider's name.

6) Can't see/manage your domain?

Match your WHOIS email

WHOIS should list an email address you control. Update it if needed to receive transfer approvals.

Collect proof of ownership

Gather invoices, payment receipts, or business registration documents to prove the domain is yours.

Escalate to support

Use prepared templates to request manual re-association of the domain to your account.

7) Billing/renewal loops

Check auto-renew settings

Ensure auto-renew is enabled and your payment method is up to date to avoid accidental expiry.

Confirm charges

Look for recent charges from your registrar. If payment failed, fix it immediately.

Request manual renewal

If your domain has lapsed, ask support for a manual renewal and to preserve existing DNS records.

8) Post-change validation

Run a DNS check

Use dig yourdomain.tld any @ns to confirm A, AAAA, CNAME, TXT, and MX records are present and correct.

Test email flow

Send and receive test emails to confirm that SPF, DKIM, and DMARC are all passing.

Monitor stability

Keep an eye on your domain for 24-48 hours. If all is stable, you can safely increase your TTL values again.

Appendices

A. Copy-paste DNS templates

Ready-to-use SPF, DKIM, and DMARC examples you can paste into your DNS settings.

B. Email scripts for escalations

Template emails you can send to support teams if you need urgent help regaining control of your domain.

C. Cutover runbook & rollback plan

A step-by-step plan for moving services safely, and what to do if something breaks.

Keep your domain & email online

Follow these steps, and you'll avoid downtime whenever Squarespace or DNS changes come up again.

Go to the Interactive Rescue Checklist

Worried you've missed something?

If you don't feel confident tackling everything in the checklist, we can help.

Get in touch