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 other Adobe coverage, see Adobe.xml.


	These wildcard cookies are set on whichever
	domain these web bugs are loaded on:

		- s_cc
		- s_fid
		- s_sq

--><ruleset name="Adobetag.com">

	<target host="www.adobetag.com"/>
	<target host="assets.adobedtm.com"/>
	<!--delivery.d2.sv.omtrdc.net
	demand.assets.adobe.com
	survey.112.2o7.net
	survey.122.2o7.net
	success.acrobat.com
	www.omniture-static.com
	delivery.d1.sv.omtrdc.net
	www.echosign.adobe.com
	www.everestads.net
	ak-www.stage.acrobat.com
	ak-stage.echosign.adobe.com
	-->
	<securecookie host="^www\.adobetag\.com$" name=".+"/>

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

</ruleset>

Adobetag.com.xml    File a bug

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

<!--
	For other Adobe coverage, see Adobe.xml.


	These wildcard cookies are set on whichever
	domain these web bugs are loaded on:

		- s_cc
		- s_fid
		- s_sq

--><ruleset name="Adobetag.com">

	<target host="www.adobetag.com"/>
	<target host="assets.adobedtm.com"/>
	<!--delivery.d2.sv.omtrdc.net
	demand.assets.adobe.com
	survey.112.2o7.net
	survey.122.2o7.net
	success.acrobat.com
	www.omniture-static.com
	delivery.d1.sv.omtrdc.net
	www.echosign.adobe.com
	www.everestads.net
	ak-www.stage.acrobat.com
	ak-stage.echosign.adobe.com
	-->
	<securecookie host="^www\.adobetag\.com$" name=".+"/>

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

</ruleset>

Adobetag.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 e081f423 2019-11-21 04:21:36 +0000;