Why does my Webflow site show SSL or HTTPS errors?
Confirm the custom domain points to Webflow, check CAA records for certificate providers, and republish after DNS changes settle.
Webflow provisions SSL automatically for connected custom domains when DNS points to Webflow. If browsers show certificate or not secure warnings, confirm the domain is connected under Site settings, Publishing, Production, and that DNS matches Webflow's current records. If your domain uses CAA records, allow both Let's Encrypt and Google Trust Services. Wait for DNS to propagate, then publish again and retest on the custom domain.
Separate a certificate problem from a DNS problem
An HTTPS warning usually means the browser does not trust the certificate for the hostname you typed, or the domain is not serving the Webflow site you expect. Treat those as different checks. First confirm you are testing the custom domain, not only the webflow.io staging subdomain.
Webflow handles SSL certificates for connected domains when DNS stays pointed at Webflow. You do not generate a CSR for the default Webflow certificate. SSL is enabled by default on newer sites and cannot be turned off.
Confirm the custom domain is connected correctly
Open Site settings, Publishing, Production and confirm the custom domain is listed and connected. A paid Site plan is required to connect a custom domain.
If you connect DNS manually, use the A and CNAME values Webflow shows for that site. If Quick connect is available for your registrar, it can write the records for you. After DNS changes, wait for propagation, then publish to the custom domain and retest in a private browser window.
Legacy DNS records can block publishing updates even when an old site still loads. If Site settings asks you to update DNS to Webflow's current records, follow that guidance before chasing certificate settings.
Fix CAA records that block certificate issuance
CAA records tell the internet which certificate authorities may issue certificates for your domain. If you do not use CAA records, Webflow can keep managing certificates automatically and you can skip this section.
If CAA records exist, Webflow requires both of its providers. In your DNS host, allow:
- 0 issue "pki.goog; cansignhttpexchanges=yes"
- 0 issue "letsencrypt.org"
Missing either value can stop provisioning or renewal. Visitors may then see security warnings or fail to load HTTPS. After you save CAA changes, wait for DNS, then check the custom domain again.
Retest with evidence before changing design work
Example: Domain: www.example.com. Problem: browser shows a certificate warning while example.webflow.io loads fine. Expected result: the custom domain loads over HTTPS without a warning and shows the latest published site. Evidence: DNS lookup time, whether CAA records exist, Site settings connection status, and a private-window screenshot of the warning.
Avoid redesigning pages while the certificate is broken. Layout changes will not repair DNS or CAA issues.
Keep domain health in the monthly review
Add a short HTTPS check for the primary custom domain whenever you change registrars, DNS hosts, or CAA records. Certificate renewal depends on DNS continuing to point at Webflow. If domain and SSL issues keep appearing alongside other site work, written monthly Webflow support can keep one person watching DNS, publish status, and certificate health together.
Questions & answers
Does Webflow enable SSL by default?
Yes for sites created after November 14, 2018. SSL is on by default and cannot be disabled on Webflow sites.
When do CAA records matter?
Only if your DNS already uses CAA records. Then you must allow Webflow's certificate providers or certificates may fail to provision or renew.
Which CAA values does Webflow require?
Allow Google Trust Services with 0 issue "pki.goog; cansignhttpexchanges=yes" and Let's Encrypt with 0 issue "letsencrypt.org".
Do I need a paid Site plan for a custom domain?
Yes. Connecting a custom domain requires a paid Site plan for that site.
Sources & further reading
Need a hand with your Webflow site?
View membership