It has been interesting, over the past some years, as a client just to observe the ongoing changes Google has been making to the nature of HTTPS connections to

It has been interesting, over the past some years, as a client just to observe the ongoing changes Google has been making to the nature of HTTPS connections to its properties. Reporting like this appears[1], and -- coincidence or not -- those observations fit into place. ---- [1] Whether regarding three letter acronyms or protocol weaknesses or whatnot P.S. I'm not sure why the downvotes. TLS renegotiation weakness. Perfect forward security. Even earlier, nascent deployment of their own intermediate certificate authority -- which disappeared after some months, only to reappear again more recently (at least, in my Gmail connections). More recently, in addition to maintaining perfect forward security, now also replacing the underlying certificates every three weeks or so -- at least, as based upon the changing validity dates that are easier/quicker to compare in/via the browser interface. I continue to "wonder" where Google comes down in all this... "security/authoritarianism" fracas. If there is a single "Google position". Regardless, they appear to be one of the most proactive parties, from a technical perspective. And politics aside, I continue to think that behind the scenes, there are a lot of people there behind the scenes who want to "do the right thing" and who work hard, within their responsibilities and areas of expertise, to "make it so".