Github Page is misconfigured - HTTPs/TLS not working

[mgarciaisaia]

When visiting https://clientjs.org/ (using TLS/HTTPs), the certificate served is only valid for *.github.com instead of clientjs.org. This is most probably a misconfiguration of the repo's settings in Github.

$ curl -v https://clientjs.org/
* Host clientjs.org:443 was resolved.
* IPv6: (none)
* IPv4: 192.30.252.153, 192.30.252.154
*   Trying 192.30.252.153:443...
* Connected to clientjs.org (192.30.252.153) port 443
* ALPN: curl offers h2,http/1.1
* (304) (OUT), TLS handshake, Client hello (1):
*  CAfile: /etc/ssl/cert.pem
*  CApath: none
* (304) (IN), TLS handshake, Server hello (2):
* (304) (IN), TLS handshake, Unknown (8):
* (304) (IN), TLS handshake, Certificate (11):
* (304) (IN), TLS handshake, CERT verify (15):
* (304) (IN), TLS handshake, Finished (20):
* (304) (OUT), TLS handshake, Finished (20):
* 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=GitHub, Inc.; CN=*.github.com
*  start date: Jun  9 00:00:00 2024 GMT
*  expire date: Jun 11 23:59:59 2025 GMT
*  subjectAltName does not match host name clientjs.org
* SSL: no alternative certificate subject name matches target host name 'clientjs.org'
* Closing connection
curl: (60) SSL: no alternative certificate subject name matches target host name 'clientjs.org'
More details here: https://curl.se/docs/sslcerts.html

curl failed to verify the legitimacy of the server and therefore could not
establish a secure connection to it. To learn more about this situation and
how to fix it, please visit the web page mentioned above.