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):

<!--
	Nonfunctional subdomains:

		- international *

	* Redirects to http, tls unsupported by redirect destination


	Partially covered subdomains:

		- allievi ¹
		- forms ²
		- www ³

	¹ Avoiding mixed css on techblog/
	² Accounting for possible excluded paths wrt redirect
	³ Some pages redirect to http


	Fully covered subdomains:

		- didactive
		- pay


	Observed cookie domains:

		- allievi ¹
		- didactive ²
		- forms ¹
		- pay ²
		- www ³

	¹ Not secured by us <= accounting for possible use on excluded paths
	² Secured by us <= not secured by server & coverage complete
	³ Not secured by us <= incomplete tls support


	Mixed content:

		- css on allievi from $self *

		- Images on allievi from $self *

	* Secured by us

--><ruleset name="SSSup.it (partial)" default_off="needs ruleset tests">
	<target host="www.sssup.it"/>
	<target host="didactive.sssup.it"/>
	<target host="allievi.sssup.it"/>
	<target host="forms.sssup.it"/>
	<target host="pay.sssup.it"/>
		<!--
			Avoid false/broken MCB:
						-->
		<exclusion pattern="^http://allievi\.sssup\.it/+techblog(?!/wp-content/|wp-includes/)"/>
		<!--
			No known matches, just being cautious:
								-->
		<exclusion pattern="^http://forms\.sssup\.it/+(?!$|\?|didactive(?:$|[?/]))"/>
		<!--
			Redirect to http:
						-->
		<!--exclusion pattern="^http://www\.sssup\.it/+($|\?|context\.jsp|context_elenco\.jsp|default\.jsp)" /-->
		<!--
			Exceptions:
					-->
		<exclusion pattern="^http://www\.sssup\.it/+(?!(?:ammissione|ammissione-dottorati-perfezionamento|ateneo|concorso-ammissione|master|orientamento|ufficiostampa)(?:$|[?/])|customcss/|favicon\.ico|images/|images_new/|intranet_logon\.jsp|isipcss/|mappa\.jsp|search\.jsp|UploadDocs/|UploadImgs/)"/>


	<!--	Not secured by server:
					-->
	<securecookie host="^(?:didactive|pay)\.sssup\.it$" name=".+"/>

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

SSSup.it.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):

<!--
	Nonfunctional subdomains:

		- international *

	* Redirects to http, tls unsupported by redirect destination


	Partially covered subdomains:

		- allievi ¹
		- forms ²
		- www ³

	¹ Avoiding mixed css on techblog/
	² Accounting for possible excluded paths wrt redirect
	³ Some pages redirect to http


	Fully covered subdomains:

		- didactive
		- pay


	Observed cookie domains:

		- allievi ¹
		- didactive ²
		- forms ¹
		- pay ²
		- www ³

	¹ Not secured by us <= accounting for possible use on excluded paths
	² Secured by us <= not secured by server & coverage complete
	³ Not secured by us <= incomplete tls support


	Mixed content:

		- css on allievi from $self *

		- Images on allievi from $self *

	* Secured by us

--><ruleset name="SSSup.it (partial)" default_off="needs ruleset tests">
	<target host="www.sssup.it"/>
	<target host="didactive.sssup.it"/>
	<target host="allievi.sssup.it"/>
	<target host="forms.sssup.it"/>
	<target host="pay.sssup.it"/>
		<!--
			Avoid false/broken MCB:
						-->
		<exclusion pattern="^http://allievi\.sssup\.it/+techblog(?!/wp-content/|wp-includes/)"/>
		<!--
			No known matches, just being cautious:
								-->
		<exclusion pattern="^http://forms\.sssup\.it/+(?!$|\?|didactive(?:$|[?/]))"/>
		<!--
			Redirect to http:
						-->
		<!--exclusion pattern="^http://www\.sssup\.it/+($|\?|context\.jsp|context_elenco\.jsp|default\.jsp)" /-->
		<!--
			Exceptions:
					-->
		<exclusion pattern="^http://www\.sssup\.it/+(?!(?:ammissione|ammissione-dottorati-perfezionamento|ateneo|concorso-ammissione|master|orientamento|ufficiostampa)(?:$|[?/])|customcss/|favicon\.ico|images/|images_new/|intranet_logon\.jsp|isipcss/|mappa\.jsp|search\.jsp|UploadDocs/|UploadImgs/)"/>


	<!--	Not secured by server:
					-->
	<securecookie host="^(?:didactive|pay)\.sssup\.it$" 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 a9c79875 2019-11-07 15:00:59 -0800;
next release 789d49da 2019-12-07 04:22:17 +0000;