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 problematic rules, see Web.com-expired.xml.


	CDN buckets:

		- wpc.016b.edgecastcdn.net/00016B/


	Other Web.com rulesets:

		- Cactus_Complete_Commerce.xml
		- LogoYes.xml
		- Mcssl.com.xml
		- Myregisteredsite.com.xml
		- Renovation_Experts.xml
		- Securepurchaseserver.com.xml
		- Solid_Cactus.xml
		- Star_Product_Reviews.xml


	ne.edgecastcdn.net/00016B/
	ne1.wpc.edgecastcdn.net/00016B/


	Nonfunctional subdomains:

		- ir	(times out)


	^: cert only matches www


	Mixed content:

		- css on www.web.com from wpc.016b.edgecastcdn.net ¹

		- Bugs, on:

			- www.web.com from fls.doubleclick.net ²
			- www.web.com from pixel.fetchback.com ³

	¹ Secured by us, causes slight alignment difference
	² Rule disabled by default
	³ Secured by us

--><ruleset name="Web.com (partial)">

	<target host="wpc.016b.edgecastcdn.net"/>
	<target host="web.com"/>
	<target host="www.web.com"/>
	<target host="support.web.com"/>
	<target host="webmail.web.com"/>


	<!--	Secured by server:
					-->
	<!--securecookie host="^secure2\.web\.com$" name="^(ASP\.NET_SessionId|pname)$" /-->
	<!--
		Not secured by server:
					-->
	<!--securecookie host="^(support)?\.web\.com$" name="^(affdata|inurl)$" /-->
	<!--securecookie host="^((support|www)\.)?web\.com$" name="^ASP\.NET_SessionId$" /-->

	<securecookie host="^(?:.*\.)?web\.com$" name=".+"/>


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

	<rule from="^http://(support|webmail)\.web\.com/" to="https://$1.web.com/"/>

	<rule from="^http://wpc\.016b\.edgecastcdn\.net/00016B/" to="https://ne1.wpc.edgecastcdn.net/00016B/"/>

</ruleset>

Web.com.xml    File a bug

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

<!--
	For problematic rules, see Web.com-expired.xml.


	CDN buckets:

		- wpc.016b.edgecastcdn.net/00016B/


	Other Web.com rulesets:

		- Cactus_Complete_Commerce.xml
		- LogoYes.xml
		- Mcssl.com.xml
		- Myregisteredsite.com.xml
		- Renovation_Experts.xml
		- Securepurchaseserver.com.xml
		- Solid_Cactus.xml
		- Star_Product_Reviews.xml


	ne.edgecastcdn.net/00016B/
	ne1.wpc.edgecastcdn.net/00016B/


	Nonfunctional subdomains:

		- ir	(times out)


	^: cert only matches www


	Mixed content:

		- css on www.web.com from wpc.016b.edgecastcdn.net ¹

		- Bugs, on:

			- www.web.com from fls.doubleclick.net ²
			- www.web.com from pixel.fetchback.com ³

	¹ Secured by us, causes slight alignment difference
	² Rule disabled by default
	³ Secured by us

--><ruleset name="Web.com (partial)">

	<target host="wpc.016b.edgecastcdn.net"/>
	<target host="web.com"/>
	<target host="www.web.com"/>
	<target host="support.web.com"/>
	<target host="webmail.web.com"/>


	<!--	Secured by server:
					-->
	<!--securecookie host="^secure2\.web\.com$" name="^(ASP\.NET_SessionId|pname)$" /-->
	<!--
		Not secured by server:
					-->
	<!--securecookie host="^(support)?\.web\.com$" name="^(affdata|inurl)$" /-->
	<!--securecookie host="^((support|www)\.)?web\.com$" name="^ASP\.NET_SessionId$" /-->

	<securecookie host="^(?:.*\.)?web\.com$" name=".+"/>


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

	<rule from="^http://(support|webmail)\.web\.com/" to="https://$1.web.com/"/>

	<rule from="^http://wpc\.016b\.edgecastcdn\.net/00016B/" to="https://ne1.wpc.edgecastcdn.net/00016B/"/>

</ruleset>

Web.com.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 a9c79875 2019-11-07 15:00:59 -0800;
next release 2b601674 2019-12-08 04:22:03 +0000;