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://sso.calacademy.org/ => https://sso.calacademy.org/: (35, 'Unknown SSL protocol error in connection to sso.calacademy.org:443 ')

	Nonfunctional hosts in *.calacademy.org:

	Incomplete certificate chain:

		calacademy.org
		www.calacademy.org

	Invalid certificate:

		calendar.calacademy.org
		hotels.calacademy.org
		libcat.calacademy.org
		pages.calacademy.org
		research.calacademy.org
		sacportal.calacademy.org
		m.stg.calacademy.org

	Timeout:

		archdrop.calacademy.org
		casp.calacademy.org
		chat.calacademy.org
		collections.calacademy.org
		ipt.calacademy.org
		myexplorer.calacademy.org
		phylocluster.calacademy.org
		researcharchive.calacademy.org
		sengis.calacademy.org
		www-dr.calacademy.org
		zeus.calacademy.org

	PROTOCOL_ERROR:

		multisite.calacademy.org

  Redirect to http:

		legacy.calacademy.org

	h: http redirect
	m: certificate mismatch
	r: connection refused
	s: self-signed certificate
	t: timeout on https
--><ruleset name="Calacademy.org" default_off="failed ruleset test">
	<target host="apps.calacademy.org"/>
	<target host="archivesadmin.calacademy.org"/>
	<target host="jira.calacademy.org"/>
	<target host="kronos.calacademy.org"/>
	<target host="monarch.calacademy.org"/>
	<target host="sso.calacademy.org"/>
	<target host="store.calacademy.org"/>
	<target host="ticketing.calacademy.org"/>
	<target host="vpn.calacademy.org"/>

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

Calacademy.org.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://sso.calacademy.org/ => https://sso.calacademy.org/: (35, 'Unknown SSL protocol error in connection to sso.calacademy.org:443 ')

	Nonfunctional hosts in *.calacademy.org:

	Incomplete certificate chain:

		calacademy.org
		www.calacademy.org

	Invalid certificate:

		calendar.calacademy.org
		hotels.calacademy.org
		libcat.calacademy.org
		pages.calacademy.org
		research.calacademy.org
		sacportal.calacademy.org
		m.stg.calacademy.org

	Timeout:

		archdrop.calacademy.org
		casp.calacademy.org
		chat.calacademy.org
		collections.calacademy.org
		ipt.calacademy.org
		myexplorer.calacademy.org
		phylocluster.calacademy.org
		researcharchive.calacademy.org
		sengis.calacademy.org
		www-dr.calacademy.org
		zeus.calacademy.org

	PROTOCOL_ERROR:

		multisite.calacademy.org

  Redirect to http:

		legacy.calacademy.org

	h: http redirect
	m: certificate mismatch
	r: connection refused
	s: self-signed certificate
	t: timeout on https
--><ruleset name="Calacademy.org" default_off="failed ruleset test">
	<target host="apps.calacademy.org"/>
	<target host="archivesadmin.calacademy.org"/>
	<target host="jira.calacademy.org"/>
	<target host="kronos.calacademy.org"/>
	<target host="monarch.calacademy.org"/>
	<target host="sso.calacademy.org"/>
	<target host="store.calacademy.org"/>
	<target host="ticketing.calacademy.org"/>
	<target host="vpn.calacademy.org"/>

	<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 737bcdfc 2019-08-09 18:08:25 +0300;