My site is deployed on Netlify and my DNS is configured as follows (managed at GoDaddy):
A @ → 75.2.60.5
A @ → 99.83.190.102
CNAME www → the-huddle dot netlify dot app
NS are the default GoDaddy nameservers.
DNS propagation is complete globally and nslookup confirms that the apex resolves to the Netlify IPs and www resolves to the Netlify hostname.
Here are my curl results:
curl -I www dot the-huddle dot co
→ HTTP/2 301
→ server: Netlify
→ location: https://the-huddle dot co
So the www hostname works correctly over HTTPS and is served by Netlify.
However:
curl -I https://the-huddle dot co
→ fails at TLS handshake with:
“LibreSSL: tlsv1 alert internal error”
So only the apex HTTPS endpoint is failing at the TLS handshake layer. No HTTP response is returned.
In the HTTPS section of the Netlify UI I see an older Let’s Encrypt certificate entry with this message:
“the-huddle dot co doesn’t appear to be served by Netlify”
The certificate shows:
• Domains: the-huddle dot co, www dot the-huddle dot co
• Created: Nov 26, 2025
I have already:
• Removed and re-added both custom domains
• Confirmed no forwarding exists at the registrar
• Confirmed the domain is not attached to any external hosting
• Verified DNS is correct and propagated globally
• Attempted to renew the certificate multiple times
• Cleared browser/PWA cache
• Tested from multiple devices and networks
Behavior summary:
• www dot the-huddle dot co → works normally over HTTPS
• the-huddle dot co → TLS handshake fails before HTTP response
• Netlify UI indicates the apex does not appear to be served by Netlify, despite DNS resolving to Netlify IPs
It appears that the TLS configuration or certificate for the apex domain may be stuck or corrupted at the Netlify edge network.
Request
Could support please:
-
Fully clear/reset the TLS / certificate state for
the-huddle dot co -
Re-provision a new certificate for
the-huddle dot coandwww dot the-huddle dot co
Thank you very much — happy to provide any further info if needed