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:
<!-- For rules causing false MCB, see Trend_Micro-falsemixed.xml. Other Trend Micro rulesets: - Trend_Micro.de.xml - Trend_Micro.eu.xml - Zero_Day_Initiative.com.xml CDN buckets: - trend-fail.download.trendmicro.com.edgesuite.net - global-web.trendmicro.com.edgesuite.net Nonfunctional domains: - trendmicro.ae * - www.trendmicro.ae ** - trendmicro.be * - www.trendmicro.be ** - trendmicro.com subdomains: - about-threats ** - de *** - community Shows ssl.trendmicro.com - documents Refused - downloadcenter Redirects to forms.trendmicro.com - fr *** - newsroom 500 - uk 403 - trendmicro.co.uk * - www.trendmicro.co.uk ** * Shows eu, mismatched, CN: www.trendmicro.eu ** 503, akamai *** "Server Error", akamai Problematic hosts in *trendmicro.com: - amea ¹ - apac ¹ - blog ² - feeds ³ - free ¹ - housecall ¹ ¹ Akamai ² Mixed css ³ Feedburner Mixed content: - Scripts: - On blog from corelib * - On blog from ajax.googleapis.com * - css on blog from blog * - Images on blog from blog * - favicon on apac, free, housecall from apac.trendmicro.com - Bugs: - On blog from edge.quantserve.com * - On blog from platform.twitter.com * * Secured by us --><ruleset name="Trend Micro.com (partial)"> <!-- Direct rewrites: --> <target host="trendmicro.com"/> <target host="blog.trendmicro.com"/> <target host="corelib.trendmicro.com"/> <target host="esupport.trendmicro.com"/> <target host="forms.trendmicro.com"/> <target host="go.trendmicro.com"/> <target host="go2.trendmicro.com"/> <target host="ssl.trendmicro.com"/> <target host="www.trendmicro.com"/> <!-- Complications: --> <target host="feeds.trendmicro.com"/> <!-- Exclude pages so as to avoid false MCB: --> <exclusion pattern="^http://blog\.trendmicro\.com/(?![\w-]+/files/|wp-content/)"/> <!-- +ve: --> <test url="http://blog.trendmicro.com/author/rikferguson/"/> <test url="http://blog.trendmicro.com/page/2/"/> <test url="http://blog.trendmicro.com/websites-use-https/"/> <!-- -ve: --> <test url="http://blog.trendmicro.com/wp-content/uploads/2013/07/simply-security-logo.png"/> <!-- Not secured by server: --> <!--securecookie host="^esupport\.trendmicro\.com$" name="^ASP\.NET_SessionId$" /--> <!--securecookie host="^forms\.trendmicro\.com$" name="^PHPSESSID$" /--> <securecookie host=".+" name=".+"/> <rule from="^http://feeds\.trendmicro\.com/" to="https://feeds.feedburner.com/"/> <rule from="^http:" to="https:"/> </ruleset>
The release branch contains the following rules that are enabled by default:
<!-- For rules causing false MCB, see Trend_Micro-falsemixed.xml. Other Trend Micro rulesets: - Trend_Micro.de.xml - Trend_Micro.eu.xml - Zero_Day_Initiative.com.xml CDN buckets: - trend-fail.download.trendmicro.com.edgesuite.net - global-web.trendmicro.com.edgesuite.net Nonfunctional domains: - trendmicro.ae * - www.trendmicro.ae ** - trendmicro.be * - www.trendmicro.be ** - trendmicro.com subdomains: - about-threats ** - de *** - community Shows ssl.trendmicro.com - documents Refused - downloadcenter Redirects to forms.trendmicro.com - fr *** - newsroom 500 - uk 403 - trendmicro.co.uk * - www.trendmicro.co.uk ** * Shows eu, mismatched, CN: www.trendmicro.eu ** 503, akamai *** "Server Error", akamai Problematic hosts in *trendmicro.com: - amea ¹ - apac ¹ - blog ² - feeds ³ - free ¹ - housecall ¹ ¹ Akamai ² Mixed css ³ Feedburner Mixed content: - Scripts: - On blog from corelib * - On blog from ajax.googleapis.com * - css on blog from blog * - Images on blog from blog * - favicon on apac, free, housecall from apac.trendmicro.com - Bugs: - On blog from edge.quantserve.com * - On blog from platform.twitter.com * * Secured by us --><ruleset name="Trend Micro.com (partial)"> <!-- Direct rewrites: --> <target host="trendmicro.com"/> <target host="blog.trendmicro.com"/> <target host="corelib.trendmicro.com"/> <target host="esupport.trendmicro.com"/> <target host="forms.trendmicro.com"/> <target host="go.trendmicro.com"/> <target host="go2.trendmicro.com"/> <target host="ssl.trendmicro.com"/> <target host="www.trendmicro.com"/> <!-- Complications: --> <target host="feeds.trendmicro.com"/> <!-- Exclude pages so as to avoid false MCB: --> <exclusion pattern="^http://blog\.trendmicro\.com/(?![\w-]+/files/|wp-content/)"/> <!-- +ve: --> <test url="http://blog.trendmicro.com/author/rikferguson/"/> <test url="http://blog.trendmicro.com/page/2/"/> <test url="http://blog.trendmicro.com/websites-use-https/"/> <!-- -ve: --> <test url="http://blog.trendmicro.com/wp-content/uploads/2013/07/simply-security-logo.png"/> <!-- Not secured by server: --> <!--securecookie host="^esupport\.trendmicro\.com$" name="^ASP\.NET_SessionId$" /--> <!--securecookie host="^forms\.trendmicro\.com$" name="^PHPSESSID$" /--> <securecookie host=".+" name=".+"/> <rule from="^http://feeds\.trendmicro\.com/" to="https://feeds.feedburner.com/"/> <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 ff5b4642b 2019-06-27 14:21:20 -0700;
next release c0a0e49cd 2019-10-16 02:46:21 +0300;
current release ff5b4642b 2019-06-27 14:21:20 -0700;
next release c0a0e49cd 2019-10-16 02:46:21 +0300;