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 release branch contains the following rules that are enabled by default:
<!-- Problematic subdomains: Invalid certificate: cl (Invalid Certificate) dl (Invalid Certificate) il (Invalid Certificate) secure (Invalid Certificate) mail.depfile.com (Self-Signed) qn.depfile.com (Self-Signed) ul (cPanel Error Page + Self-Signed) wl (Invalid Certificate) wn (Invalid Certificate) www.depfile.com (Certificate only valid for depfile.com. Redirects.) www.depfile.us (Invalid certificate) www.dipfile.com (Invalid certificate) xl (Invalid certificate) 404: al (404) el (404) fl (404) gl (404) ol (404) pl (404) tl (404) vl (404) yl (404) Other: mn (Apache 2 Test Page, CentOS) nn (Apache Directory Listing, Ubuntu) openbtc (Apache 2 Test Page, CentOS + Self-Signed Certificate) --><ruleset name="DepFile.com"> <target host="depfile.com"/> <target host="dipfile.com"/> <target host="depfile.us"/> <securecookie host=".+" name=".+"/> <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.