Domain serving HTTP with Server: Netlify but TLS dropped + cert renewal fails with "doesn't appear to be served by Netlify"

Support
,
1

Site: wearebecreative.netlify.app Custom domain: wearebecreative.com

I have contradictory evidence that this is a backend/edge state issue on your side, not a DNS or customer-config problem. Please investigate the domain’s cert binding on your edge infrastructure.

Evidence the domain IS bound at HTTP:

$ curl -sI http://wearebecreative.com
HTTP/1.1 301 Moved Permanently
Server: Netlify
X-Nf-Request-Id: 01KPSR4XYW4FZK8H6RNMRFRQVN
Location: https://wearebecreative.com/

Evidence the domain is NOT bound at HTTPS: TLS Client Hello is sent, then the connection is dropped with no Server Hello (tested with curl -v --resolve wearebecreative.com:443:75.2.60.5). Browsers show ERR_CONNECTION_CLOSED.

Dashboard: “wearebecreative.com doesn’t appear to be served by Netlify.” Renew certificate fails. Cert record shows Created Mar 29, Expires Jun 27.

Things I’ve already tried (none fixed it):

  • Confirmed DNS: A 75.2.60.5 for apex, CNAME wearebecreative.netlify.app for www. Propagated globally per dnschecker.org.

  • Removed and re-added the custom domain multiple times.

  • Triggered “Clear cache and deploy site”.

  • Verified no Netlify DNS zone conflict at the team level.

  • No CAA records, no GoDaddy forwarding, no domain hold.

  • Let’s Debug returns clean — no Let’s Encrypt issuance blockers.

  • Only one A record at apex.

Given HTTP works but HTTPS doesn’t, and the verification check disagrees with your own edge, this looks like a stale/broken cert binding or SNI mapping that needs to be reset on your end. Please force a re-provision / re-bind for this domain.

Request ID from above for reference: 01KPSR4XYW4FZK8H6RNMRFRQVN