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 Zendesk rulesets:

		- Zdassets.com.xml


	CDN buckets:

		- s3.amazonaws.com/zd-assets/ | d16cvnquvjw7pr.cloudfront.net


	Clients with custom domains redirect back to said domains when rewritten
	to their respective zendesk.com subdomains. All resources on client
	pages are fetched from assets.zendesk.com, save for:

		- favicon.ico
		- generated/
		- system/.+/favicon.ico
		- widgets/


	Problematic domains:

		- cdn.zendesk.com *
		- hello.zendesk.com *
		- app.hello.zendesk.com *
		- radar.zendesk.com *

	* Mismatched

	Fully covered domains:

		- p6assets.zendesk.com


	Mixed content:

		- Images, on:

			- www from s3.amazonaws.com
			- www from d26a57ydsghvgx.cloudfront.net

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

	<target host="zendesk.com"/>
	<target host="*.zendesk.com"/>

		<exclusion pattern="^http://hello\.zendesk\.com/"/>
		<test url="http://hello.zendesk.com/"/>

		<!-- See https://github.com/EFForg/https-everywhere/issues/9159 -->
		<exclusion pattern="^http://app\.hello\.zendesk\.com/"/>
		<test url="http://app.hello.zendesk.com/"/>

		<exclusion pattern="^http://radar\.zendesk\.com/"/>
		<test url="http://radar.zendesk.com/"/>

		<exclusion pattern="^http://video\.zendesk\.com/"/>
		<test url="http://video.zendesk.com/"/>

		<!--	Direct rewrites:
					-->
		<test url="http://developer.zendesk.com/"/>
		<test url="http://support.zendesk.com/"/>
		<test url="http://www.zendesk.com/"/>

		<!--	Special cases:
					-->
		<test url="http://cdn.zendesk.com/"/>


	<!--	Not secured by server:
					-->
	<!--securecookie host="^\.zendesk\.com$" name="^(__cfduid|__qca|cf_clearance)$" /-->
	<!--securecookie host="^p6assets\.zendesk\.com$" name="^(_zendesk_session|_zendesk_shared_session)$" /-->

	<!--securecookie host="^(.*\.)?zendesk\.com$" name=".+" /-->

	<securecookie host="^\.zendesk\.com$" name="^(?:__cfduid|__qca|cf_clearance)$"/>
	<securecookie host="^p\dassets\.zendesk\.com$" name=".+"/>


	<rule from="^http://cdn\.zendesk\.com/" to="https://d16cvnquvjw7pr.cloudfront.net/"/>

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

</ruleset>

Zendesk.com.xml    File a bug

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

<!--
	Other Zendesk rulesets:

		- Zdassets.com.xml


	CDN buckets:

		- s3.amazonaws.com/zd-assets/ | d16cvnquvjw7pr.cloudfront.net


	Clients with custom domains redirect back to said domains when rewritten
	to their respective zendesk.com subdomains. All resources on client
	pages are fetched from assets.zendesk.com, save for:

		- favicon.ico
		- generated/
		- system/.+/favicon.ico
		- widgets/


	Problematic domains:

		- cdn.zendesk.com *
		- hello.zendesk.com *
		- app.hello.zendesk.com *
		- radar.zendesk.com *

	* Mismatched

	Fully covered domains:

		- p6assets.zendesk.com


	Mixed content:

		- Images, on:

			- www from s3.amazonaws.com
			- www from d26a57ydsghvgx.cloudfront.net

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

	<target host="zendesk.com"/>
	<target host="*.zendesk.com"/>

		<exclusion pattern="^http://hello\.zendesk\.com/"/>
		<test url="http://hello.zendesk.com/"/>

		<!-- See https://github.com/EFForg/https-everywhere/issues/9159 -->
		<exclusion pattern="^http://app\.hello\.zendesk\.com/"/>
		<test url="http://app.hello.zendesk.com/"/>

		<exclusion pattern="^http://radar\.zendesk\.com/"/>
		<test url="http://radar.zendesk.com/"/>

		<exclusion pattern="^http://video\.zendesk\.com/"/>
		<test url="http://video.zendesk.com/"/>

		<!--	Direct rewrites:
					-->
		<test url="http://developer.zendesk.com/"/>
		<test url="http://support.zendesk.com/"/>
		<test url="http://www.zendesk.com/"/>

		<!--	Special cases:
					-->
		<test url="http://cdn.zendesk.com/"/>


	<!--	Not secured by server:
					-->
	<!--securecookie host="^\.zendesk\.com$" name="^(__cfduid|__qca|cf_clearance)$" /-->
	<!--securecookie host="^p6assets\.zendesk\.com$" name="^(_zendesk_session|_zendesk_shared_session)$" /-->

	<!--securecookie host="^(.*\.)?zendesk\.com$" name=".+" /-->

	<securecookie host="^\.zendesk\.com$" name="^(?:__cfduid|__qca|cf_clearance)$"/>
	<securecookie host="^p\dassets\.zendesk\.com$" name=".+"/>


	<rule from="^http://cdn\.zendesk\.com/" to="https://d16cvnquvjw7pr.cloudfront.net/"/>

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

</ruleset>

Zendesk.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 33860265 2019-12-09 04:21:45 +0000;