Those are the correct IP addresses so it is not a DNS issue.
The output indicates that something on the local system or the local network is preventing the SSL handshake. This could be a firewall, “Net Nanny” software, or a local Windows security policy causing this. The issue could be in the system itself, in a wireless or wired router, or at the ISP level.
If I manually connect to the same IP address using the --connect-to option of curl, the SSL is working correctly:
$ curl --compressed -svo /dev/null https://creacionesisis.netlify.app/ --connect-to creacionesisis.netlify.app:443:18.208.88.157
* Connecting to hostname: 18.208.88.157
* Trying 18.208.88.157:443...
* Connected to 18.208.88.157 (18.208.88.157) port 443
* ALPN: curl offers h2,http/1.1
* (304) (OUT), TLS handshake, Client hello (1):
} [331 bytes data]
* CAfile: /etc/ssl/cert.pem
* CApath: none
* (304) (IN), TLS handshake, Server hello (2):
{ [122 bytes data]
* (304) (IN), TLS handshake, Unknown (8):
{ [19 bytes data]
* (304) (IN), TLS handshake, Certificate (11):
{ [2809 bytes data]
* (304) (IN), TLS handshake, CERT verify (15):
{ [78 bytes data]
* (304) (IN), TLS handshake, Finished (20):
{ [36 bytes data]
* (304) (OUT), TLS handshake, Finished (20):
} [36 bytes data]
* SSL connection using TLSv1.3 / AEAD-CHACHA20-POLY1305-SHA256 / [blank] / UNDEF
* ALPN: server accepted h2
* Server certificate:
* subject: C=US; ST=California; L=San Francisco; O=Netlify, Inc; CN=*.netlify.app
* start date: Jan 31 00:00:00 2025 GMT
* expire date: Mar 3 23:59:59 2026 GMT
* subjectAltName: host "creacionesisis.netlify.app" matched cert's "*.netlify.app"
* issuer: C=US; O=DigiCert Inc; CN=DigiCert Global G2 TLS RSA SHA256 2020 CA1
* SSL certificate verify ok.
* using HTTP/2
* [HTTP/2] [1] OPENED stream for https://creacionesisis.netlify.app/
* [HTTP/2] [1] [:method: GET]
* [HTTP/2] [1] [:scheme: https]
* [HTTP/2] [1] [:authority: creacionesisis.netlify.app]
* [HTTP/2] [1] [:path: /]
* [HTTP/2] [1] [user-agent: curl/8.7.1]
* [HTTP/2] [1] [accept: */*]
* [HTTP/2] [1] [accept-encoding: deflate, gzip]
> GET / HTTP/2
> Host: creacionesisis.netlify.app
> User-Agent: curl/8.7.1
> Accept: */*
> Accept-Encoding: deflate, gzip
>
* Request completely sent off
< HTTP/2 200
< accept-ranges: bytes
< age: 29
< cache-control: public,max-age=0,must-revalidate
< cache-status: "Netlify Edge"; hit
< content-encoding: gzip
< content-type: text/html; charset=UTF-8
< date: Fri, 26 Dec 2025 20:37:17 GMT
< etag: "d3672575e5ab3a4681c66edd52d842f5-ssl-df"
< server: Netlify
< strict-transport-security: max-age=31536000; includeSubDomains; preload
< vary: Accept-Encoding
< x-nf-request-id: 01KDE62HSX3D45KX69E4PB2JR1
< content-length: 801
<
{ [801 bytes data]
* Connection #0 to host 18.208.88.157 left intact
This means the issue is not at Netlify. The issue is in the local system or at the local network level.
Does this happen for all devices on this network or just this one device? If it happens for all devices, that would strongly indicate the issue was at the local network level.
You might also test with curl again but ignoring SSL errors like so:
curl --compressed -k -svo NUL https://creacionesisis.netlify.app/
You might still get the same error but, if not, it may tell us more.
