Easy Tech TutsHow to Fix Squarespace Domain Forwarding Not Working 2026 Easily
By Impran M N
Domain forwarding in Squarespace isn't instant — it can take anywhere from a few minutes to 48 hours to fully propagate, especially with SSL enabled, and in the meantime your domain can throw a browser error that looks far more broken than it actually is. If your redirect still isn't working after a while, this guide walks through what a correctly configured forwarding rule looks like, what the failure actually looks like in the browser, and the DNS records worth double-checking before you assume something is wrong.
01Confirm the forwarding rule itself is set up correctly
In your Squarespace domain settings, scroll to the Domain Forwarding section and check the rule against what you intended: the From field is your domain, the To field is the exact destination URL, Redirect Type shows Permanent redirect (the standard choice), and Forwarding Over SSL is switched on. A Last Updated timestamp confirms when the rule was actually saved — if it's older than you expect, your most recent edit may not have gone through.
02Recognize what a still-propagating redirect looks like
Visiting the domain before forwarding has finished propagating typically shows a browser error like "This site can't be reached" with a DNS_PROBE_FINISHED_NXDOMAIN message, rather than a broken-looking Squarespace page. That specific error means the browser couldn't resolve the domain to any address yet — it's a DNS propagation symptom, not evidence that your forwarding rule is misconfigured. Seeing this right after saving a new rule is expected, not alarming.
03Give it time before troubleshooting further
Squarespace states that forwarding changes, especially with SSL enabled, can take up to 48 hours to fully propagate across the internet, though most cases resolve within one to two hours. If it's only been thirty minutes since you saved the rule, the NXDOMAIN error from the previous step is very likely just DNS still catching up — wait before assuming something needs fixing.
04Clear your browser cache or test elsewhere
If it's been over an hour and the redirect still isn't working, your browser may be holding onto old DNS or page data. Open the domain in an incognito or private window, or clear your browser's cache and reload.
If it still fails, try the domain on a completely different network — your phone on cellular data, for instance. If it works there but not on your usual connection, the issue is local DNS caching on your network, not your Squarespace setup.
05Check DNS Settings for leftover records
Go to Settings, Domains, and open DNS Settings for the domain. This page lists every DNS record grouped by the service that created it — a Squarespace Domain Connect CNAME record, MX records for an email provider like Google Workspace, and so on. Look specifically for a leftover A record or CNAME on the same subdomain you're forwarding, like www — even a single stale record here can override the forwarding rule and stop the redirect from firing.
06Remove and re-add the rule as a last resort
If you've waited a reasonable amount of time, cleared your cache, and confirmed there's no conflicting DNS record, delete the forwarding rule using the trash icon next to it, save, wait a minute, and then re-add it from scratch with the same From, To, and SSL settings. This resets the underlying configuration and resolves the rare cases where a rule looks correctly saved in the interface but isn't actually being applied.
Frequently asked questions
How long should I wait before troubleshooting forwarding?
Give it at least an hour or two, since propagation with SSL can take up to 48 hours in some cases, though most rules resolve within one to two hours.
Why does clearing my cache help?
Your browser may still be showing an old cached version of the page or DNS lookup, which an incognito window or cache clear resolves.
What does the DNS_PROBE_FINISHED_NXDOMAIN error actually mean?
It means the browser couldn't resolve your domain to any address at that moment — usually a sign that DNS for the new forwarding rule hasn't finished propagating yet, not that the rule itself is broken.
What if a leftover DNS record is causing the issue?
Even one leftover A record or CNAME on the forwarded subdomain can block the redirect from working — remove it in DNS Settings, being careful not to touch records for unrelated services like email.
Does removing and re-adding the rule actually help?
Yes, it can reset the redirect configuration and resolve cases where the rule appears saved but isn't functioning.
About the author
Impran M N
I've been hooked on technology for as long as I can remember — especially the new tools and AI apps that seem to land every other week. Easy Tech Tuts is where I write up whatever I've just worked out: I do the task in the real product, record the screen, and turn it into the guide I wish I'd found first.
