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.

<!--
	For other Budget coverage, see Budget.com.xml


	Non-functional subdomains:
		- locations		(e)
		- mail			(s)

	e: expired certificate
	h: http redirect
	i: invalid certificate chain
	m: certificate mismatch
	r: connection refused
	s: self-signed certificate
	t: timeout on https
--><ruleset name="Budget.com.ar">

	<target host="budget.com.ar"/>
	<target host="www.budget.com.ar"/>

	<securecookie host=".+" name=".+"/>

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

<!--
	For other Budget coverage, see Budget.com.xml


	Non-functional subdomains:
		- locations		(e)
		- mail			(s)

	e: expired certificate
	h: http redirect
	i: invalid certificate chain
	m: certificate mismatch
	r: connection refused
	s: self-signed certificate
	t: timeout on https
--><ruleset name="Budget.com.ar">

	<target host="budget.com.ar"/>
	<target host="www.budget.com.ar"/>

	<securecookie host=".+" name=".+"/>

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

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;