HTTPS for GitHub Pages
Millions of people rely on GitHub Pages to host their websites and millions more visit these websites every day. To better protect traffic to GitHub Pages sites, as well as…
Millions of people rely on GitHub Pages to host their websites and millions more visit these websites every day. To better protect traffic to GitHub Pages sites, as well as to encourage the broader adoption of HTTPS across the internet, GitHub Pages now officially1 supports HTTPS for all <username>.github.io sites. HTTPS provides a layer of encryption that prevents others from snooping on or tampering with traffic to your Pages site.
You can now visit *.github.io sites using HTTPS and configure HTTPS enforcement for your site. With HTTPS enforcement enabled, any HTTP requests to your github.io site will be transparently redirected to HTTPS.
Starting next Wednesday (June 15, 2016, 12pm PDT), HTTPS enforcement will be required for all new GitHub Pages sites. To enable HTTPS enforcement for your existing *.github.io site, visit the settings page for your site’s repository. Check out the Pages HTTPS documentation for more information.
1 You have been able to request Pages sites over HTTPS for some time, but we refrained from officially supporting it because the traffic from our CDN to our servers wasn’t encrypted until now.
Written by
Related posts
GitHub Availability Report: October 2025
In October, we experienced four incidents that resulted in degraded performance across GitHub services.
TypeScript, Python, and the AI feedback loop changing software development
An interview with the leader of GitHub Next, Idan Gazit, on TypeScript, Python, and what comes next.
What 986 million code pushes say about the developer workflow in 2025
Nearly a billion commits later, the way we ship code has changed for good. Here’s what the 2025 Octoverse data says about how devs really work now.