Embedded content loaded from third-party domains (for example, YouTube, Google Analytics, ad networks, or CDNs) may also be affected. You can test this by loading the web page in question in a browser with HTTPS Everywhere installed and pulling down the HTTPS Everywhere rules menu. This will show a list of HTTPS Everywhere rules that were applied as the page was loaded, including rules that might have affected embedded content from other domains.
The stable (as yet unreleased) branch contains the following rule that is enabled by default:
<!-- Could not resolve host: gkskm1438867.br.whoer.net rbysz1438864.br.whoer.net nl3-speed.whoer.net www.tcp.whoer.net tcp9.whoer.net ua3-speed.whoer.net uk2-speed.whoer.net OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to: ca1-speed.whoer.net ca2-speed.whoer.net ch1-speed.whoer.net ch2-speed.whoer.net de1-speed.whoer.net de2-speed.whoer.net de3-speed.whoer.net es1-speed.whoer.net fr1-speed.whoer.net fr2-speed.whoer.net fr3-speed.whoer.net hk1-speed.whoer.net it1-speed.whoer.net nl1-speed.whoer.net nl2-speed.whoer.net nl88-speed.whoer.net nl99-speed.whoer.net pl1-speed.whoer.net ro1-speed.whoer.net ru1-speed.whoer.net ru2-speed.whoer.net ru3-speed.whoer.net ru4-speed.whoer.net se1-speed.whoer.net se2-speed.whoer.net sg1-speed.whoer.net tcp.whoer.net tr1-speed.whoer.net ua1-speed.whoer.net ua2-speed.whoer.net uk1-speed.whoer.net us1-speed.whoer.net us2-speed.whoer.net us3-speed.whoer.net us4-speed.whoer.net Connnection Refused: mail.whoer.net (r) nl33-speed.whoer.net nl44-speed.whoer.net nl55-speed.whoer.net nl66-speed.whoer.net Connnection timed out: nl4-speed.whoer.net nl5-speed.whoer.net Failed to connect, No route to host: us5-speed.whoer.net r: connection refused --><ruleset name="Whoer.net"> <target host="whoer.net"/> <target host="www.whoer.net"/> <!-- hosts referenced here were enumerated by `python3 sublist3r.py -d whoer.net` --> <target host="vpnapi.whoer.net"/> <target host="wime.whoer.net"/> <rule from="^http:" to="https:"/> </ruleset>
The HTTPS Everywhere developers welcome corrections and updates to rules. Please see our developer information and documentation of the ruleset format. If filing a bug in the Tor Project's Trac bug tracker, you can use the shared username and password cypherpunks / writecode; please ensure that the bug is marked as applying to HTTPS Everywhere.
Information current as of:
current release 2d5e1314 2020-08-13 11:58:12 -0700;
next release d250820e 2021-01-22 00:47:53 +0300;
current release 2d5e1314 2020-08-13 11:58:12 -0700;
next release d250820e 2021-01-22 00:47:53 +0300;