NameSilo
Connect NameSilo domains to Webflow sites through DNS configuration for custom domain hosting.

How to integrate NameSilo with Webflow
Connect NameSilo domains to Webflow through DNS configuration. Manage nameservers and DNS records directly in NameSilo while Webflow handles hosting and SSL certificate provisioning.
Use Webflow’s Quick Connect to automate your domain connect. If you’re comfortable with manual DNS entry, you can also use NameSilo’s pre-configured DNS templates for quick setup or set up manual DNS configuration for custom routing. You can also build with the NameSilo API for automated workflows.
Note: Always get current DNS values directly from your Webflow site settings rather than using older documentation. See Webflow's DNS migration guide for details.
Quick Connect automated setup
Webflow's Quick Connect provides automated domain connection without manual DNS entry. This method uses Entri integration to connect supported domains through an automated workflow.
Access Quick Connect from the domain connection interface in Webflow Site settings. The system detects your registrar and provides guided steps. For NameSilo domains, you may need to provide account credentials or API access for automated DNS record creation.
This method handles DNS verification automatically and uses current DNS values. It requires granting temporary access to your domain registrar account and may not support all domain configurations or TLDs.
Connect with NameSilo's Webflow DNS template
NameSilo provides a pre-configured DNS template that automatically sets up required DNS records for Webflow.
Here is the easiest way you can integrate NameSilo with Webflow.
For new domain registrations:
- Select "Webflow" from the Service Link dropdown during checkout
- DNS records populate after registration completes
- Access Domain Manager to verify record creation
For existing domains:
- Navigate to Domain Manager in your NameSilo account
- Verify the domain uses NameSilo's default nameservers (
NS1.DNSOWL.COM,NS2.DNSOWL.COM,NS3.DNSOWL.COM) - Access DNS settings for your domain
- Apply the pre-built Webflow template
- Allow up to 48 hours for DNS propagation if nameservers were recently changed
Note: Pre-configured templates may contain outdated DNS records due to Webflow's infrastructure changes. Verify the template uses current DNS values from your Webflow site settings, or use Quick Connect instead.
Manual DNS configuration
Manual DNS configuration works when you need custom routing or subdomain setups. This method requires entering specific DNS values that Webflow provides during the domain connection process.
Add your domain in Webflow under Site Settings > Publishing > Production. Webflow generates the required DNS records with current values for their infrastructure.
In NameSilo's DNS Manager, create each record type using the values from Webflow:
- Add the
Arecord for your apex domain - Add the
CNAMErecord forwwwsubdomain routing - Add the
TXTrecord with Webflow's verification code - Save changes and wait for DNS propagation
Important: Do not use DNS values from older guides. Get current record values directly from your Webflow site settings. DNS requirements changed with Webflow's Cloudflare migration.
Manual configuration allows the following use cases:
- Setting up custom subdomains as detailed in Webflow's subdomain connection guide
- Keeping existing DNS records for email or other services
- Creating multi-subdomain architectures
- Testing domain connections before applying templates
Build with Webflow and NameSilo APIs
The NameSilo API supports automated domain management for agencies and developers managing multiple client sites. Combine NameSilo's domain registration and DNS management APIs with Webflow's API to build end-to-end automation for domain provisioning, DNS configuration, and site deployment.
NameSilo's API supports domain registration, DNS record management, domain transfers, and WHOIS operations. Webflow's API handles site creation, publishing, and domain connection.
Common automation patterns include:
- Bulk domain provisioning for multi-client agencies
- Automated domain registration when new Webflow sites are created
- Automated DNS record updates synchronized with site deployments
A typical workflow can look like this:
- Register domains through NameSilo's domain registration API
- Configure DNS records through NameSilo's DNS management API with Webflow's required
A,CNAME, andTXTrecords - Connect the domain to a Webflow site through Webflow's API
This reduces setup time from hours to minutes per domain for agencies onboarding new clients or deploying multiple sites.
What you can build
Integrating NameSilo with Webflow enables custom-branded website delivery with professional domain management.
- Agency client portfolios: Build custom-branded websites where clients own their NameSilo domains while you manage Webflow design and hosting, keeping domain registration and site development separate.
- E-commerce storefronts: Launch online stores with custom domains connecting NameSilo's domain management to Webflow's e-commerce capabilities, including product pages, checkout flows, and customer accounts.
- Marketing landing pages: Deploy campaign-specific landing pages on dedicated domains or subdomains for rapid testing of different domain strategies.
- Multi-site operations: Manage multiple websites across different domains using NameSilo's bulk domain management with Webflow's multi-site hosting.
Frequently asked questions
Three DNS records complete the connection:
- An
Arecord that uses the hostname ‘@' and points to the IP address198.202.211.1for apex domain routing - A
CNAMErecord that uses hostname 'www' and points tocdn.webflow.comforwwwsubdomain traffic - A
TXTrecord that uses hostname '_webflow' with a unique verification code that Webflow provides when you add the domain in Site settings
Create these records through NameSilo's DNS Manager or apply the pre-configured Webflow template that sets up all three automatically. DNS propagation typically completes within 48 hours globally.
Three DNS records complete the connection:
- An
Arecord that uses the hostname ‘@' and points to the IP address198.202.211.1for apex domain routing - A
CNAMErecord that uses hostname 'www' and points tocdn.webflow.comforwwwsubdomain traffic - A
TXTrecord that uses hostname '_webflow' with a unique verification code that Webflow provides when you add the domain in Site settings
Create these records through NameSilo's DNS Manager or apply the pre-configured Webflow template that sets up all three automatically. DNS propagation typically completes within 48 hours globally.
- An
Yes, Webflow automatically generates and renews SSL certificates for custom domains connected through NameSilo. Sites created after November 2018 receive automatic SSL provisioning once DNS records point correctly to Webflow's servers.
Certificate generation begins after DNS verification completes and can take a few hours. Custom SSL certificate uploads are available only for Enterprise plan customers. Avoid using proxy services like Cloudflare during initial setup, as these can interfere with automatic SSL provisioning by preventing Webflow from verifying domain ownership.
Yes, Webflow automatically generates and renews SSL certificates for custom domains connected through NameSilo. Sites created after November 2018 receive automatic SSL provisioning once DNS records point correctly to Webflow's servers.
Certificate generation begins after DNS verification completes and can take a few hours. Custom SSL certificate uploads are available only for Enterprise plan customers. Avoid using proxy services like Cloudflare during initial setup, as these can interfere with automatic SSL provisioning by preventing Webflow from verifying domain ownership.
Yes, you can connect NameSilo subdomains to Webflow sites using manual DNS configuration. Subdomains require a
CNAMErecord pointing tocdn.webflow.comand aTXTrecord for verification, but don't need theArecord used for apex domains.In NameSilo's DNS Manager, create a
CNAMErecord with your subdomain as the hostname (like 'blog' or 'shop') andcdn.webflow.comas the target. Add theTXTrecord with the verification code Webflow provides. This setup works for connecting multiple subdomains to different Webflow sites under a single apex domain.Yes, you can connect NameSilo subdomains to Webflow sites using manual DNS configuration. Subdomains require a
CNAMErecord pointing tocdn.webflow.comand aTXTrecord for verification, but don't need theArecord used for apex domains.In NameSilo's DNS Manager, create a
CNAMErecord with your subdomain as the hostname (like 'blog' or 'shop') andcdn.webflow.comas the target. Add theTXTrecord with the verification code Webflow provides. This setup works for connecting multiple subdomains to different Webflow sites under a single apex domain.The "too many redirects" error typically occurs when you haven't set a default domain in Webflow or when SSL and redirect settings conflict. This is one of the most common post-connection issues.
Fix this by accessing Site settings > Publishing > Production and setting either your apex domain or
wwwsubdomain as the default. After setting the default domain, republish your site to apply the change. This tells Webflow which version of your domain to use and eliminates redirect loops between the apex andwwwversions.The "too many redirects" error typically occurs when you haven't set a default domain in Webflow or when SSL and redirect settings conflict. This is one of the most common post-connection issues.
Fix this by accessing Site settings > Publishing > Production and setting either your apex domain or
wwwsubdomain as the default. After setting the default domain, republish your site to apply the change. This tells Webflow which version of your domain to use and eliminates redirect loops between the apex andwwwversions.Your NameSilo domain should use NameSilo's default nameservers for standard Webflow connections. These are
NS1.DNSOWL.COM,NS2.DNSOWL.COM, andNS3.DNSOWL.COM.These nameservers allow you to manage DNS records through NameSilo's interface while Webflow handles hosting. Verify nameserver settings in your NameSilo Domain Manager before applying DNS templates or manual configuration.
If you recently changed nameservers, allow up to 48 hours for the change to propagate before attempting to connect the domain to Webflow. Alternative nameserver configurations require manual DNS management outside NameSilo's interface.
Your NameSilo domain should use NameSilo's default nameservers for standard Webflow connections. These are
NS1.DNSOWL.COM,NS2.DNSOWL.COM, andNS3.DNSOWL.COM.These nameservers allow you to manage DNS records through NameSilo's interface while Webflow handles hosting. Verify nameserver settings in your NameSilo Domain Manager before applying DNS templates or manual configuration.
If you recently changed nameservers, allow up to 48 hours for the change to propagate before attempting to connect the domain to Webflow. Alternative nameserver configurations require manual DNS management outside NameSilo's interface.

Description
NameSilo is an ICANN-accredited domain registrar that manages over 3 million domains. The platform includes free WHOIS privacy protection, DNS management, email forwarding, and Domain Defender security. NameSilo offers transparent pricing without hidden fees and provides API access for automated domain management.
This integration page is provided for informational and convenience purposes only.


