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:
<!-- 404 status code: ombx.io HSTS preloaded: cloud.openmailbox.org lb1.openmailbox.org mail.openmailbox.org smtp.openmailbox.org Redirects: app.openmailbox.org → app.openmailbox.org/login Server not found: autoconfig.openmailbox.org autodiscover.openmailbox.org clouds.openmailbox.org imap.openmailbox.org lhj5d8mf9n.openmailbox.org mail2.openmailbox.org ns1.openmailbox.org ns2.openmailbox.org pop.openmailbox.org smtp3.openmailbox.org td321ajzoi.openmailbox.org translate.openmailbox.org vkeplat7nh.openmailbox.org webmail.openmailbox.org www.webmail.openmailbox.org www.cloud.openmailbox.org www.ombx.io Timeout was reached: forum.openmailbox.org --><ruleset name="OpenMailBox.org"> <target host="openmailbox.org"/> <target host="www.openmailbox.org"/> <target host="app.openmailbox.org"/> <target host="ombx.io"/> <test url="http://ombx.io/KoRjCLGE"/> <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.