Squarespace Domains
Connect Squarespace Domains with Webflow to host sites on custom domains registered through Squarespace's registrar.

How to integrate Squarespace Domains with Webflow
Connect your Squarespace-registered domain to Webflow to use Squarespace's domain registration service while hosting your site on Webflow's infrastructure. This lets you manage domain renewals and settings through Squarespace while serving your Webflow site to visitors who type your custom domain.
You can connect through DNS configuration by pointing your domain's DNS records to Webflow's servers, or build with Webflow APIs to programmatically manage domains and deployments after initial setup.
After DNS setup completes, you can use Webflow's Domains API and Sites Publish API with site-specific Bearer tokens to automate domain management.
Connect with DNS configuration
Connect your Squarespace-registered domain to Webflow by configuring DNS records that point to Webflow's servers. You can use Webflow's automated quick connect feature or manually configure DNS records through Squarespace's domain management interface.
Before starting, you need an active paid Site plan on Webflow. The process requires updating your domain's DNS records in Squarespace and then verifying the connection in Webflow. DNS propagation (the time it takes for DNS changes to spread across the internet's DNS servers globally) depends on your DNS provider settings.
Two connection methods:
- Quick connect domain: Use Webflow's automated setup through Entri integration to handle DNS record configuration for supported registrars. Navigate to site settings, select Publishing > Production, and choose Quick connect domain. This creates the required
Arecords (@pointing to75.2.70.75and99.83.190.102),CNAMErecord (www pointing toproxy-ssl.webflow.com), and verificationTXTrecord automatically. - Manual DNS configuration: Manually add DNS records in your Squarespace domain panel for complete control or if quick connect isn't available. Add
Arecords with host@(representing your root domain) pointing to75.2.70.75and99.83.190.102(Webflow's server IPs), aCNAMErecord with hostwwwpointing toproxy-ssl.webflow.com(Webflow's proxy endpoint), and copy theTXTverification record from Webflow's domain settings.
Access Squarespace’s domain panel by logging into your account, navigating to Settings > Domains, selecting your domain, and accessing DNS Settings. You'll add or modify records here based on Webflow's requirements, outlined in your site settings.
After configuring DNS records, verify the connection in Webflow site settings under Publishing > Domains. Webflow displays DNS verification status with a green checkmark for successful connections, while warnings highlight missing or misconfigured records.
After DNS propagation completes, Webflow automatically provisions SSL certificates. Check certificate status in site settings under your custom domain listing. The process typically completes after successful DNS verification.
Build with Webflow APIs
Once DNS verification succeeds, publish your site to the custom domain through Publishing > Publish to production in Webflow. You can also use the Sites Publish API endpoint to programmatically deploy to specific domains:
POST /sites/{site_id}/publish
Authorization: Bearer {site_token}
{
"customDomains": ["example.com"]
}
After initial DNS setup, use Webflow's Domains API to retrieve domain information programmatically:
GET /sites/{site_id}/domains
Authorization: Bearer {site_token}
The response includes domain status, SSL certificate state, and creation timestamps. This enables automated monitoring of domain health across multiple sites.
API access requires site-specific Bearer tokens (authentication credentials you include in API request headers) from Site Settings > Apps & Integrations > API Access. Tokens require specific scopes (sites:read for domain information, sites:publish for deployments) and expire after 365 days of inactivity.
What you can build
Integrating Squarespace Domains with Webflow lets you use Squarespace's domain registration service while hosting sites on Webflow's infrastructure.
- Multi-domain site deployment: Connect multiple Squarespace-registered domains (yourcompany.com, yourcompany.co, yourcompany.io) to a single Webflow site for international market coverage or brand protection strategies.
- Centralized domain registration: Maintain domain registrations centrally in Squarespace while hosting different sites on Webflow, useful for agencies managing client domains or companies with separate product microsites.
- Custom domain staging workflows: Connect different Squarespace-registered domains to Webflow's staging and production environments, so you can use preview.yourdomain.com for client review before publishing to the primary domain.
- Client domain management: Register domains through Squarespace on behalf of clients, build their sites in Webflow, and transfer domain ownership after project completion while the site remains connected.
Frequently asked questions
You can keep your Squarespace-registered domain when moving a site to Webflow by updating DNS records to point to Webflow's servers instead of Squarespace. The domain remains registered with Squarespace while your site content lives on Webflow.
In your Squarespace domain panel, remove existing DNS records that point to Squarespace hosting (typically
Arecords pointing to Squarespace IPs like198.185.159.144). Then add Webflow's required DNS records following the manual domain connection process. Your original Squarespace site becomes inaccessible once DNS propagates, so complete your Webflow site build before updating DNS.Squarespace domain renewals and management remain in your Squarespace account at Settings > Domains. You'll continue paying Squarespace for domain registration while paying Webflow for site hosting.
You can keep your Squarespace-registered domain when moving a site to Webflow by updating DNS records to point to Webflow's servers instead of Squarespace. The domain remains registered with Squarespace while your site content lives on Webflow.
In your Squarespace domain panel, remove existing DNS records that point to Squarespace hosting (typically
Arecords pointing to Squarespace IPs like198.185.159.144). Then add Webflow's required DNS records following the manual domain connection process. Your original Squarespace site becomes inaccessible once DNS propagates, so complete your Webflow site build before updating DNS.Squarespace domain renewals and management remain in your Squarespace account at Settings > Domains. You'll continue paying Squarespace for domain registration while paying Webflow for site hosting.
No, you don't need to transfer domain ownership. Webflow connects to domains registered with any registrar through DNS configuration, including Squarespace-registered domains. Many users prefer keeping domains registered with their original registrar while hosting sites elsewhere.
No, you don't need to transfer domain ownership. Webflow connects to domains registered with any registrar through DNS configuration, including Squarespace-registered domains. Many users prefer keeping domains registered with their original registrar while hosting sites elsewhere.
DNS propagation time varies depending on your existing DNS record Time To Live (TTL) settings, which tell DNS servers how long to cache your records before checking for updates, and how quickly DNS servers worldwide sync their data. In practice, DNS changes typically take anywhere from a few minutes to 48 hours to propagate fully, with most changes visible within 24 hours.
You can check propagation status using DNS lookup tools that query nameservers globally. Webflow's site settings also display verification status, showing when DNS records successfully point to Webflow servers.
During propagation, some visitors may see your old site (if one existed) while others see your new Webflow site. This happens because different internet service providers cache DNS information at different rates. Avoid making additional DNS changes during this window to prevent extending propagation time.
DNS propagation time varies depending on your existing DNS record Time To Live (TTL) settings, which tell DNS servers how long to cache your records before checking for updates, and how quickly DNS servers worldwide sync their data. In practice, DNS changes typically take anywhere from a few minutes to 48 hours to propagate fully, with most changes visible within 24 hours.
You can check propagation status using DNS lookup tools that query nameservers globally. Webflow's site settings also display verification status, showing when DNS records successfully point to Webflow servers.
During propagation, some visitors may see your old site (if one existed) while others see your new Webflow site. This happens because different internet service providers cache DNS information at different rates. Avoid making additional DNS changes during this window to prevent extending propagation time.
After completing initial DNS setup manually, you can automate publishing to custom domains using Webflow's Sites API. This works well for agencies managing multiple client sites or companies with several product microsites on different domains.
Generate a site-specific API token from Site Settings > Apps & Integrations > API Access with the
sites:publishscope. Use the publishing endpoint to deploy specific sites to their custom domains programmatically. The API accepts domain arrays, allowing selective publishing to staging or production domains based on your deployment workflow. Note that Webflow's API has rate limits of 60 requests per minute, so implement appropriate throttling in your automation scripts.Squarespace doesn't provide APIs for domain registration or DNS management, so the initial DNS configuration requires manual setup through their domain panel. Automation applies only to Webflow's publishing workflow after domains connect successfully.
After completing initial DNS setup manually, you can automate publishing to custom domains using Webflow's Sites API. This works well for agencies managing multiple client sites or companies with several product microsites on different domains.
Generate a site-specific API token from Site Settings > Apps & Integrations > API Access with the
sites:publishscope. Use the publishing endpoint to deploy specific sites to their custom domains programmatically. The API accepts domain arrays, allowing selective publishing to staging or production domains based on your deployment workflow. Note that Webflow's API has rate limits of 60 requests per minute, so implement appropriate throttling in your automation scripts.Squarespace doesn't provide APIs for domain registration or DNS management, so the initial DNS configuration requires manual setup through their domain panel. Automation applies only to Webflow's publishing workflow after domains connect successfully.

Description
Squarespace Domains allows domain registration and DNS management. Domains registered through Squarespace can connect to external hosting providers like Webflow through standard DNS configuration.
This integration page is provided for informational and convenience purposes only.

Greenhouse
Connect Greenhouse's powerful applicant tracking system with Webflow to create dynamic career pages, automate job postings, and streamline your recruitment process. Display live job listings, collect applications, and maintain a seamless candidate experience without manual updates.

Yahoo
Point your Yahoo domain name to Webflow

Wix DNS
Point your Wix domain name to Webflow

OVH
Connect OVH infrastructure with Webflow to add cloud hosting, automated deployments, and scalable storage.

NS1
Connect NS1 with Webflow to manage DNS with traffic routing based on real-time telemetry and geographic data.

One.com
Point your One.com domain name to Webflow

Name.com
Point your Name.com domain name to Webflow

Network Solutions
Connect Network Solutions with Webflow to host your custom domain using automated DNS setup or manual configuration.

Namecheap (registrar-servers.com)
Point your Namecheap domain name to Webflow


