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:

<!--
	Connection closed:
		fbia

	Invalid certificate:
		extsrv01
		hbbtv
		imf
		imf-rest
		liveblog
		newsletter
		olympia
		on
		smashdown
		spiele
		stage
		turniere-games
		base.tv

	Refused:
		ticker

	SSL: no alternative certificate subject name matches target host name:
		tracking

	SSL certificate problem: unable to get local issuer certificate:
		ftp

	Timeout:
		account
		community
		imf-staging
		mail10
--><ruleset name="Sport1.de">

	<target host="sport1.de"/>
	<target host="www.sport1.de"/>
	<target host="amp.sport1.de"/>
	<target host="amp-stage.sport1.de"/>
	<target host="api.sport1.de"/>
	<target host="api-stage.sport1.de"/>
	<target host="assets.sport1.de"/>
	<target host="behave.sport1.de"/>
	<target host="bets.sport1.de"/>
	<target host="bets-staging.sport1.de"/>
	<target host="business.sport1.de"/>
	<target host="cmsdata.sport1.de"/>
	<target host="cmsdata-staging.sport1.de"/>
	<target host="darts.sport1.de"/>
	<target host="docs.sport1.de"/>
	<target host="esports-shop.sport1.de"/>
	<target host="ezadmin.sport1.de"/>
	<target host="games.sport1.de"/>
	<target host="go.sport1.de"/>
	<target host="icc.sport1.de"/>
	<target host="images.sport1.de"/>
	<target host="insights.sport1.de"/>
	<target host="jump.sport1.de"/>
	<target host="m.sport1.de"/>
	<target host="newsletter-abmeldung.sport1.de"/>
	<target host="newsletter-anmeldung.sport1.de"/>
	<target host="newsletter-profil.sport1.de"/>
	<target host="oz.sport1.de"/>
	<target host="pmds.sport1.de"/>
	<target host="react.sport1.de"/>
	<target host="react-stage.sport1.de"/>
	<target host="reshape.sport1.de"/>
	<target host="shop.sport1.de"/>
	<target host="sportsapi.sport1.de"/>
	<target host="sportshtml.sport1.de"/>
	<target host="sportshtmlblank.sport1.de"/>
	<target host="www.stage.sport1.de"/>
	<target host="ezadmin.stage.sport1.de"/>
	<target host="m.stage.sport1.de"/>
	<target host="stage-oz.sport1.de"/>
	<target host="stage-reshape.sport1.de"/>
	<target host="stage-tv.sport1.de"/>
	<target host="status.sport1.de"/>
	<target host="streaming-event01.sport1.de"/>
	<target host="streaming-event02.sport1.de"/>
	<target host="streaming-ext1.sport1.de"/>
	<target host="streaming-ext2.sport1.de"/>
	<target host="streaming-ext3.sport1.de"/>
	<target host="streaming-s1free.sport1.de"/>
	<target host="streaming-s1plus.sport1.de"/>
	<target host="tv.sport1.de"/>
	<target host="video.sport1.de"/>
	<target host="vod.sport1.de"/>
	<target host="vod-dach.sport1.de"/>
	<target host="vod-int.sport1.de"/>
	<target host="vod-int-bu.sport1.de"/>
	<target host="vod-onefootball.sport1.de"/>
	<target host="widgets.sport1.de"/>
	<target host="widgets-stage.sport1.de"/>

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

</ruleset>

Sport1.de.xml    File a bug

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

<!--
	Connection closed:
		fbia

	Invalid certificate:
		extsrv01
		hbbtv
		imf
		imf-rest
		liveblog
		newsletter
		olympia
		on
		smashdown
		spiele
		stage
		turniere-games
		base.tv

	Refused:
		ticker

	SSL: no alternative certificate subject name matches target host name:
		tracking

	SSL certificate problem: unable to get local issuer certificate:
		ftp

	Timeout:
		account
		community
		imf-staging
		mail10
--><ruleset name="Sport1.de">

	<target host="sport1.de"/>
	<target host="www.sport1.de"/>
	<target host="amp.sport1.de"/>
	<target host="amp-stage.sport1.de"/>
	<target host="api.sport1.de"/>
	<target host="api-stage.sport1.de"/>
	<target host="assets.sport1.de"/>
	<target host="behave.sport1.de"/>
	<target host="bets.sport1.de"/>
	<target host="bets-staging.sport1.de"/>
	<target host="business.sport1.de"/>
	<target host="cmsdata.sport1.de"/>
	<target host="cmsdata-staging.sport1.de"/>
	<target host="darts.sport1.de"/>
	<target host="docs.sport1.de"/>
	<target host="esports-shop.sport1.de"/>
	<target host="ezadmin.sport1.de"/>
	<target host="games.sport1.de"/>
	<target host="go.sport1.de"/>
	<target host="icc.sport1.de"/>
	<target host="images.sport1.de"/>
	<target host="insights.sport1.de"/>
	<target host="jump.sport1.de"/>
	<target host="m.sport1.de"/>
	<target host="newsletter-abmeldung.sport1.de"/>
	<target host="newsletter-anmeldung.sport1.de"/>
	<target host="newsletter-profil.sport1.de"/>
	<target host="oz.sport1.de"/>
	<target host="pmds.sport1.de"/>
	<target host="react.sport1.de"/>
	<target host="react-stage.sport1.de"/>
	<target host="reshape.sport1.de"/>
	<target host="shop.sport1.de"/>
	<target host="sportsapi.sport1.de"/>
	<target host="sportshtml.sport1.de"/>
	<target host="sportshtmlblank.sport1.de"/>
	<target host="www.stage.sport1.de"/>
	<target host="ezadmin.stage.sport1.de"/>
	<target host="m.stage.sport1.de"/>
	<target host="stage-oz.sport1.de"/>
	<target host="stage-reshape.sport1.de"/>
	<target host="stage-tv.sport1.de"/>
	<target host="status.sport1.de"/>
	<target host="streaming-event01.sport1.de"/>
	<target host="streaming-event02.sport1.de"/>
	<target host="streaming-ext1.sport1.de"/>
	<target host="streaming-ext2.sport1.de"/>
	<target host="streaming-ext3.sport1.de"/>
	<target host="streaming-s1free.sport1.de"/>
	<target host="streaming-s1plus.sport1.de"/>
	<target host="tv.sport1.de"/>
	<target host="video.sport1.de"/>
	<target host="vod.sport1.de"/>
	<target host="vod-dach.sport1.de"/>
	<target host="vod-int.sport1.de"/>
	<target host="vod-int-bu.sport1.de"/>
	<target host="vod-onefootball.sport1.de"/>
	<target host="widgets.sport1.de"/>
	<target host="widgets-stage.sport1.de"/>

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

</ruleset>

Sport1.de.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 79252541 2021-07-13 13:19:11 -0700;
next release 17d61a00 2022-05-25 04:06:39 +0000;