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:

<!--
Disabled by https-everywhere-checker because:
Fetch error: http://perel.eu/ => https://www.perel.eu/: (6, 'Could not resolve host: perel.eu')
	Unsupported domains (non-exhaustive list):

	hps140.com			(cannot find server)
	www.hps140.com			(certificate only valid for www.velleman.eu)
	k8200.eu			(ditto)
	www.k8200.eu			(ditto)
	velbus.eu			(ditto)
	www.velbus.eu			(ditto)
	forum.velleman.be		(cannot establish connection)
	portal.velleman.be		(certificate only valid for portal.velleman.eu)
	forum.velleman.eu		(cannot establish connection)
	vellemaninstruments.com		(cannot find server)
	www.vellemaninstruments.com	(certificate only valid for www.velleman.eu)
	velleman-kit.com		(ditto)
	www.velleman-kit.com		(ditto)
	vellemanprojects.eu		(cannot find server)
	www.vellemanprojects.eu		(certificate only valid for www.velleman.eu)

	The ruleset redirects portal.velleman.be requests to the portal.velleman.eu
	domain.
--><ruleset name="Velleman Group (partial)">
	<target host="hqpower.eu"/>
	<target host="www.hqpower.eu"/>

	<securecookie host="^www\.hqpower\.eu$" name=".+"/>

	<rule from="^http://(?:www\.)?hqpower\.eu/" to="https://www.hqpower.eu/"/>

	<target host="perel.eu"/>
	<target host="www.perel.eu"/>

	<securecookie host="^www\.perel\.eu$" name=".+"/>

	<rule from="^http://(?:www\.)?perel\.eu/" to="https://www.perel.eu/"/>

	<target host="velleman.be"/>
	<target host="portal.velleman.be"/>
	<target host="www.velleman.be"/>

	<rule from="^http://(?:www\.)?velleman\.be/" to="https://www.velleman.eu/"/>
	<!--
		By default, requests for http://portal.velleman.be/ (where there is nothing after the final slash)
		seem to redirect to https://portal.velleman.be/ServicePortal/ which gives an error about the SSL
		certificate only being valid for the portal.velleman.eu domain. As such, this ruleset redirects such
		requests to the https://portal.velleman.eu/ServicePortal/ URL. Other HTTP and HTTPS requests in the
		portal.velleman.be domain are redirected to the equivalent URL in the portal.velleman.eu domain
		(August 30, 2013.)
	-->
	<rule from="^http://portal\.velleman\.be/$" to="https://portal.velleman.eu/ServicePortal/"/>
	<rule from="^http://portal\.velleman\.be/(.+)" to="https://portal.velleman.eu/$1"/>

	<target host="velleman.eu"/>
	<target host="portal.velleman.eu"/>
	<target host="www.velleman.eu"/>

	<securecookie host="^(?:portal|www)\.velleman\.eu$" name=".+"/>

	<rule from="^http://(?:www\.)?velleman\.eu/" to="https://www.velleman.eu/"/>
	<!--
		By default, requests for http://portal.velleman.eu/ or https://portal.velleman.eu/ (where there is
		nothing after the final slash) seem to redirect to https://portal.velleman.be/ServicePortal/ which
		gives an error about the SSL certificate only being valid for the portal.velleman.eu domain. As such,
		this ruleset redirects such requests to the https://portal.velleman.eu/ServicePortal/ URL
		(August 30, 2013.)
	-->
	<rule from="^http://portal\.velleman\.eu/$" to="https://portal.velleman.eu/ServicePortal/"/>
	<rule from="^http://portal\.velleman\.eu/(.+)" to="https://portal.velleman.eu/$1"/>

	<target host="vellemanusa.com"/>
	<target host="www.vellemanusa.com"/>

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

	<rule from="^http://(?:www\.)?vellemanusa\.com/" to="https://www.vellemanusa.com/"/>
</ruleset>

Velleman-Group.xml    File a bug

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

<!--
Disabled by https-everywhere-checker because:
Fetch error: http://perel.eu/ => https://www.perel.eu/: (6, 'Could not resolve host: perel.eu')
	Unsupported domains (non-exhaustive list):

	hps140.com			(cannot find server)
	www.hps140.com			(certificate only valid for www.velleman.eu)
	k8200.eu			(ditto)
	www.k8200.eu			(ditto)
	velbus.eu			(ditto)
	www.velbus.eu			(ditto)
	forum.velleman.be		(cannot establish connection)
	portal.velleman.be		(certificate only valid for portal.velleman.eu)
	forum.velleman.eu		(cannot establish connection)
	vellemaninstruments.com		(cannot find server)
	www.vellemaninstruments.com	(certificate only valid for www.velleman.eu)
	velleman-kit.com		(ditto)
	www.velleman-kit.com		(ditto)
	vellemanprojects.eu		(cannot find server)
	www.vellemanprojects.eu		(certificate only valid for www.velleman.eu)

	The ruleset redirects portal.velleman.be requests to the portal.velleman.eu
	domain.
--><ruleset name="Velleman Group (partial)">
	<target host="hqpower.eu"/>
	<target host="www.hqpower.eu"/>

	<securecookie host="^www\.hqpower\.eu$" name=".+"/>

	<rule from="^http://(?:www\.)?hqpower\.eu/" to="https://www.hqpower.eu/"/>

	<target host="perel.eu"/>
	<target host="www.perel.eu"/>

	<securecookie host="^www\.perel\.eu$" name=".+"/>

	<rule from="^http://(?:www\.)?perel\.eu/" to="https://www.perel.eu/"/>

	<target host="velleman.be"/>
	<target host="portal.velleman.be"/>
	<target host="www.velleman.be"/>

	<rule from="^http://(?:www\.)?velleman\.be/" to="https://www.velleman.eu/"/>
	<!--
		By default, requests for http://portal.velleman.be/ (where there is nothing after the final slash)
		seem to redirect to https://portal.velleman.be/ServicePortal/ which gives an error about the SSL
		certificate only being valid for the portal.velleman.eu domain. As such, this ruleset redirects such
		requests to the https://portal.velleman.eu/ServicePortal/ URL. Other HTTP and HTTPS requests in the
		portal.velleman.be domain are redirected to the equivalent URL in the portal.velleman.eu domain
		(August 30, 2013.)
	-->
	<rule from="^http://portal\.velleman\.be/$" to="https://portal.velleman.eu/ServicePortal/"/>
	<rule from="^http://portal\.velleman\.be/(.+)" to="https://portal.velleman.eu/$1"/>

	<target host="velleman.eu"/>
	<target host="portal.velleman.eu"/>
	<target host="www.velleman.eu"/>

	<securecookie host="^(?:portal|www)\.velleman\.eu$" name=".+"/>

	<rule from="^http://(?:www\.)?velleman\.eu/" to="https://www.velleman.eu/"/>
	<!--
		By default, requests for http://portal.velleman.eu/ or https://portal.velleman.eu/ (where there is
		nothing after the final slash) seem to redirect to https://portal.velleman.be/ServicePortal/ which
		gives an error about the SSL certificate only being valid for the portal.velleman.eu domain. As such,
		this ruleset redirects such requests to the https://portal.velleman.eu/ServicePortal/ URL
		(August 30, 2013.)
	-->
	<rule from="^http://portal\.velleman\.eu/$" to="https://portal.velleman.eu/ServicePortal/"/>
	<rule from="^http://portal\.velleman\.eu/(.+)" to="https://portal.velleman.eu/$1"/>

	<target host="vellemanusa.com"/>
	<target host="www.vellemanusa.com"/>

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

	<rule from="^http://(?:www\.)?vellemanusa\.com/" to="https://www.vellemanusa.com/"/>
</ruleset>

Velleman-Group.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 ff5b4642b 2019-06-27 14:21:20 -0700;
next release c0a0e49cd 2019-10-16 02:46:21 +0300;