What is HTTPS?

One letter separates http:// from https:// and it stands for "secure" — the difference between a conversation shouted across a crowded room and one held through an encrypted line. Over plain HTTP, everything a visitor exchanges with your site travels readable by anyone along the path, from the coffee-shop Wi-Fi to any network in between; over HTTPS, passwords, card numbers and form entries are encrypted, and the content cannot be tampered with in transit. The machinery behind it is the site's SSL/TLS certificate, which vouches for the domain and triggers the padlock. By now HTTPS is not an option but baseline hygiene, for cumulative reasons: browsers stamp plain-HTTP pages with a visible "Not secure" label that repels customers, Google treats HTTPS as a ranking signal and requires it for modern features, payment processors and privacy regulations assume it, and certificates have become free and self-renewing — so the cost excuse is gone. What remains worth checking on your own site: that automatic renewal genuinely works, that every page forces HTTPS including redirects from the old addresses, and that no "mixed content" — resources still loading over HTTP inside a secure page — quietly breaks the padlock.