How To Connect Squarespace Domain To Hostinger 2026 Easily

Log in to Squarespace, go to Domains, and select the domain to move. The overview page shows its status as Active, its provider, and expiration date, with a left-hand menu including Overview, DNS, Website, Email, Activity, Permissions, and Billing.

Inside DNS, look for the Domain Nameservers section specifically. That's where the actual switch happens, a few steps from now.

Squarespace's own documentation is blunt about this: custom nameservers are "only necessary if you need to add DNSSEC or use a service that requires them," and warns that if you're not sure why you're changing them, you probably don't need to. Moving hosting to Hostinger is a valid reason. Casually flipping the setting isn't.

In a separate tab, sign in to Hostinger. The nameserver values live in the Websites section: open the domain's dashboard and use the connection wizard, reached through the "Check guide" link next to the domain's status.

Hostinger's own support documentation notes the wizard detects the domain's current DNS provider (Squarespace, here) and links straight to its login page, and that it offers two connection methods: nameservers, or an A record only. The rest of this guide uses nameservers, since that's the full hosting migration; the A record option is worth knowing about too, and comes up again below.

Back in Squarespace's Domain Nameservers section, switch from the default Squarespace servers to custom nameservers and enter the Hostinger addresses exactly as shown, without extra spaces or missing characters. A single wrong character is the most common reason this stalls.

Save the change. Squarespace will warn that content built through its own site tools stops resolving once custom nameservers are active, which is expected since hosting is intentionally moving elsewhere.

Nameserver changes take time to spread across DNS servers worldwide. Hostinger's documentation gives up to 24 hours, usually less; Squarespace's own guidance gives up to 48 hours for changes made on its side, so plan for the longer window instead of the shorter one.

Avoid repeatedly re-saving the nameserver fields in the meantime; it doesn't speed anything up. Open the website's dashboard in Hostinger and look near the top for a status banner. While the domain still points elsewhere, Hostinger shows a red "Domain isn't connected to your website" notice with a Check guide link and a Domain card marked "Action required." That banner is the clearest signal available; once it clears, the connection is live.

Hostinger's documentation states this plainly: pointing a domain by nameservers configures its email records for Hostinger Email, replacing whatever was there before. If the domain's email is handled anywhere else, mail can stop arriving right when the site comes back up.

If that applies, add the correct MX records for the real mail provider inside Hostinger's DNS zone once propagation finishes. The alternative is to go back to Hostinger's connection wizard from step 2 and use the A record method instead of nameservers; Hostinger notes existing email records are left untouched with that option, at the cost of managing the site's other DNS more manually.

As soon as the connection banner clears, check Hostinger's SSL settings for the site to confirm a certificate is issued and active. Most Hostinger plans provision this automatically shortly after the domain resolves, but confirming costs nothing. Load the domain in a browser and check for the padlock icon before calling the migration finished; a site that loads but throws a certificate warning still needs this step.