Introduction
Link your free subdomain to a Webflow-published site, configure DNS settings for optimal performance, and enable Webflows automatic SSL certificate provisioning.
What You Will Need
- A Webflow account (free tier works) with a published site
- An is-cool-me subdomain (free at dash.is-pro.dev)
- Access to the is-cool-me DNS dashboard (Cloudflare-powered)
- 10 minutes of free time
Step 1: Publish Your Webflow Site
In Webflow, publish your site at least once to the default webflow.io staging domain. This generates a working HTTPS endpoint that we will point your subdomain to. Make sure your site design and content are ready before connecting a custom domain.
Step 2: Add Your Subdomain in Webflow
Go to your Webflow project settings, click the "Publishing" tab, and scroll to "Custom Domains". Click "Add Custom Domain" and enter your is-cool-me subdomain (e.g., mysite.is-pro.dev). Webflow will display a DNS target — either a CNAME or A record values.
Step 3: Configure DNS in the is-cool-me Dashboard
In your is-cool-me DNS dashboard, add a CNAME record pointing to Webflow's target domain (e.g., proxy-ssl.webflow.com). If Webflow provides A records instead, add those pointing to Webflow's IP addresses. Set proxying to DNS-only (gray cloud) for Webflow compatibility.
Step 4: Enable SSL in Webflow
Back in Webflow, toggle SSL to "Enabled" for your custom domain. Webflow provisions a Let's Encrypt certificate automatically. This process takes 1-5 minutes. Your site will be served over HTTPS once the certificate is active.
Step 5: Publish and Verify
Click "Publish" in Webflow to push the latest changes. Visit your subdomain to confirm the site loads over HTTPS with the correct content. Check that all assets, forms, and interactions work as expected on the custom domain.
Troubleshooting
Webflow shows "Pending SSL": SSL provisioning can take up to 15 minutes with Webflow. Ensure your DNS is set to DNS-only (gray cloud) — proxied (orange cloud) can interfere with Webflow's certificate validation.
Site not loading on custom domain: Verify the DNS record is saving correctly and pointing to Webflow's target. Use the DNS Checker tool on is-cool-me to confirm the record resolves.
Mixed content warnings: If your Webflow site loads resources over HTTP, update all asset URLs to use HTTPS or protocol-relative URLs. Webflow usually handles this automatically when SSL is enabled.