guter Riecher!
https://www.eff.org/https-everywhere/faq
ZitatQ. Why does HTTPS Everywhere use encrypted.google.com? It looks different...
A. The HTTPS version of Google at encrypted.google.com looks different, and sometimes omits links and buttons, that are on the http://www.google.com domain. In the past, HTTPS Everywhere had to use encrypted.google.com because that was the only way to perform searches over https. It is now possible to use https://www.google.com, but we continue to use the encrypted.google.com subdomain, because it provides slightly better security properties.
Theoretisch müsste man ja selbst ein ruleset definieren können, was vorgibt, wohin umgeleitet wird, aber wo man dieses einfügt habe ich noch nicht entdeckt...