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 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://aggregateknowledge.com// => https://www.aggregateknowledge.com/: (60, 'SSL certificate problem: certificate has expired')
Fetch error: http://www.aggregateknowledge.com/ => https://www.aggregateknowledge.com/: (60, 'SSL certificate problem: certificate has expired')
Fetch error: http://aggregateknowledge.com/ => https://www.aggregateknowledge.com/: (60, 'SSL certificate problem: certificate has expired')
Fetch error: http://creative.aggregateknowledge.com/ => https://www.aggregateknowledge.com/: (60, 'SSL certificate problem: certificate has expired')
Fetch error: http://www-stage.aggregateknowledge.com/ => https://www.aggregateknowledge.com/: (60, 'SSL certificate problem: certificate has expired')

	For other Neustar coverage, see NeuStar.xml.


	CDN buckets:

		- d37f3s04rhujtb.cloudfront.net

			- content.aggregateknowledge.com


	Nonfunctional aggregateknowledge.com subdomains:

		- cust
		- demo		(times out)
		- docs
		- mail
		- sjc[12]


	Problematic aggregateknowledge.com subdomains:

		- ^ *
		- creative *
		- www-stage *

	* Mismatched


	images: Drop


	Insecure cookies are set for these domains:

		- .aggregateknowledge.com

--><ruleset name="Aggregate Knowledge.com" default_off="failed ruleset test">

	<target host="content.aggregateknowledge.com"/>
	<target host="dashboard.aggregateknowledge.com"/>
	<target host="data.aggregateknowledge.com"/>
	<target host="ui.aggregateknowledge.com"/>
	<target host="www.aggregateknowledge.com"/>

	<!--	Complications:
				-->
	<target host="aggregateknowledge.com"/>
	<target host="creative.aggregateknowledge.com"/>
	<target host="www-stage.aggregateknowledge.com"/>

		<!--	$ redirects to www.404.html, so appease fetch tester.

			Obviously this makes us stand out more, but
			preventing @jsha from disabling the ruleset is
			more important than blending in.
									-->
		<exclusion pattern="^http://data\.aggregateknowledge\.com/$"/>


	<!--	Not secured by server:
					-->
	<!--securecookie host="^\.aggregateknowledge\.com$" name="(?:u|uuid)$" /-->

	<securecookie host="^\.aggregateknowledge\.com$" name=".+"/>


	<!--	Redirect keeps path and args,
		but not forward slash:
					-->
	<rule from="^http://aggregateknowledge\.com/+" to="https://www.aggregateknowledge.com/"/>

		<test url="http://aggregateknowledge.com//"/>

	<rule from="^http://(?:creative|www-stage)\.aggregateknowledge\.com/" to="https://www.aggregateknowledge.com/"/>

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

</ruleset>

Aggregate_Knowledge.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://aggregateknowledge.com// => https://www.aggregateknowledge.com/: (60, 'SSL certificate problem: certificate has expired')
Fetch error: http://www.aggregateknowledge.com/ => https://www.aggregateknowledge.com/: (60, 'SSL certificate problem: certificate has expired')
Fetch error: http://aggregateknowledge.com/ => https://www.aggregateknowledge.com/: (60, 'SSL certificate problem: certificate has expired')
Fetch error: http://creative.aggregateknowledge.com/ => https://www.aggregateknowledge.com/: (60, 'SSL certificate problem: certificate has expired')
Fetch error: http://www-stage.aggregateknowledge.com/ => https://www.aggregateknowledge.com/: (60, 'SSL certificate problem: certificate has expired')

	For other Neustar coverage, see NeuStar.xml.


	CDN buckets:

		- d37f3s04rhujtb.cloudfront.net

			- content.aggregateknowledge.com


	Nonfunctional aggregateknowledge.com subdomains:

		- cust
		- demo		(times out)
		- docs
		- mail
		- sjc[12]


	Problematic aggregateknowledge.com subdomains:

		- ^ *
		- creative *
		- www-stage *

	* Mismatched


	images: Drop


	Insecure cookies are set for these domains:

		- .aggregateknowledge.com

--><ruleset name="Aggregate Knowledge.com" default_off="failed ruleset test">

	<target host="content.aggregateknowledge.com"/>
	<target host="dashboard.aggregateknowledge.com"/>
	<target host="data.aggregateknowledge.com"/>
	<target host="ui.aggregateknowledge.com"/>
	<target host="www.aggregateknowledge.com"/>

	<!--	Complications:
				-->
	<target host="aggregateknowledge.com"/>
	<target host="creative.aggregateknowledge.com"/>
	<target host="www-stage.aggregateknowledge.com"/>

		<!--	$ redirects to www.404.html, so appease fetch tester.

			Obviously this makes us stand out more, but
			preventing @jsha from disabling the ruleset is
			more important than blending in.
									-->
		<exclusion pattern="^http://data\.aggregateknowledge\.com/$"/>


	<!--	Not secured by server:
					-->
	<!--securecookie host="^\.aggregateknowledge\.com$" name="(?:u|uuid)$" /-->

	<securecookie host="^\.aggregateknowledge\.com$" name=".+"/>


	<!--	Redirect keeps path and args,
		but not forward slash:
					-->
	<rule from="^http://aggregateknowledge\.com/+" to="https://www.aggregateknowledge.com/"/>

		<test url="http://aggregateknowledge.com//"/>

	<rule from="^http://(?:creative|www-stage)\.aggregateknowledge\.com/" to="https://www.aggregateknowledge.com/"/>

	<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 6a955e7 2018-11-01 05:00:06 -0700;
next release e7f9f87 2018-12-14 12:11:54 -0700;