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 rules causing false/broken MCB, see T-Mobile.com-falsemixed.xml.

	For other Deutsche Telekom coverage, see Deutsche_Telekom.xml.


	Note that some services linked from the home page will be HTTP.
	Trying to force these to HTTPS currently (2010-05) seems to produce
	certificate errors.


	CDN buckets:

		- wac.04c7.edgecastcdn.net/0004C7/


	Nonfunctional hosts in *t-mobile.com:

		- explore.business ¹
		- cache.deals ¹
		- htc ³
		- cache.htc ³
		- investor ⁴
		- locator ⁵
		- cache.newsroom ¹
		- sdc ⁴
		- t-mobile-coverage ⁶

	¹ Handshake fails
	¹ 404, CN: gp1.wac.edgecastcdn.net
	³ Revoked cert
	⁴ Dropped
	⁵ 404
	⁶ Shows another domain


	Problematic hosts in *t-mobile.com:

		- b2b ⁷
		- cache.business ¹
		- es.explore.business ²
		- images.businessresources ³
		- cache.explore	 ¹
		- find ⁴
		- cache.prepaid-phones ¹
		- videos ⁵
		- cache.videos ⁶
		- es.videos ⁵

	¹ Expired
	² TLS unsupported at redirect destination
	³ Akamai
	⁴ Works, mismatched, CN: find.my.t-mobile.com. Functionally
	   equivalent to the latter, but visually different.
	⁵ Mixed css
	⁶ Mismatched, CN: gp1.wac.edgecastcdn.net
	⁷ Incomplete certificate chain


	Insecure cookies are set for these domains and hosts:

		- .t-mobile.com
		- account.t-mobile.com
		- es.account.t-mobile.com
		- .ebill.t-mobile.com
		- explore.t-mobile.com
		- es.explore.t-mobile.com
		- my.t-mobile.com
		- .my.t-mobile.com
		- account.my.t-mobile.com
		- es.my.t-mobile.com
		- m.my.t-mobile.com
		- newsroom.t-mobile.com
		- es.support.t-mobile.com
		- videos.t-mobile.com
		- es.videos.t-mobile.com


	Mixed content:

		- css, on:

			- videos from www.t-mobile.com *
			- es.videos from es.t-mobile.com *

		- Images, on:

			- find.es from www.t-mobile.com *
			- find.es from s.tmocache.com *

		- favicon on es.videos from www.t-mobile.com *

	* Secured by us

--><ruleset name="T-Mobile.com (partial)">
	<target host="t-mobile.com"/>
	<target host="www.t-mobile.com"/>
	<target host="account.t-mobile.com"/>
	<target host="es.account.t-mobile.com"/>
	<target host="business.t-mobile.com"/>
	<target host="es.business.t-mobile.com"/>
	<target host="find.business.t-mobile.com"/>
	<target host="ebill.t-mobile.com"/>
	<target host="es.t-mobile.com"/>
	<target host="find.es.t-mobile.com"/>
	<target host="explore.t-mobile.com"/>
	<target host="es.explore.t-mobile.com"/>
	<target host="my.t-mobile.com"/>
	<target host="account.my.t-mobile.com"/>
	<target host="es.account.my.t-mobile.com"/>
	<target host="es.my.t-mobile.com"/>
	<target host="m.my.t-mobile.com"/>
	<target host="manage.my.t-mobile.com"/>
	<target host="es.manage.my.t-mobile.com"/>
	<target host="newsroom.t-mobile.com"/>
	<target host="prepaid-phones.t-mobile.com"/>
	<target host="es.prepaid-phones.t-mobile.com"/>
	<target host="secure-checkout.t-mobile.com"/>
	<target host="support.t-mobile.com"/>
	<target host="apps.support.t-mobile.com"/>
	<target host="es.support.t-mobile.com"/>
	<target host="vip.t-mobile.com"/>
	<!--target host="videos.t-mobile.com" /-->
	<!--target host="es.videos.t-mobile.com" /-->
	<!--target host="cache.videos.t-mobile.com" /-->

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

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

T-Mobile.xml    File a bug

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

<!--

	For rules causing false/broken MCB, see T-Mobile.com-falsemixed.xml.

	For other Deutsche Telekom coverage, see Deutsche_Telekom.xml.


	Note that some services linked from the home page will be HTTP.
	Trying to force these to HTTPS currently (2010-05) seems to produce
	certificate errors.


	CDN buckets:

		- wac.04c7.edgecastcdn.net/0004C7/


	Nonfunctional hosts in *t-mobile.com:

		- explore.business ¹
		- cache.deals ¹
		- htc ³
		- cache.htc ³
		- investor ⁴
		- locator ⁵
		- cache.newsroom ¹
		- sdc ⁴
		- t-mobile-coverage ⁶

	¹ Handshake fails
	¹ 404, CN: gp1.wac.edgecastcdn.net
	³ Revoked cert
	⁴ Dropped
	⁵ 404
	⁶ Shows another domain


	Problematic hosts in *t-mobile.com:

		- b2b ⁷
		- cache.business ¹
		- es.explore.business ²
		- images.businessresources ³
		- cache.explore	 ¹
		- find ⁴
		- cache.prepaid-phones ¹
		- videos ⁵
		- cache.videos ⁶
		- es.videos ⁵

	¹ Expired
	² TLS unsupported at redirect destination
	³ Akamai
	⁴ Works, mismatched, CN: find.my.t-mobile.com. Functionally
	   equivalent to the latter, but visually different.
	⁵ Mixed css
	⁶ Mismatched, CN: gp1.wac.edgecastcdn.net
	⁷ Incomplete certificate chain


	Insecure cookies are set for these domains and hosts:

		- .t-mobile.com
		- account.t-mobile.com
		- es.account.t-mobile.com
		- .ebill.t-mobile.com
		- explore.t-mobile.com
		- es.explore.t-mobile.com
		- my.t-mobile.com
		- .my.t-mobile.com
		- account.my.t-mobile.com
		- es.my.t-mobile.com
		- m.my.t-mobile.com
		- newsroom.t-mobile.com
		- es.support.t-mobile.com
		- videos.t-mobile.com
		- es.videos.t-mobile.com


	Mixed content:

		- css, on:

			- videos from www.t-mobile.com *
			- es.videos from es.t-mobile.com *

		- Images, on:

			- find.es from www.t-mobile.com *
			- find.es from s.tmocache.com *

		- favicon on es.videos from www.t-mobile.com *

	* Secured by us

--><ruleset name="T-Mobile.com (partial)">
	<target host="t-mobile.com"/>
	<target host="www.t-mobile.com"/>
	<target host="account.t-mobile.com"/>
	<target host="es.account.t-mobile.com"/>
	<target host="business.t-mobile.com"/>
	<target host="es.business.t-mobile.com"/>
	<target host="find.business.t-mobile.com"/>
	<target host="ebill.t-mobile.com"/>
	<target host="es.t-mobile.com"/>
	<target host="find.es.t-mobile.com"/>
	<target host="explore.t-mobile.com"/>
	<target host="es.explore.t-mobile.com"/>
	<target host="my.t-mobile.com"/>
	<target host="account.my.t-mobile.com"/>
	<target host="es.account.my.t-mobile.com"/>
	<target host="es.my.t-mobile.com"/>
	<target host="m.my.t-mobile.com"/>
	<target host="manage.my.t-mobile.com"/>
	<target host="es.manage.my.t-mobile.com"/>
	<target host="newsroom.t-mobile.com"/>
	<target host="prepaid-phones.t-mobile.com"/>
	<target host="es.prepaid-phones.t-mobile.com"/>
	<target host="secure-checkout.t-mobile.com"/>
	<target host="support.t-mobile.com"/>
	<target host="apps.support.t-mobile.com"/>
	<target host="es.support.t-mobile.com"/>
	<target host="vip.t-mobile.com"/>
	<!--target host="videos.t-mobile.com" /-->
	<!--target host="es.videos.t-mobile.com" /-->
	<!--target host="cache.videos.t-mobile.com" /-->

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

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

T-Mobile.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 ff5b4642b 2019-06-27 14:21:20 -0700;
next release c0a0e49cd 2019-10-16 02:46:21 +0300;