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:
<!-- Other Intel rulesets: + Cilk_Plus.org.xml + Intel.co.jp.xml + Intel.co.uk.xml + Intel_Free_Press.com.xml + McAfee.xml + McAfee-Mobile-Security.xml + McAfee-MX-Logic.xml + McAfee-SECURE.xml + ScanAlert.xml + SiteAdvisor.com.xml + Threading-Building-Blocks.xml + Ywxi.net.xml Non-functional hosts Couldn't connect to server: - prd1idz.cps.intel.com - mysearch.intel.com - scoop.intel.com - search.intel.com - ssl.intel.com - xdk.intel.com Timeout was reached: - staging-our.intel.com - staging-scoop.intel.com SSL connect error: - chi1.intel.com 4xx client error: - corpredirect.intel.com Different content: - click.intel.com --><ruleset name="Intel.com (partial)"> <target host="intel.com"/> <target host="www.intel.com"/> <target host="ark.intel.com"/> <target host="blogs.intel.com"/> <target host="communities.intel.com"/> <target host="embedded.communities.intel.com"/> <target host="download-software.intel.com"/> <target host="downloadcenter.intel.com"/> <target host="downloadmirror.intel.com"/> <test url="http://downloadmirror.intel.com/28992/eng/Release_Note_16_8_3_1003.pdf"/> <target host="edc.intel.com"/> <target host="educate.intel.com"/> <target host="engage.intel.com"/> <target host="failover.intel.com"/> <test url="http://failover.intel.com/failover/www.intel.com/Assets/contact-numbers.pdf"/> <target host="firmware.intel.com"/> <target host="newsroom.intel.com"/> <target host="origin-software.intel.com"/> <target host="processormatch.intel.com"/> <test url="http://processormatch.intel.com/Resources/Program%20for%20CEC%20Friendly%20MB%20Guidelines%20June%202018%20Public.pdf"/> <target host="registrationcenter.intel.com"/> <target host="sfederation.intel.com"/> <target host="signin.intel.com"/> <target host="software.intel.com"/> <target host="staging-blogs.intel.com"/> <target host="tuningplan.intel.com"/> <target host="www-ssl.intel.com"/> <securecookie host=".+" name=".+"/> <rule from="^http:" to="https:"/> </ruleset>
The release branch contains the following rules that are enabled by default:
<!-- CDN buckets: - corpredirect.intel.com.edgesuite.net - downloadmirror.intel.com.edgesuite.net - inside.intel.com.edgesuite.net - a1578.b.akamai.net - software.intel.com.edgesuite.net - a163.b.akamai.net - software-downloads.intel.com.edgesuite.net - a978.b.akamai.net - downloads-software.intel.com Other Intel rulesets: - ACPICA.org.xml - Cilk_Plus.org.xml - Intel.co.jp.xml - Intel.co.uk.xml - Intel_Free_Press.com.xml - McAfee.xml - McAfee-Mobile-Security.xml - McAfee-MX-Logic.xml - McAfee-SECURE.xml - PathDefender.com.xml - ScanAlert.xml - SiteAdvisor.com.xml - Threading-Building-Blocks.xml - Ywxi.net.xml Nonfunctional domains: - intel.com subdomains: - cache-www ² - corpredirect ³ - mysearch ⁴ - prd1idz.cps ⁵ - processormatch ⁴ - www ² - www-cache ² - scoop ⁴ - staging-our ⁵ - staging-scoop ⁵ - xdk ⁴ - itcommunity.intel.co.uk ⁵ - intellinuxgraphics.org ¹ Redirects to http, akamai ² 503, akamai ³ Shows another domain, akamai ⁴ Refused ⁵ Dropped Problematic subdomains: - chi1 (Expired) - embedded.edc ³ - firmware ⁴ - inside ¹ - search ² - ssl ² ¹ Works, akamai ² Works, self-signed ³ Some paths 404; mismatched, CN: chi1.intel.com ⁴ Incomplete certificate chain Partially covered subdomains: - communities.edc ³ (→ embedded.communities) - newsroom ¹ ¹ Avoiding false/broken MCB, rest handled in -falsemixed.xml ³ Inconsistent redirection behavior Fully covered subdomains: - communities - embedded.communities - downloadcenter - downloads-software - jira.hppd - origin-software - registrationcenter - secure-software - sfederation - signin - software - xdk (→ software.intel.com) Observed cookie domains: - communities - embedded.communities - downloadcenter - edc - engage - freepress - origin-software - secure-software - software - thehub - www Insecure cookies are set for these domains and hosts: - .intel.com - click.intel.com - .click.intel.com - newsroom.intel.com - registrationcenter.intel.com - sfederation.intel.com - signin.intel.com - .signin.intel.com Mixed content: - css on newsroom from www ¹ - Images, on: - blogs, from: - $self ¹ - www ¹ - embedded.communities from $self ¹ - engage from $self ¹ - newsroom from www ¹ - favicon on downloadcenter from www ¹ - Ad/web bug on engage from intel.airprojects.org ² ¹ Secured by us ² Unsecurable --><ruleset name="Intel.com (partial)"> <!-- Direct rewrites: --> <target host="intel.com"/> <target host="www.intel.com"/> <target host="ark.intel.com"/> <target host="blogs.intel.com"/> <target host="click.intel.com"/> <target host="communities.intel.com"/> <target host="embedded.communities.intel.com"/> <target host="download-software.intel.com"/> <target host="downloadcenter.intel.com"/> <target host="downloadmirror.intel.com"/> <target host="edc.intel.com"/> <target host="educate.intel.com"/> <target host="engage.intel.com"/> <target host="failover.intel.com"/> <test url="http://failover.intel.com/failover/www.intel.com/Assets/contact-numbers.pdf"/> <target host="freepress.intel.com"/> <target host="newsroom.intel.com"/> <target host="registrationcenter.intel.com"/> <target host="software.intel.com"/> <target host="origin-software.intel.com"/> <target host="sfederation.intel.com"/> <target host="signin.intel.com"/> <target host="staging-blogs.intel.com"/> <target host="www-ssl.intel.com"/> <!-- Complications: --> <target host="xdk.intel.com"/> <securecookie host=".+" name=".+"/> <!-- Redirects like so: --> <rule from="^http://xdk\.intel\.com/$" to="https://software.intel.com/en-us/intel-xdk"/> <!-- It's impossible to fill the test quota for this rule since for the coverage checker, \? = ? --> <rule from="^http://xdk\.intel\.com/\?$" to="https://software.intel.com/en-us/intel-xdk/"/> <test url="http://xdk.intel.com/?"/> <rule from="^http://xdk\.intel\.com/" to="https://software.intel.com/en-us/intel-xdk/"/> <test url="http://xdk.intel.com/index.php"/> <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 0f162a8c 2021-01-16 01:43:11 +0100;
current release 2d5e1314 2020-08-13 11:58:12 -0700;
next release 0f162a8c 2021-01-16 01:43:11 +0100;