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://www.lavabit.com/ => https://www.lavabit.com/: (51, "SSL: no alternative certificate subject name matches target host name 'www.lavabit.com'")

chain issues:

	linux1.hosting.lavabit.com
	linux2.hosting.lavabit.com
	mail.hosting.lavabit.com
	mysql.hosting.lavabit.com
	pgsql.hosting.lavabit.com
	stats.hosting.lavabit.com
	windows2.hosting.lavabit.com
	www.hosting.lavabit.com
	144-72.249.41.lavabit.com
	165-72.249.41.lavabit.com

cert mismatch:
	ashlee.lavabit.com
	osheana.virtual.lavabit.com

(still) expired:
	hosting.lavabit.com
	windows1.hosting.lavabit.com

no response:
	alexis.lavabit.com check
	click.lavabit.com
	liberty.lavabit.com
	alexis.lavabit.com
	vpn.lavabit.com
	hayden.virtual.lavabit.com
	risa.virtual.lavabit.com
	ns1.lavabit.com
	ns2.lavabit.com
	ns3.lavabit.com
	ns4.lavabit.com
	mistress.stacie.lavabit.com
	ns1.hosting.lavabit.com
	ns2.hosting.lavabit.com
	karen.lavabit.com
	lacey.lavabit.com
	mssql.hosting.lavabit.com

can't be resolved:

	www.liberty.lavabit.com
	(www.)admin.lavabit.com

Self-Signed:
	mercurial.stacie.lavabit.com
	rogers.virtual.lavabit.com

Timeout:
	michelle.lavabit.com
	minnie.ashlee.lavabit.com
	gw.lavabit.com
	genny.hosting.lavabit.com
	gina.hosting.lavabit.com
	brooke.virtual.lavabit.com
	butters.virtual.lavabit.com
--><ruleset name="Lavabit" default_off="failed ruleset test">
	<target host="lavabit.com"/>
	<target host="www.lavabit.com"/>
	<target host="dana.ashlee.lavabit.com"/>
	<target host="dana.lavabit.com"/>
	<target host="git.lavabit.com"/>


	<securecookie host=".+" name=".+"/>

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

Lavabit.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://www.lavabit.com/ => https://www.lavabit.com/: (51, "SSL: no alternative certificate subject name matches target host name 'www.lavabit.com'")

chain issues:

	linux1.hosting.lavabit.com
	linux2.hosting.lavabit.com
	mail.hosting.lavabit.com
	mysql.hosting.lavabit.com
	pgsql.hosting.lavabit.com
	stats.hosting.lavabit.com
	windows2.hosting.lavabit.com
	www.hosting.lavabit.com
	144-72.249.41.lavabit.com
	165-72.249.41.lavabit.com

cert mismatch:
	ashlee.lavabit.com
	osheana.virtual.lavabit.com

(still) expired:
	hosting.lavabit.com
	windows1.hosting.lavabit.com

no response:
	alexis.lavabit.com check
	click.lavabit.com
	liberty.lavabit.com
	alexis.lavabit.com
	vpn.lavabit.com
	hayden.virtual.lavabit.com
	risa.virtual.lavabit.com
	ns1.lavabit.com
	ns2.lavabit.com
	ns3.lavabit.com
	ns4.lavabit.com
	mistress.stacie.lavabit.com
	ns1.hosting.lavabit.com
	ns2.hosting.lavabit.com
	karen.lavabit.com
	lacey.lavabit.com
	mssql.hosting.lavabit.com

can't be resolved:

	www.liberty.lavabit.com
	(www.)admin.lavabit.com

Self-Signed:
	mercurial.stacie.lavabit.com
	rogers.virtual.lavabit.com

Timeout:
	michelle.lavabit.com
	minnie.ashlee.lavabit.com
	gw.lavabit.com
	genny.hosting.lavabit.com
	gina.hosting.lavabit.com
	brooke.virtual.lavabit.com
	butters.virtual.lavabit.com
--><ruleset name="Lavabit" default_off="failed ruleset test">
	<target host="lavabit.com"/>
	<target host="www.lavabit.com"/>
	<target host="dana.ashlee.lavabit.com"/>
	<target host="dana.lavabit.com"/>
	<target host="git.lavabit.com"/>


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