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://st.yell.com/ => https://st.yell.com/: (6, 'Could not resolve host: st.yell.com')

	Note: This website blocks Tor users.


	Problematic hosts in *yell.com:

		- (www.)? ᵀ
		- hotels ᵐ

	ᵀ Blocks Tor users
	ᵐ Mismatched


	Partially covered hosts in *yell.com:

		- marketing *

	* Some pages redirect to http, others 404


	Mixed content:

		- Images on marketing from st.yell.com ˢ

	ˢ Secured by us

--><ruleset name="Yell.com (partial)" default_off="failed ruleset test">

	<!--	Direct rewrites:
				-->
	<!--target host="yell.com" />		needs clearnet testing -->
	<target host="auth.yell.com"/>
	<target host="business.yell.com"/>
	<target host="careers.yell.com"/>
	<target host="s-omniture.yell.com"/>
	<target host="st.yell.com"/>
	<!--target host="www.yell.com" />	needs clearnet testing -->

	<!--	Complications:
				-->
	<target host="marketing.yell.com"/>

		<!--	Redirects to http:
						-->
		<!--exclusion pattern="^http://marketing\.yell\.com/(?:$|contact\.html)" /-->
		<!--
			404:
				-->
		<!--exclusion pattern="^http://marketing\.yell\.com/contact/$" /-->
		<!--
			Exceptions:
					-->
		<!--exclusion pattern="^http://marketing\.yell\.com/(?!help(?:$|[?/]))" /-->
		<!--
			(& preempted redirect:)
						-->
		<exclusion pattern="^http://marketing\.yell\.com/+(?!$|help(?:$|[?/]))"/>

			<!--	+ve:
					-->
			<test url="http://marketing.yell.com/contact.html"/>
			<test url="http://marketing.yell.com/contact/"/>
			<test url="http://marketing.yell.com/legal/prominence-rules/"/>
			<test url="http://marketing.yell.com/legal/security-policy/"/>
			<test url="http://marketing.yell.com/legal/sms-spec/"/>
			<test url="http://marketing.yell.com/web-design/yell-com/"/>

			<!--	-ve:
					-->
			<test url="http://marketing.yell.com/help/accounts-billing.html"/>


	<securecookie host="^\." name="^(?:_gat?$|s_v\w)"/>
	<securecookie host="^(?!marketing\.)\w" name=".+"/>


	<!--	Redirects to http first:
					-->
	<rule from="^http://marketing\.yell\.com/$" to="https://business.yell.com/"/>

		<!--	There be faulty regex somewhere
			in the coverage checker...
							-->
		<test url="http://marketing.yell.com/"/>

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

</ruleset>

yell.com.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://st.yell.com/ => https://st.yell.com/: (6, 'Could not resolve host: st.yell.com')

	Note: This website blocks Tor users.


	Problematic hosts in *yell.com:

		- (www.)? ᵀ
		- hotels ᵐ

	ᵀ Blocks Tor users
	ᵐ Mismatched


	Partially covered hosts in *yell.com:

		- marketing *

	* Some pages redirect to http, others 404


	Mixed content:

		- Images on marketing from st.yell.com ˢ

	ˢ Secured by us

--><ruleset name="Yell.com (partial)" default_off="failed ruleset test">

	<!--	Direct rewrites:
				-->
	<!--target host="yell.com" />		needs clearnet testing -->
	<target host="auth.yell.com"/>
	<target host="business.yell.com"/>
	<target host="careers.yell.com"/>
	<target host="s-omniture.yell.com"/>
	<target host="st.yell.com"/>
	<!--target host="www.yell.com" />	needs clearnet testing -->

	<!--	Complications:
				-->
	<target host="marketing.yell.com"/>

		<!--	Redirects to http:
						-->
		<!--exclusion pattern="^http://marketing\.yell\.com/(?:$|contact\.html)" /-->
		<!--
			404:
				-->
		<!--exclusion pattern="^http://marketing\.yell\.com/contact/$" /-->
		<!--
			Exceptions:
					-->
		<!--exclusion pattern="^http://marketing\.yell\.com/(?!help(?:$|[?/]))" /-->
		<!--
			(& preempted redirect:)
						-->
		<exclusion pattern="^http://marketing\.yell\.com/+(?!$|help(?:$|[?/]))"/>

			<!--	+ve:
					-->
			<test url="http://marketing.yell.com/contact.html"/>
			<test url="http://marketing.yell.com/contact/"/>
			<test url="http://marketing.yell.com/legal/prominence-rules/"/>
			<test url="http://marketing.yell.com/legal/security-policy/"/>
			<test url="http://marketing.yell.com/legal/sms-spec/"/>
			<test url="http://marketing.yell.com/web-design/yell-com/"/>

			<!--	-ve:
					-->
			<test url="http://marketing.yell.com/help/accounts-billing.html"/>


	<securecookie host="^\." name="^(?:_gat?$|s_v\w)"/>
	<securecookie host="^(?!marketing\.)\w" name=".+"/>


	<!--	Redirects to http first:
					-->
	<rule from="^http://marketing\.yell\.com/$" to="https://business.yell.com/"/>

		<!--	There be faulty regex somewhere
			in the coverage checker...
							-->
		<test url="http://marketing.yell.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 80b59db95 2019-01-31 14:20:13 -0800;
next release 0af4c03e7 2019-04-21 17:47:19 +0200;