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:

<ruleset name="Letterboxd.com">
	<target host="letterboxd.com"/>
	<target host="www.letterboxd.com"/>

<!--
	the following subdomains don't support https yet but are listed here for reference
-->

<!-- 	<target host="news.letterboxd.com" /> -->
<!-- 	<target host="embed.letterboxd.com" /> -->
<!-- 	<target host="feedback.letterboxd.com" /> -->

<!--
	there is also ltrbxd.com which appears to be mainly used for a cdn.
	However not all subdomains work correctly with https. For example,
	every file on a.ltrbxd.com is also available on skyfall.a.ltrbxd.com,
	oblivion.a.ltrbxd.com etc. These servers can be accessed with https
	but browsers will display errors/warnings because there is only a
	wildcard certificate for *.ltrbxd.com and not one for each of the subdomains.
-->

	<target host="a.ltrbxd.com"/>
<!-- 	<target host="*.a.ltrbxd.com" /> -->
	<target host="s1.ltrbxd.com"/>
<!-- 	<target host="*.s1.ltrbxd.com" /> -->
	<target host="s2.ltrbxd.com"/>
<!-- 	<target host="*.s2.ltrbxd.com" /> -->


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

Letterboxd.com.xml    File a bug

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

<ruleset name="Letterboxd.com">
	<target host="letterboxd.com"/>
	<target host="www.letterboxd.com"/>

<!--
	the following subdomains don't support https yet but are listed here for reference
-->

<!-- 	<target host="news.letterboxd.com" /> -->
<!-- 	<target host="embed.letterboxd.com" /> -->
<!-- 	<target host="feedback.letterboxd.com" /> -->

<!--
	there is also ltrbxd.com which appears to be mainly used for a cdn.
	However not all subdomains work correctly with https. For example,
	every file on a.ltrbxd.com is also available on skyfall.a.ltrbxd.com,
	oblivion.a.ltrbxd.com etc. These servers can be accessed with https
	but browsers will display errors/warnings because there is only a
	wildcard certificate for *.ltrbxd.com and not one for each of the subdomains.
-->

	<target host="a.ltrbxd.com"/>
<!-- 	<target host="*.a.ltrbxd.com" /> -->
	<target host="s1.ltrbxd.com"/>
<!-- 	<target host="*.s1.ltrbxd.com" /> -->
	<target host="s2.ltrbxd.com"/>
<!-- 	<target host="*.s2.ltrbxd.com" /> -->


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

Letterboxd.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 a9c79875 2019-11-07 15:00:59 -0800;
next release 28fe0feb 2019-12-10 04:21:51 +0000;