HTTPS Everywhere Atlas

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:

<!--
	Problematic subdomains:

		- apidocs *
		- blog *
		- br *
		- connect *
		- dev *

	* Works, mismatched


	Partially covered subdomains:

		- support *

	* Avoiding false/broken MCB


	Fully covered subdomains:

		- (www.)
		- api
		- api2
		- app
		- cdn
		- multimedia
		- secure
		- static
		- support-panel


	Mixed content:

		- css, on:

			- apidocs from $self ¹
			- blog from $self ¹
			- connect from $self ¹
			- support from $self ²

		- Images, on:

			- apidocs from $self ¹
			- blog from $self ¹
			- support from $self ²

		- favicon, on:

			- blog from $self ¹
			- support from $self ²

	¹ Not secured by us <= mismatched
	² Secured by us

--><ruleset name="GetResponse.com (partial)">

	<target host="getresponse.com"/>
	<target host="api.getresponse.com"/>
	<target host="api2.getresponse.com"/>
	<target host="app.getresponse.com"/>
	<target host="cdn.getresponse.com"/>
	<target host="multimedia.getresponse.com"/>
	<target host="secure.getresponse.com"/>
	<target host="static.getresponse.com"/>
	<target host="support.getresponse.com"/>
	<target host="support-panel.getresponse.com"/>
	<target host="www.getresponse.com"/>
		<!--exclusion pattern="^http://(apidocs|blog|br|connect|dev)\.getresponse\.com/" /-->
		<!--
			Avoid false/broken MCB:
						-->
		<exclusion pattern="^http://support\.getresponse\.com/+(?!uploads/|wp-content/|wp-includes/)"/>


	<rule from="^http:" to="https:"/>

</ruleset>

GetResponse.com.xml    File a bug

The release branch contains the following rules that are enabled by default:

<!--
	Problematic subdomains:

		- apidocs *
		- blog *
		- br *
		- connect *
		- dev *

	* Works, mismatched


	Partially covered subdomains:

		- support *

	* Avoiding false/broken MCB


	Fully covered subdomains:

		- (www.)
		- api
		- api2
		- app
		- cdn
		- multimedia
		- secure
		- static
		- support-panel


	Mixed content:

		- css, on:

			- apidocs from $self ¹
			- blog from $self ¹
			- connect from $self ¹
			- support from $self ²

		- Images, on:

			- apidocs from $self ¹
			- blog from $self ¹
			- support from $self ²

		- favicon, on:

			- blog from $self ¹
			- support from $self ²

	¹ Not secured by us <= mismatched
	² Secured by us

--><ruleset name="GetResponse.com (partial)">

	<target host="getresponse.com"/>
	<target host="api.getresponse.com"/>
	<target host="api2.getresponse.com"/>
	<target host="app.getresponse.com"/>
	<target host="cdn.getresponse.com"/>
	<target host="multimedia.getresponse.com"/>
	<target host="secure.getresponse.com"/>
	<target host="static.getresponse.com"/>
	<target host="support.getresponse.com"/>
	<target host="support-panel.getresponse.com"/>
	<target host="www.getresponse.com"/>
		<!--exclusion pattern="^http://(apidocs|blog|br|connect|dev)\.getresponse\.com/" /-->
		<!--
			Avoid false/broken MCB:
						-->
		<exclusion pattern="^http://support\.getresponse\.com/+(?!uploads/|wp-content/|wp-includes/)"/>


	<rule from="^http:" to="https:"/>

</ruleset>

GetResponse.com.xml    File a bug

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 ff5b4642 2019-06-27 14:21:20 -0700;
next release e6015813 2019-08-24 17:03:46 +0800;