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 release branch contains the following rules that are enabled by default:

	Trinidad Guardian

	Nonfunctional subdomains:

		- adserver *
		- subscriptions *

	* Refused

	Fully covered subdomains:

		- (www.)

	Mixed content:

		- Script on www from www *
		- Images on www from www *

		- css, on www from:

			- www *
			- *

		- Ads/web bugs, on www from:

			- adserver **
			- *
			- *
			- *
			- *
			- *
			- **
			- **

	* Secured by us
	** Unsecurable, but who cares

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

--><ruleset name=" (false MCB)" platform="mixedcontent">

	<target host=""/>
	<target host=""/>

	<!--securecookie host="^\.guardian\.co\.tt$" name="^(__cfduid|__utm\w)$" /-->
	<securecookie host="^(?:www)?\.guardian\.co\.tt$" name=".+"/>

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

</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 2d5e1314 2020-08-13 11:58:12 -0700;
next release 57d23f0f 2020-11-22 19:12:30 -0500;