AWS Route 53

How to integrate Amazon Route 53 with Webflow

Route 53 connects to Webflow through DNS configuration rather than through a marketplace app or embedded widget. This infrastructure-level approach provides enterprise DNS capabilities like health checks, traffic routing policies, and DNS management at scale. This provides AWS's global DNS network for your Webflow sites without changing how you design or build in Webflow.

You can connect Route 53 to Webflow through manual DNS configuration in the Route 53 console or by automating DNS management through both platforms' APIs. This guide covers DNS record setup for single sites, subdomain delegation for teams, automated deployment workflows for agencies, and health monitoring for high-availability infrastructure.

Configure DNS records in Route 53 console

Route 53 manages DNS records through hosted zones—containers for DNS records—in the AWS console. This method gives you direct control over DNS configuration without requiring API integration or custom code. Use console configuration when you're setting up individual Webflow sites, need visual confirmation of your DNS records, or want to leverage Route 53's routing policies like geolocation or latency-based routing. The setup involves creating a hosted zone in Route 53, copying DNS values from your Webflow publishing settings, and creating the required records that point to Webflow's infrastructure.

Key capabilities:

• Create hosted zones with Creating a Hosted Zone for your domain in Route 53
• Configure DNS records with Creating Records pointing to Webflow's infrastructure
• Verify DNS propagation using tools like whatsmydns.net to confirm global DNS updates
• Manage SSL certificates through Webflow's automated provisioning after DNS verification

Start by creating a hosted zone for your domain in Route 53. Get the DNS record values from Webflow by opening your site settings, going to the Publishing tab, and viewing your domain's required DNS configuration. Copy the IP addresses for A records and the CNAME target provided by Webflow. Then create DNS records in your Route 53 hosted zone matching Webflow's requirements.

Required DNS records:

• A records pointing your root domain (@) to Webflow IPs from your site settings (typically 198.202.211.1 OR 75.2.70.75 and 99.83.190.102)
• CNAME record for your www subdomain pointing to proxy-ssl.webflow.com OR cdn.webflow.com
• TXT record containing Webflow's domain verification token

Check Webflow's DNS troubleshooting guide for current record values, as Webflow updated DNS infrastructure in April 2025. Always get the exact values from your Webflow site settings rather than using generic documentation.

Important formatting considerations:

Route 53 automatically adds trailing dots to DNS records. When you enter CNAME values like proxy-ssl.webflow.com, Route 53 stores them as proxy-ssl.webflow.com. — this is correct behavior and doesn't require manual adjustment. Remove any existing A or CNAME records for your domain before adding Webflow's records to avoid conflicts.

DNS propagation typically completes within 1-2 hours, though it can take up to 48 hours globally. Use whatsmydns.net to verify your DNS records have propagated. Webflow's SSL certificate provisioning polls for verification every 4 hours, so HTTPS may take up to 24 hours to activate after DNS propagation.

Set up subdomains with separate hosted zones

Route 53 supports subdomain delegation through separate hosted zones. This approach works when different teams manage different subdomains or you need isolated DNS management for specific parts of your domain hierarchy.

Follow AWS's subdomain configuration guide to create a public hosted zone for your subdomain in Route 53. Copy the four NS (nameserver) records from the new subdomain zone. In your parent domain's hosted zone, create an NS record with the subdomain name and paste the four nameserver values. Set the TTL (Time To Live) to 172,800 seconds (48 hours) for stable nameserver delegation.

Add Webflow's required A and CNAME records in the subdomain's hosted zone following the same pattern as root domain configuration. This separation means you can grant different IAM (Identity and Access Management) permissions for subdomain management without exposing parent domain DNS control.

Build with Webflow and Route 53 APIs

The Route 53 and Webflow APIs enable automated DNS configuration, multi-site deployment workflows, and programmatic domain management. Use API integration when you're deploying multiple Webflow sites at once, need automated DNS provisioning for client projects, or want to integrate domain setup into CI/CD pipelines. The setup requires authenticating with both platforms through their respective methods, querying site requirements from Webflow's Sites API, and programmatically creating DNS records in Route 53. See the Webflow Sites API documentation and Route 53 API Reference for complete endpoint details and authentication requirements.

Both APIs require authentication — Webflow uses Bearer tokens with appropriate scopes, while Route 53 uses AWS Signature Version 4 signing. Generate a Webflow API token from your workspace settings with sites:read and sites:write permissions. Configure AWS credentials through IAM (Identity and Access Management) with policies granting Route 53 permissions for hosted zones and record sets.

Core API workflow:

• List Webflow sites with GET /sites to discover domains needing DNS configuration
• Get site details with GET /sites/{site_id} to check hosting status and custom domain requirements
• List hosted zones with ListHostedZones to correlate Route 53 zones with Webflow domains
• Update DNS records with ChangeResourceRecordSets to create or modify records pointing to Webflow
• Publish site with POST /sites/{site_id}/publish to trigger Webflow's DNS verification

Automate DNS for new Webflow sites

Teams deploying multiple Webflow sites benefit from automated DNS configuration that eliminates manual record creation. This pattern works for agencies managing client sites or companies running multiple branded properties.

When you create a new Webflow site, query the Webflow Sites API to get the site ID and domain requirements. Use this data to determine which DNS records Route 53 needs. Create or update a Route 53 hosted zone for the domain, then construct a ChangeResourceRecordSets request with Webflow's required A and CNAME records.

The Route 53 API returns a change ID that you can poll with GET /2013-04-01/change/{Id} to confirm propagation status. Once Route 53 confirms the change is complete, trigger Webflow's publish endpoint to start domain verification. Your automation should handle verification failures gracefully — Webflow rate limits verification checks to 10 attempts per hour per domain.

Monitor DNS health and trigger failover

Route 53's health checks work alongside Webflow hosting to detect outages and route traffic to backup systems. While Webflow provides reliable hosting infrastructure, some enterprises maintain backup static sites for critical business continuity.

Create health checks through CreateHealthCheck that monitor your Webflow site's availability. Configure failover routing policies that switch traffic to backup infrastructure when health checks fail. Route 53 integrates with AWS EventBridge for health status changes that can trigger automated incident response.

Each check requires separate configuration for HTTP/HTTPS endpoints, ping checks, or calculated checks combining multiple health monitors.

What you can build

Integrating Route 53 with Webflow gives you enterprise DNS management for visual site development, automated deployment workflows, and resilient hosting infrastructure.

• Multi-site agency deployments: Build client site provisioning systems that create Webflow projects, configure Route 53 DNS automatically, and verify domain connectivity without manual console work for each deployment.
• Global traffic management: Route visitors through Route 53's geolocation policies to region-specific Webflow landing pages, reducing latency for international audiences while maintaining centralized content management.
• High-availability marketing sites: Configure Route 53 health checks that monitor your primary Webflow site and automatically fail over to static backup pages during outages, maintaining business continuity for revenue-critical pages.
• Subdomain-based campaigns: Delegate Route 53 hosted zones for campaign subdomains to marketing teams, letting them manage DNS for campaign.example.com Webflow sites independently while central IT controls parent domain security.