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 Madison Logic rulesets:

		- MLno6.com.xml


	Problematic domains:

		- (www.)dinclinx.com	(mismatched, CN: *.madisonlogic.com)

		- (www.)madisonlogic.com

			- Data differ
			- $ redirects to Login.aspx
			- css/ & graphics/ 404


	Partially covered domains:

		- (www.)madisonlogic.com


	Fully covered domains:

		- (www.)dinclinx.com	(→ clk.madisonlogic.com)

		- madisonlogic.com subdomains:

			- blog
			- clk
			- js-agent
			- jsc
			- st


	Mixed content:

		- Script on blog from blog *

		- css:

			- On blog from blog *
			- On blog from fonts.googleapis.com **

		- Images on blog from blog ***

	* Secured by us, just a facebook widget
	** Secured by us
	*** Secured by us, doesn't trip MCB anyway

--><ruleset name="Madison Logic (partial)">

	<target host="dinclinx.com"/>
	<target host="www.dinclinx.com"/>
	<target host="www.madisonlogic.com"/>
	<target host="blog.madisonlogic.com"/>
	<target host="clk.madisonlogic.com"/>
	<target host="js-agent.madisonlogic.com"/>
	<target host="jsc.madisonlogic.com"/>
	<target host="st.madisonlogic.com"/>


	<!--	Tracking cookies:
					-->
	<securecookie host="^\.madisonlogic\.com$" name="^__(?:utm\w|zlcid)$"/>


	<rule from="^http://(?:www\.)?dinclinx\.com/" to="https://clk.madisonlogic.com/"/>

	<rule from="^http://www\.madisonlogic\.com/images/(arrow|bg|headBg|linkbutton_background|mainNav)\.gif$" to="https://www.madisonlogic.com/images/$2.gif"/>

	<!--	Included on 3rd-party websites.
						-->
	<rule from="^http://(blog|clk|js-agent|jsc|st)\.madisonlogic\.com/" to="https://$1.madisonlogic.com/"/>

</ruleset>

Madison-Logic.xml    File a bug

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

<!--
	Other Madison Logic rulesets:

		- MLno6.com.xml


	Problematic domains:

		- (www.)dinclinx.com	(mismatched, CN: *.madisonlogic.com)

		- (www.)madisonlogic.com

			- Data differ
			- $ redirects to Login.aspx
			- css/ & graphics/ 404


	Partially covered domains:

		- (www.)madisonlogic.com


	Fully covered domains:

		- (www.)dinclinx.com	(→ clk.madisonlogic.com)

		- madisonlogic.com subdomains:

			- blog
			- clk
			- js-agent
			- jsc
			- st


	Mixed content:

		- Script on blog from blog *

		- css:

			- On blog from blog *
			- On blog from fonts.googleapis.com **

		- Images on blog from blog ***

	* Secured by us, just a facebook widget
	** Secured by us
	*** Secured by us, doesn't trip MCB anyway

--><ruleset name="Madison Logic (partial)">

	<target host="dinclinx.com"/>
	<target host="www.dinclinx.com"/>
	<target host="www.madisonlogic.com"/>
	<target host="blog.madisonlogic.com"/>
	<target host="clk.madisonlogic.com"/>
	<target host="js-agent.madisonlogic.com"/>
	<target host="jsc.madisonlogic.com"/>
	<target host="st.madisonlogic.com"/>


	<!--	Tracking cookies:
					-->
	<securecookie host="^\.madisonlogic\.com$" name="^__(?:utm\w|zlcid)$"/>


	<rule from="^http://(?:www\.)?dinclinx\.com/" to="https://clk.madisonlogic.com/"/>

	<rule from="^http://www\.madisonlogic\.com/images/(arrow|bg|headBg|linkbutton_background|mainNav)\.gif$" to="https://www.madisonlogic.com/images/$2.gif"/>

	<!--	Included on 3rd-party websites.
						-->
	<rule from="^http://(blog|clk|js-agent|jsc|st)\.madisonlogic\.com/" to="https://$1.madisonlogic.com/"/>

</ruleset>

Madison-Logic.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;