SSL Issues and NO SUPPORT from Webflwow!

Does anyone have any idea on how to fix the Webflow SSL Certificate handshake issue I am seeing described here?

My site www.land-stats.com is configured on GoDaddy with the following DNS

I have the domain connected to Webflow and SSL turned on as seen here

I have published the site on Webflow but when I go to the URL I get this error

When I check OpenSSL in my terminal I get this error

% openssl s_client -connect land-stats.com:443

Connecting to 99.83.190.102

CONNECTED(00000006)

80C5C80001000000:error:0A000126:SSL routines::unexpected eof while reading:ssl/record/rec_layer_s3.c:692:


no peer certificate available


No client certificate CA names sent


SSL handshake has read 0 bytes and written 329 bytes

Verification: OK


New, (NONE), Cipher is (NONE)

This TLS version forbids renegotiation.

Compression: NONE

Expansion: NONE

No ALPN negotiated

Early data was not sent

Verify return code: 0 (ok)


Here is my site Read-Only: LINK
(how to share your site Read-Only link)

When you set up your custom domain did you create a TXT record with the hostname _webflow and the value shown in Site settings beginning with “one-time-verification=” (e.g., “one-time-verification=01ab2345-cd67e-89f0-11gh-12i13456j789k”)

I don’t see one in your zone.

I didnt see the onetime verification in GoDaddy so i deleted the domain in Webflow and re-added it using the quickconnect domain and now I see the one-time-verification= in Godaddy.

I then go to republish the production and the staging sites. The staging site works fine with SSL but the production still gets this error:

www.land-stats.com sent an invalid response.
ERR_SSL_PROTOCOL_ERROR

And I see this when checking the certificate for www.land-stats.com where its something about a name mismatch:

When I check just land-stats.com I see this where it says “Failed to Communicate with the Server”



Lastly I sent another support ticket and got a tester for my domain and even after publishing the site correctly I get this:

yet I republish and get this:

This is only a theory, but I’m suspicious of this CAA record, which may be blocking cert issuance. Personally, I’d try temporarily removing that to see if it resolves the problem.

Outside of that, the only time I’ve seen SSL issuance problems correctly configured DNS ( A, CNAME, and TXT records ) is when DNSSEC is enabled and those DNS changes are considered invalid due to a DNSSEC signature mismatch.

I’d try disabling DNSSEC if it’s enabled. You may need to contact your registrar.

On this one you may have missed the hyphen in the domain name.
I think this is the correct report.

https://www.ssllabs.com/ssltest/analyze.html?d=land-stats.com

It would be nice if they gave more details on the “Failed to communicate with the secure server.”, but my money’s on the CAA record. I think the cert isn’t being issued as a result of that record’s restrictions.