You can point a Squarespace-registered domain at Cloudflare nameservers when Squarespace exposes the custom nameserver setting for that domain. Plenty of owners inherited from Google Domains find the option missing, greyed out, or blocked by a 60-day lock. The durable fix is transferring the registration to a registrar that treats DNS as yours.
Why owners want Cloudflare nameservers on a Squarespace domain
Three reasons come up over and over. The domain needs to point at a new host while the old Squarespace site stays live during a rebuild. The owner wants a WAF, page rules, and redirect logic at the edge. Or the domain has outgrown a single website and now carries mail, a help desk, a booking tool, and two subdomains that need records the platform panel handles awkwardly.
Squarespace sold the domain as part of a bundle, and the DNS panel reflects that. It exists to connect a Squarespace site and an email provider. That is fine until the domain becomes infrastructure rather than an accessory to one page, which is the moment most small businesses hit around year three.
According to Squarespace's own announcement of the deal, the Google Domains acquisition covered approximately 10 million domains across 180 countries (2023). Google Domains customers were used to a registrar that did nothing except register and resolve. They were handed a website platform that also happens to hold their DNS, and the difference shows up the first time they try to delegate to Cloudflare.
What Squarespace restricts on domain DNS
Squarespace manages DNS for domains it registers, and the custom nameserver control is not consistently available across every account and domain state. Domains actively connected to a Squarespace site, domains inside a transfer lock window, and some migrated Google registrations are where owners report the option missing entirely.
Check first, before you plan anything. Open Domains, pick the domain, and look for a nameservers section separate from the DNS records list. One of three things is true:
- The setting is there and editable. You can delegate to Cloudflare without transferring the registration. Do the record work first anyway.
- The setting is there but locked. Usually a lock window or an active site connection. Note the date the lock expires.
- The setting is not there at all. Transfer the registration out. That is the whole answer, and it is cheaper than the alternative.
Even when delegation works, you are still renewing a domain at a website company. Squarespace lists .com renewals at $20/yr. Cloudflare Registrar sells at wholesale cost with no markup, which puts a .com in the $10-$11/yr range including the ICANN fee. On one domain that is coffee money. On a portfolio of 40 client domains it is $400 a year for nothing, which is the kind of line item that quietly funds a competitor.
How to move DNS to Cloudflare without downtime
The order matters more than the individual steps. Build and verify the destination zone before you touch nameservers, because a nameserver change is not reversible inside the TTL window. Resolvers that already picked up Cloudflare will not go back just because you clicked undo.
- Inventory everything. Screenshot or export the full Squarespace DNS record list. A and AAAA records, the www CNAME, MX records, every TXT record (SPF, DKIM, domain verification strings for Google, Microsoft, Meta, Klaviyo), and any SRV records. The verification TXT records are what people forget, and losing them means re-verifying a mail domain under time pressure.
- Lower TTLs. Drop the TTL on your A, CNAME, and MX records to 300 seconds. Then wait out the previous TTL, which is often 3600 or 14400 seconds. Skipping this wait is why a "five minute" DNS change turns into four hours of mixed results.
- Create the Cloudflare zone. Cloudflare scans your existing records on import. Treat that scan as a draft, not a copy. Compare it line by line against your inventory. Mail records and TXT records are the ones that come across incomplete.
- Keep records DNS-only for now. While the site still lives on Squarespace, leave the cloud grey. Proxying a Squarespace-hosted site through Cloudflare commonly produces SSL errors and redirect loops because the platform manages its own certificate.
- Disable DNSSEC at Squarespace. If a DS record stays published at the registry while your domain now answers from Cloudflare, validating resolvers will refuse to resolve you. The site does not load slowly. It does not load at all, for a subset of users you cannot identify. Turn DNSSEC off, wait for the DS record to clear, then re-enable it later on Cloudflare's side.
- Change the nameservers. Two Cloudflare nameservers, exactly as assigned to your zone.
- Verify from outside your own browser. Check propagation with a global DNS lookup tool, send a test message to and from the domain, and confirm the MX answers match what you inventoried. Your own machine's cache is the least useful evidence you have.
If something looks wrong after the switch, resist the urge to assume the site was compromised. Resolution problems and hosting problems look identical from the browser, and we wrote a whole walkthrough on how to check DNS before assuming your site was hacked. If DNS terminology in general is still fuzzy, the plain-English DNS guide for site owners covers what each record type does.
How to transfer a Squarespace domain out
Delegating nameservers moves DNS. It does not move the registration, the renewal bill, or the control. If the goal is to stop depending on Squarespace, transfer the domain.
Cloudflare Registrar has one requirement that sets your sequence: the domain must already be using Cloudflare nameservers before Cloudflare will accept the transfer. So DNS first, registration second. If Squarespace will not let you set custom nameservers, you transfer to any registrar that will, point the nameservers at Cloudflare, wait out the lock, then move to Cloudflare Registrar if the pricing matters to you.
The mechanics at Squarespace: unlock the domain, make sure the registrant email on file is one you can actually receive mail at, request the authorization code, then start the transfer at the gaining registrar and approve it. Transfers for gTLDs typically complete within five days and add a year to the expiry date.
Two lock windows will bite you if you do not plan for them. According to ICANN's Transfer Policy, a domain cannot be transferred for 60 days after a prior registrar transfer, and a change to the registered name holder triggers its own 60-day lock (2016). Domains registered or renewed within the last 60 days also sit inside standard registry lock rules. Check the dates before you promise a client a launch date.
| Step | Downtime risk | Timing |
|---|---|---|
| Inventory existing DNS records | None | 15-30 minutes |
| Lower TTLs to 300s | None | Wait out old TTL, up to 4 hours |
| Build and verify Cloudflare zone | None | 30-60 minutes |
| Disable DNSSEC at Squarespace | None if done before the switch | Allow a few hours to clear |
| Change nameservers to Cloudflare | High if records are wrong | Minutes to propagate with low TTLs |
| Unlock, get auth code, transfer registrar | None if DNS already moved | Up to 5 days |
What this costs versus staying on Squarespace
The domain is the small number. The platform underneath it is where the annual spend lives, and it is worth doing the arithmetic before you decide to only move DNS and leave everything else alone.
| Line item | Squarespace | Cloudflare + managed WordPress |
|---|---|---|
| .com renewal | $20/yr list | $10-$11/yr at cost |
| DNS management | Platform panel, limited controls | Full zone control, API, analytics |
| WAF, edge redirects, page rules | Not available | Included on Cloudflare free and up |
| Site platform | $23/mo Business plan, billed annually | $89/mo per site managed WordPress |
| Sales transaction fee | 3% on the Business plan, on top of processing | None from the host |
| Support | Ticket and chat | Under 2 hours during business hours |
A storefront doing $15,000 a month through a Squarespace Business plan pays roughly $450 a month in platform transaction fees before Stripe takes its cut. That single line is five times the platform cost. Owners staring at that number are usually the ones searching for nameserver settings in the first place, because the domain is the first thing that has to move.
The same bundling logic applies to the marketing add-ons Squarespace and most all-in-one platforms include, which we broke down in what you end up paying twice for with bundled marketing tools. Capped email sends and a basic analytics panel are not free. They are priced into the plan whether you use them or not.
Moving the site, not just the domain
DNS is the easy half. Content, URLs, and SEO equity are where a Squarespace to WordPress move either goes cleanly or costs you a quarter of organic traffic. Squarespace URL structures do not match WordPress defaults, so every blog post, product, and gallery page needs a mapped 301. Skip that and you hand Google a site full of 404s on the day you launch.
We do the mapping before the cutover, stage the new site on a subdomain, and flip DNS only after the redirect table is tested against a crawl of the live site. The same sequence we use for migrating off GoDaddy to managed WordPress hosting applies here, with the extra step of exporting Squarespace content and rebuilding templates rather than moving an existing WordPress install.
Once the site is on WordPress, the operational load changes shape. You own updates, backups, and the security surface that a hosted platform used to absorb. That is the tradeoff, and it is why the host you pick matters more than it did on Squarespace. Our plans cover 24/7 monitoring, TopSyde Sentinel for malware detection and removal, and the virtual patching approach described in how managed hosts handle WordPress zero-days. If you want the full scope of what a managed provider should absorb, what managed WordPress hosting covers in 2026 lists it without the marketing gloss, and the stack we run shows the specifics.
Downtime during a migration is not theoretical money. Our analysis of what website downtime costs a business puts the range at $137 to $427 per minute for mid-size sites, which is the entire argument for doing TTLs and DNSSEC in the right order instead of flipping nameservers on a Friday afternoon.
If the domain is stuck and the site needs to move anyway, send us the domain and a link to the current site. We will tell you which locks apply, what the redirect map looks like, and what the migration takes. Plans start at $89/mo per site with a 30-day money-back guarantee, and we handle the migration as part of onboarding.
Frequently Asked Questions
Can I use Cloudflare nameservers without transferring my domain away from Squarespace?
Sometimes. If Squarespace exposes an editable custom nameserver setting for that specific domain, yes, and the registration stays put. If the setting is missing or locked, transferring the registration is the only reliable path. Either way, build and verify the Cloudflare zone before changing anything.
Will moving nameservers break my Google Workspace email?
Only if you forget the records. MX, SPF, DKIM, and any domain verification TXT entries all live in DNS, and they do not follow a nameserver change automatically. Copy them into Cloudflare, confirm they match, then switch. Our guide on business email versus host mailboxes covers why keeping mail separate from your site host is worth it.
How long does a Squarespace domain transfer take?
Typically five days or less for gTLDs once you unlock the domain, retrieve the authorization code, and approve the transfer. ICANN's 60-day locks after a prior transfer or a registrant contact change will block it outright, so check those dates before scheduling a launch.
Should I turn on Cloudflare's proxy while the site is still on Squarespace?
No. Leave records DNS-only until the site moves. Proxying a Squarespace-hosted domain through Cloudflare commonly causes certificate mismatches and redirect loops because the platform issues and serves its own SSL. Enable the proxy after the site is on a host that expects it.
DevOps & Security Lead
12+ years DevOps, Linux & cloud infrastructure certified
Marcus leads infrastructure and security at TopSyde, managing the server fleet and AI monitoring systems that keep client sites fast and protected. Former sysadmin turned WordPress hosting specialist.
