# SHA-1 in HTTPS on GitHub sunset

By Steven Van · 2026-09-15

GitHub has completed its planned removal of SHA-1 from HTTPS on github.com and partner CDNs; GitHub Enterprise Server is unaffected.

GitHub has disabled SHA-1 in HTTPS for [GitHub](<https://creatorstoolbox.com/tools/github>) on schedule, following the sunset it announced in April. The change applies to github.com and partner CDNs, including GitHub Enterprise Cloud and GitHub Enterprise Cloud with Data Residency; GitHub Enterprise Server is unaffected.

Anything connecting over HTTPS with SHA-1, whether a browser, an API client, or a Git client, will now fail to connect unless it supports newer TLS algorithms. GitHub's [original announcement](<https://github.blog/changelog/2026-04-20-sunsetting-sha-1-in-https-on-github/>) recommended using an up-to-date browser, a modern API client library, and a recent version of Git with an up-to-date TLS backend such as OpenSSL.

[![](<https://github.blog/wp-content/uploads/2026/04/SunsettingSHA-1_Social_01.png>)](<https://github.blog/changelog/2026-04-20-sunsetting-sha-1-in-https-on-github/>)

![GitHub](<https://github.githubassets.com/assets/GitHub-Mark-ea2971cee799.png>)

GitHub

Where the world builds software — Git hosting, pull requests, issues, Actions CI/CD, and Copilot, free for public and private repos.

[View GitHub →](<https://creatorstoolbox.com/tools/github>)

Sources

[Original source](<https://github.blog/changelog/2026-04-20-sunsetting-sha-1-in-https-on-github/>)

[Read SHA-1 in HTTPS on GitHub sunset on Creators Toolbox](<https://creatorstoolbox.com/blog/github-sha-1-in-https-on-github-sunset>)

---
Canonical source: https://creatorstoolbox.com/blog/github-sha-1-in-https-on-github-sunset