Gandi

How to integrate Gandi with Webflow

Connecting your Gandi-registered domain to Webflow removes the webflow.io subdomain from your site URL. You manage DNS records through Gandi's LiveDNS panel while Webflow handles hosting, SSL certificates, and CDN distribution.

You can connect Gandi domains to Webflow through manual DNS configuration or API-based automation for teams managing multiple domains programmatically.

Manual DNS configuration

Manual DNS configuration connects Gandi domains to Webflow sites by adding specific DNS records in Gandi's LiveDNS panel that point to Webflow's hosting infrastructure. This method takes 3 to 48 hours for DNS propagation and provides automatic SSL certificate provisioning once records are verified.

The Webflow manual domain connection guide walks through obtaining your site-specific DNS records. You configure these in Gandi's DNS management interface following Gandi's domain linking documentation.

DNS records required for connections made after November 3, 2025:

• A record pointing @ to 198.202.211.1 configures root domain routing
• CNAME record pointing www to cdn.webflow.com. handles www subdomain (trailing dot required)
• TXT record with hostname _webflow enables domain verification

DNS records required for connections made before November 3, 2025:

• Two A records pointing @ to 75.2.70.75 and 99.83.190.102 configure root domain routing
• CNAME record pointing www to proxy-ssl.webflow.com. handles www subdomain (trailing dot required)
• TXT record with hostname _webflow enables domain verification

Configuration steps:

1. Access your domain in Gandi's dashboard and navigate to DNS Records
2. Remove any conflicting A or CNAME records pointing to old hosting
3. Add Webflow's A record with hostname blank (represents @)
4. Add CNAME record with name www and the appropriate value including the trailing dot
5. Save DNS changes in Gandi
6. In Webflow, go to Site settings > Publishing > Production and add your custom domain
7. Use Check status to verify connection
8. Wait up to 48 hours for full DNS propagation and SSL provisioning

Verification considerations:

DNS changes at Gandi typically propagate within 3 hours but can take up to 48 hours globally. Use whatsmydns.net to check propagation status across different geographic regions. The Webflow DNS troubleshooting guide helps resolve common configuration issues like missing trailing dots or conflicting records.

Build with Webflow and Gandi APIs

API integration enables automated domain provisioning and DNS configuration for agencies managing multiple client sites or SaaS platforms that provision custom domains programmatically. You connect Gandi's Domain and LiveDNS APIs with Webflow's Data API to automate workflows from domain registration through DNS configuration.

This method requires server-side code to coordinate both platforms. Gandi's Domain API (v5) handles domain registration and management, while their LiveDNS API (v5) configures DNS records.

Webflow's Data API (v2) currently supports publishing sites to existing custom domains but does not support programmatically adding custom domains. You must add custom domains through Webflow's Site settings interface before using the API to publish to them.

Authentication requirements:

Both platforms use token-based authentication. Generate a Gandi Personal Access Token with domain and DNS permissions. Create a Webflow API token with site publishing permissions.

Automated domain provisioning

Automated domain provisioning checks domain availability, registers domains, and configures DNS records. This workflow benefits SaaS platforms offering custom domain features or agencies launching multiple client sites simultaneously.

Your application calls Gandi's GET /domains/check endpoint to verify availability, then POST /domains to register. Domain registration through Gandi's API requires complex contact data structures including owner, admin, tech, and billing contacts with approximately 15 required fields each.

Registration also requires prepaid account funding and registry-specific compliance. After registration, you can configure DNS records through POST /livedns/domains/{fqdn}/records with Webflow's required A and CNAME values.

Implementation flow:

1. Check domain availability with GET /domains/check
2. Register domain using POST /domains with complete contact and billing information
3. Wait for registration confirmation (typically 5-15 minutes)
4. Create A record pointing to 198.202.211.1 (or current DNS values) via POST /livedns/domains/{fqdn}/records
5. Create CNAME record pointing www to the appropriate Webflow proxy value
6. Add your custom domain in Webflow's Site settings > Publishing > Production interface
7. Use Webflow's Data API to publish sites to the configured domain
8. Monitor DNS propagation status

Error handling:

Domain registration can fail due to registry restrictions, payment issues, or conflicting ownership. Implement retry logic with exponential backoff. Check DNS record creation responses for conflicts with existing records that must be deleted first.

Webhook-driven DNS updates

Webhook-driven DNS updates respond to Webflow site publishing events by updating DNS configuration automatically. Webflow's site_publish webhook includes domain information in its payload. When you publish a site, this webhook can trigger DNS record updates at Gandi.

Gandi uses a notification system via XML-RPC and SNS rather than REST webhooks, requiring server-side code that acts as middleware to translate between systems. Set up Webflow webhooks for site publishing events, then implement a handler that calls Gandi's LiveDNS API endpoints to update records. This integration pattern requires advanced development work and custom middleware infrastructure.

Implementation pattern:

Your webhook handler receives Webflow events, validates the payload signature, extracts domain and site information from the webhook payload, then calls PUT /v5/livedns/domains/{fqdn}/records/{rrset_name}{rrset_type} to replace DNS records at Gandi. This endpoint replaces all records with the specified name. Store domain-to-site mappings in your database to coordinate changes across both platforms.

What you can build

Integrating Gandi with Webflow enables domain management workflows that combine Gandi's domain infrastructure with Webflow's hosting platform.

• Multi-client agency dashboards: Build a centralized management interface where you provision domains through Gandi's API, configure DNS automatically, and deploy client sites to Webflow
• SaaS platforms with custom domains: Enable customers to connect their own domains through automated DNS verification and SSL provisioning by combining Gandi's DNS API with Webflow's manual domain configuration and API publishing workflow
• Marketing campaign microsites: Launch temporary promotional sites by registering campaign-specific domains at Gandi, pointing them to Webflow landing pages through automated DNS configuration, and decommissioning everything programmatically after the campaign ends
• International domain portfolios: Manage country-specific domains for global brands by registering multiple domains through Gandi's extensive TLD support and routing them to localized Webflow sites with region-specific content