Yesterday, Google released Chrome 90, and with that “HTTPS” is becoming the default protocol if you enter just a hostname into the URL bar without specifying the protocol . This is the latest indication that the EFF’s “HTTPS Everywhere” initiative is succeeding . Browsers are more and more likely to push users to encrypted content. While I applaud this trend, it does have a downside for small internal sites that often make it difficult to configure proper certificates. In addition, browsers are becoming pickier as to what certificates they accept. For example, in the “good old days”, I could set up internal certificates that were valid for 10 years, not having to worry about the expiring. Currently, browsers will reject certificates valid for more than 13 months (398 days) .