NS1

How to integrate NS1 with Webflow

NS1 connects to Webflow at the DNS layer for complete control over traffic management while maintaining Webflow's visual development capabilities. Use this integration for geographic traffic routing to reduce latency, automated failover when monitoring detects site issues, or DNS automation in CI/CD pipelines.

You can integrate using manual DNS configuration for most configurations. Or build custom automation using the NS1 API and Webflow API for advanced scenarios like automated DNS provisioning in CI/CD pipelines or dynamic record management based on Webflow CMS changes.

Configure DNS records manually

Manual DNS configuration connects NS1-managed domains to Webflow sites without requiring code. This method requires initial setup plus DNS propagation time. You maintain full control over DNS records while Webflow handles hosting, SSL certificates, and CDN distribution automatically.

This integration requires the following DNS records in NS1:

• Add a paid Site plan in Webflow and configure the custom domain under Site settings > Publishing > Production
• Create two A records with hostname @ pointing to 75.2.70.75 and 99.83.190.102
• Add a CNAME record with hostname www pointing to either proxy-ssl.webflow.com or cdn.webflow.com (check your Webflow domain settings for the correct endpoint)
• Create a TXT record with hostname _webflow containing your verification code from Webflow

DNS propagation takes up to 48 hours, though changes often appear within a few hours. SSL certificate generation happens automatically after domain verification.

Note: NS1 is not supported by Webflow's Quick Connect service, making manual configuration the standard approach for NS1 users.

Build with Webflow and NS1 APIs

API integration enables automated DNS management, dynamic record updates based on CMS content, and custom traffic routing logic. This approach suits DevOps workflows where DNS configuration integrates with deployment pipelines, or scenarios where Webflow CMS changes trigger DNS updates automatically.

Both platforms provide REST APIs. NS1 uses API key authentication via the X-NSONE-Key header, while Webflow supports Bearer token authentication with Site Tokens or OAuth 2.0.

Note: NS1 implements rate limiting using a token bucket algorithm with endpoint-specific limits. Monitor rate limit headers to prevent service interruptions.

#### Automate DNS provisioning

Automated DNS provisioning integrates zone and record creation into deployment workflows. Use this pattern when spinning up new Webflow sites programmatically or managing multiple client sites through a single control plane.

Your automation script can perform these DNS management operations:

• List all zones with GET /zones to retrieve active DNS zones
• Create new zones using POST /zones with JSON body containing zone, ttl, refresh, retry, expiry, and nx_ttl parameters
• Manage DNS records through POST /zones/{zone}/records for creation and GET/PUT/DELETE endpoints for complete CRUD operations
• Retrieve Webflow sites with GET /v2/sites to list accessible sites for automation workflows

Your automation script calls the Webflow API to create or configure a site, then calls NS1 API endpoints to provision DNS zones and create the required A and CNAME records pointing to Webflow's infrastructure. This removes manual DNS configuration for each new site.

Sync CMS content to DNS records

CMS-driven DNS updates enable dynamic infrastructure changes based on content management. Configure Webflow webhooks to trigger DNS updates when CMS content changes, useful for routing traffic based on content structure or managing subdomain mappings for multi-tenant applications.

Webflow webhook events trigger DNS automation:

• Trigger DNS updates on content changes using collection_item_create when new CMS content is added
• Update DNS records dynamically with collection_item_change when CMS content is modified
• Clean up DNS entries using collection_item_delete when CMS items are removed
• Coordinate with publishing through site_publish to synchronize DNS changes with content deployment

Validate webhook authenticity using x-webflow-timestamp and x-webflow-signature headers. Implement HMAC-SHA256 signature verification before processing webhook payloads.

Set up webhook endpoints using POST /sites/{siteId}/webhooks in Webflow. Your webhook handler receives CMS change notifications, extracts relevant data from the payload, and calls NS1's record management APIs to update DNS configuration accordingly.

What you can build

Integrating NS1 with Webflow enables enterprise-grade web infrastructure with intelligent traffic management.

• Global marketing sites with geographic optimization - Build multi-regional marketing sites where NS1's Filter Chain routes visitors to the closest Webflow-hosted content based on real-time latency data, reducing page load times across continents.
• High-availability product sites with automated failover - Create product showcase sites where NS1 health checks monitor Webflow site availability and automatically route traffic to backup infrastructure if the primary site experiences issues.
• Multi-tenant SaaS marketing with dynamic subdomain routing - Deploy customer-specific landing pages as Webflow CMS items where webhook automation creates subdomain DNS records in NS1 for each new customer signup.
• A/B testing infrastructure with DNS-level traffic splitting - Implement marketing experiments by deploying multiple Webflow sites and using NS1's traffic steering to distribute visitors across variants based on custom percentages or user attributes. Note that DNS caching at the browser and ISP level can affect real-time traffic distribution precision.