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:

<!--
	For University of South Florida Saint Petersburg see USFSP.edu.xml

	Mismatched:
		- directory.acomp
		- it
		- system

	Refused:
		- news

	Timeout:
		- tap

	Incomplete certificate chain:
		- lib

	SSL configuration error:
		- usfweb2 (see https://www.ssllabs.com/ssltest/analyze.html?d=usfweb2.usf.edu)
--><ruleset name="University of South Florida (partial)">
	<target host="usf.edu"/>
	<target host="www.usf.edu"/>
	<target host="it.usf.edu"/>
	<target host="lib.usf.edu"/>
	<target host="www.lib.usf.edu"/>
	<target host="guides.lib.usf.edu"/>
	<target host="my.usf.edu"/>
	<target host="mysites.usf.edu"/>
	<target host="netid.usf.edu"/>
	<target host="news.usf.edu"/>
	<target host="research.usf.edu"/>
	<target host="www.research.usf.edu"/>
	<target host="system.usf.edu"/>
	<target host="webauth.usf.edu"/>

	<!-- .* removes the path to match website's own 301 redirect -->
	<rule from="^http://(it|news|system)\.usf\.edu/.*" to="https://www.usf.edu/$1"/>
	<test url="http://it.usf.edu/abcdef"/>
	<test url="http://news.usf.edu/abcdef"/>
	<test url="http://system.usf.edu/abcdef"/>

	<rule from="^http://lib\.usf\.edu/" to="https://www.lib.usf.edu/"/>

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

University-of-South-Florida.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://usfsp.edu/ => https://usfsp.edu/: (51, "SSL: no alternative certificate subject name matches target host name 'usfsp.edu'")

Disabled by https-everywhere-checker because:
Fetch error: http://usfsp.edu/ => https://usfsp.edu/: (51, "SSL: no alternative certificate subject name matches target host name 'usfsp.edu'")
	For problematic rules, see University-of-South-Florida-mismatches.xml.


	Nonfunctional usf.edu subdomains:

		- (www.)		(times out)
		- directory.acomp	(cert: netid.usf.edu; redirects there)
		- it			(expired, self-signed; 301s to rc.blog.usf.edu/domain-not-found/)
		- guides.lib		(cert: libguides.com; 404)
		- (www.)nelson
		- news
		- (www.)research
		- system
		- tap			(expired, self-signed; 301s to rc.blog.usf.edu/domain-not-found/)

--><ruleset name="University of South Florida (partial)" default_off="failed ruleset test">

	<target host="lib.usf.edu"/>
	<target host="www.lib.usf.edu"/>
	<target host="my.usf.edu"/>
	<target host="mysites.usf.edu"/>
	<target host="netid.usf.edu"/>
	<target host="usfsts.usf.edu"/>
	<target host="usfweb2.usf.edu"/>
	<target host="webauth.usf.edu"/>
	<target host="stpete.usf.edu"/>
	<target host="www.stpete.usf.edu"/>
	<target host="sharemypc.stpete.usf.edu"/>
	<target host="usfsp.edu"/>
	<target host="dev.usfsp.edu"/>
	<target host="vpn.usfsp.edu"/>
	<target host="www.usfsp.edu"/>
	<target host="sharemypc.usfsp.edu"/>


	<!--	Not handling cross-domain cookies as a precaution.	-->
	<securecookie host="^(?:\w.*\.)?usf(?:sp)?\.edu$" name=".+"/>


	<!--	Cert only matches www.lib.
						-->
	<rule from="^http://(?:www\.)?lib\.usf\.edu/" to="https://www.lib.usf.edu/"/>


	<!--	- Cert doesn't match
		- Redirects like so
				-->
	<rule from="^http://(?:www\.)?stpete\.usf\.edu/" to="https://www.usfsp.edu/"/>


	<!--	- Cert only matches sharemypc.stpete.usf
		- Data appear identical
				-->
	<rule from="^http://sharemypc\.(?:stpete\.usf|usfsp)\.edu/" to="https://sharemypc.stpete.usf.edu/"/>

	<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 9f4cdb0a 2019-09-17 05:08:33 +0200;