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 disabled by default (so very few users' browsing is likely to be affected by their action):

<!--
Disabled by https-everywhere-checker because:
Fetch error: http://rollcall.com/ => https://secure.rollcall.com/: (6, 'Could not resolve host: secure.rollcall.com')

	For other Economist Group coverage, see Economist.com.xml


	CDN buckets:

		- g1.panthercdn.com

			- cdn


	Nonfunctional subdomains:

		- atr *
		- blogs *
		- boeing *

	* Refused


	Problematic subdomains:

		- (www.)	(works; mismatched, CN: *.iproduction.com)
		- cdn		(403; mismatched, CN: support2.cdnetworks.net)


	Fully covered subdomains:

		- (www.)	(→ secure)
		- cdn		(→ secure)
		- secure


	Mixed content:

		- Script on secure from cdn *
		- css on secure from cdn *
		- Images on secure from cdn *

	* Secured by us.


	NB: We secure all resources, and thus
	platform should be removed with Ffx 24.

--><ruleset name="Roll Call.com (partial)" platform="mixedcontent" default_off="failed ruleset test">

	<target host="rollcall.com"/>
	<target host="cdn.rollcall.com"/>
	<target host="secure.rollcall.com"/>
	<target host="www.rollcall.com"/>


	<securecookie host="^(?:\.?secure)?\.rollcall\.com$" name=".+"/>


	<rule from="^http://(?:(?:cdn|secure|www)\.)?rollcall\.com/" to="https://secure.rollcall.com/"/>

</ruleset>

Roll_Call.com.xml    File a bug

The release branch contains the following rules that are disabled by default (so very few users' browsing is likely to be affected by their action):

<!--
Disabled by https-everywhere-checker because:
Fetch error: http://rollcall.com/ => https://secure.rollcall.com/: (6, 'Could not resolve host: secure.rollcall.com')

	For other Economist Group coverage, see Economist.com.xml


	CDN buckets:

		- g1.panthercdn.com

			- cdn


	Nonfunctional subdomains:

		- atr *
		- blogs *
		- boeing *

	* Refused


	Problematic subdomains:

		- (www.)	(works; mismatched, CN: *.iproduction.com)
		- cdn		(403; mismatched, CN: support2.cdnetworks.net)


	Fully covered subdomains:

		- (www.)	(→ secure)
		- cdn		(→ secure)
		- secure


	Mixed content:

		- Script on secure from cdn *
		- css on secure from cdn *
		- Images on secure from cdn *

	* Secured by us.


	NB: We secure all resources, and thus
	platform should be removed with Ffx 24.

--><ruleset name="Roll Call.com (partial)" platform="mixedcontent" default_off="failed ruleset test">

	<target host="rollcall.com"/>
	<target host="cdn.rollcall.com"/>
	<target host="secure.rollcall.com"/>
	<target host="www.rollcall.com"/>


	<securecookie host="^(?:\.?secure)?\.rollcall\.com$" name=".+"/>


	<rule from="^http://(?:(?:cdn|secure|www)\.)?rollcall\.com/" to="https://secure.rollcall.com/"/>

</ruleset>

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 ff5b4642b 2019-06-27 14:21:20 -0700;
next release c0a0e49cd 2019-10-16 02:46:21 +0300;