GitHub Turned Off SHA-1 in HTTPS. It Has Nothing to Do With Git's SHA-1

Fri, 18 Sep 2026 09:00:00 +0530

On September 15, GitHub finished a deprecation it had been broadcasting since April: SHA-1 is no longer accepted in the HTTPS/TLS layer for github.com and its partner CDNs.[1] If a client can’t negotiate a TLS handshake without SHA-1-based signatures, it now gets a connection failure instead of a page, an API response, or a repository. GitHub Enterprise Server is untouched; this only hits github.com, GitHub Enterprise Cloud, and GitHub Enterprise Cloud with Data Residency.[1]

Tls on Kuldeep Pisda

GitHub Turned Off SHA-1 in HTTPS. It Has Nothing to Do With Git's SHA-1