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:

<!--
	Other Alcatel-Lucent rulesets:

		- Bell-Labs.com.xml


	CDN buckets:

		- now.eloqua.com.edgesuite.net

			- a578.g.akamai.net
			- conversation-images.alcatel-lucent.com


	Nonfunctional subdomains:

		- enterprise		(refused)
		- www.partnerlocator	(dropped)


	Problematic subdomains:

		- ^		(shows www3; mismatched, CN: alcatel-lucent.com)
		- conversation	(works; mismatched, CN: secure.eloqua.com)
		- conversation-images	(works, akamai)
		- corporatereporting	(mismatched, CN: www.homeretailgroup.com)
		- webform	(works; mismatched, CN: *.us.neolane.net)
		- www1		(data differs, valid cert)
		- www2		("site is unavailable for maintenance purposes"; expired 2006-08-30, invalid, self-signed)
			conversation-images	(→ akamai)


	Partially covered subdomains:

		- developer-enterprise	($ shows blank page)
		- www2			($ → www)


	Fully covered domains:

		- alcatel-lucent.com subdomains:

			- (www.)		(^ → www)
			- applicationpartner
			- businessportal
			- corporatereporting	(→ www3)
			- service.esd
			- market
			- my-home
			- support
			- services.support
			- www2

		- market.lucent.com
		- services.support.lucent.com

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

	<target host="alcatel-lucent.com"/>
	<target host="*.alcatel-lucent.com"/>
		<!--
			These paths show a blank page:

				- $
				- component/comprofiler/registers
				- forum/index
									-->
		<!--exclusion pattern="^http://developer-enterprise.alcatel-lucent.com/($|\?|component/comprofiler/|forum/index)" /-->
		<exclusion pattern="^http://developer-enterprise.alcatel-lucent.com/(?!api_content(?:$|[?/])|components/|images/|libraries/|media/|modules/|plugins/|templates/|webapp/)"/>
	<target host="*.lucent.com"/>


	<!--	Is locale used on unsecurable domains?
							-->
	<!--securecookie host"^\.alcatel-lucent\.com$" name="^locale$" /-->
	<securecookie host="^(?:\.?applicationpartner|businessportal|service\.esd|market|www3)\.alcatel-lucent\.com$" name=".+"/>


	<rule from="^http://(?:www\.)?alcatel-lucent\.com/" to="https://www.alcatel-lucent.com/"/>

	<!--	Server drops path:
					-->
	<rule from="^http://corporatereporting\.alcatel-lucent\.com/.*" to="https://www3.alcatel-lucent.com/corporate-portal/corporate-reporting-portal.html"/>

	<rule from="^http://(applicationpartner|businessportal|developer-enterprise|service\.esd|market|my-home|(?:services\.)?support|www3)\.alcatel-lucent\.com/" to="https://$1.alcatel-lucent.com/"/>

	<!--	Server drops path:
					-->
	<rule from="^http://www2\.alcatel-lucent\.com/(?:\?.*)?$" to="https://wwww.alcatel-lucent.com/"/>

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

</ruleset>

Alcatel-Lucent.com.xml    File a bug

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

<!--
	Other Alcatel-Lucent rulesets:

		- Bell-Labs.com.xml


	CDN buckets:

		- now.eloqua.com.edgesuite.net

			- a578.g.akamai.net
			- conversation-images.alcatel-lucent.com


	Nonfunctional subdomains:

		- enterprise		(refused)
		- www.partnerlocator	(dropped)


	Problematic subdomains:

		- ^		(shows www3; mismatched, CN: alcatel-lucent.com)
		- conversation	(works; mismatched, CN: secure.eloqua.com)
		- conversation-images	(works, akamai)
		- corporatereporting	(mismatched, CN: www.homeretailgroup.com)
		- webform	(works; mismatched, CN: *.us.neolane.net)
		- www1		(data differs, valid cert)
		- www2		("site is unavailable for maintenance purposes"; expired 2006-08-30, invalid, self-signed)
			conversation-images	(→ akamai)


	Partially covered subdomains:

		- developer-enterprise	($ shows blank page)
		- www2			($ → www)


	Fully covered domains:

		- alcatel-lucent.com subdomains:

			- (www.)		(^ → www)
			- applicationpartner
			- businessportal
			- corporatereporting	(→ www3)
			- service.esd
			- market
			- my-home
			- support
			- services.support
			- www2

		- market.lucent.com
		- services.support.lucent.com

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

	<target host="alcatel-lucent.com"/>
	<target host="*.alcatel-lucent.com"/>
		<!--
			These paths show a blank page:

				- $
				- component/comprofiler/registers
				- forum/index
									-->
		<!--exclusion pattern="^http://developer-enterprise.alcatel-lucent.com/($|\?|component/comprofiler/|forum/index)" /-->
		<exclusion pattern="^http://developer-enterprise.alcatel-lucent.com/(?!api_content(?:$|[?/])|components/|images/|libraries/|media/|modules/|plugins/|templates/|webapp/)"/>
	<target host="*.lucent.com"/>


	<!--	Is locale used on unsecurable domains?
							-->
	<!--securecookie host"^\.alcatel-lucent\.com$" name="^locale$" /-->
	<securecookie host="^(?:\.?applicationpartner|businessportal|service\.esd|market|www3)\.alcatel-lucent\.com$" name=".+"/>


	<rule from="^http://(?:www\.)?alcatel-lucent\.com/" to="https://www.alcatel-lucent.com/"/>

	<!--	Server drops path:
					-->
	<rule from="^http://corporatereporting\.alcatel-lucent\.com/.*" to="https://www3.alcatel-lucent.com/corporate-portal/corporate-reporting-portal.html"/>

	<rule from="^http://(applicationpartner|businessportal|developer-enterprise|service\.esd|market|my-home|(?:services\.)?support|www3)\.alcatel-lucent\.com/" to="https://$1.alcatel-lucent.com/"/>

	<!--	Server drops path:
					-->
	<rule from="^http://www2\.alcatel-lucent\.com/(?:\?.*)?$" to="https://wwww.alcatel-lucent.com/"/>

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

</ruleset>

Alcatel-Lucent.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 ff5b4642 2019-06-27 14:21:20 -0700;
next release a7393f1a 2019-08-20 19:23:28 +0300;