Hypertext Transfer Protocol Secure (HTTPS)
The Essentials
- HTTP layered over TLS for encrypted communication
- Uses port 443 by default
- Required for HTTP/2 and HTTP/3 performance benefits
- Google ranking signal since 2014
- Browsers display Not Secure warning for plain HTTP
Why You Should Care About HTTPS
HTTPS is no longer optional for any website. Every major browser marks plain HTTP sites with a visible "Not Secure" warning in the address bar, which immediately damages user trust. Google confirmed HTTPS as a ranking signal, and HTTP/2 and HTTP/3 - which provide significant performance improvements - require HTTPS.
Beyond the ranking and trust benefits, HTTPS prevents a range of attacks. Without it, anyone on the network path (ISPs, Wi-Fi hotspot operators, or attackers) can read and modify the traffic. This means they could inject ads, malware, or tracking scripts into your pages, redirect users to phishing sites, or steal session cookies to hijack accounts.
For sites that use any form of authentication, handle any user data, or set cookies, HTTPS is essential. Even for purely static informational sites, the browser warning alone is reason enough. The HSTS header and HSTS preload list take this further by preventing any HTTP connection attempts.
How to Test for HTTPS
Check that your site loads over HTTPS by visiting it in a browser and confirming the lock icon appears. Use an SSL checker to verify the certificate is valid and the server redirects HTTP to HTTPS. Also verify that no mixed content warnings appear - these happen when an HTTPS page loads resources over plain HTTP.