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:

<!--
	Problematic domains:

		- blog.launchpad.net *

	* Self-signed


	Partially covered subdomains:

		- feeds *

	* Redirects to http


	Fully covered domains:

		- launchpad.net

		- [\w.-]+.launchpad.net: *

			- answers
			- bazaar
			- blueprints
			- code
			- edge
			- help
			- login
			- translations
			- www

	* Except where excluded below


	These altnames don't exist:

		- www.login.launchpad.net


	Insecure cookies are set for these domains:

		- blog.launchpad.net
		- login.launchpad.net


	Mixed content:

		- Image on blog from ubuntuone.com ¹
		- Bugs on blog, help from i.creativecommons.org ²

	¹ Unsecurable <= supports <=ssl3 only
	² Secured by us

--><ruleset name="Launchpad">
    <target host="launchpad.net"/>
    <target host="*.launchpad.net"/>
    <target host="launchpadlibrarian.net"/>
    <target host="*.launchpadlibrarian.net"/>

		<!--
			We preempt redirect from $:
							-->
		<exclusion pattern="^http://feeds\.launchpad\.net/(?!$)"/>
		<exclusion pattern="^http://ppa\.launchpad\.net/"/>

			<test url="http://feeds.launchpad.net/"/>
			<test url="http://feeds.launchpad.net/rohc/announcements.atom"/>
			<test url="http://ppa.launchpad.net/"/>


		<test url="http://answers.launchpad.net/"/>
		<test url="http://bazaar.launchpad.net/"/>
		<test url="http://blueprints.launchpad.net/"/>
		<test url="http://code.launchpad.net/"/>
		<test url="http://edge.launchpad.net/"/>
		<test url="http://help.launchpad.net/"/>
		<test url="http://login.launchpad.net/"/>
		<test url="http://translations.launchpad.net/"/>
		<test url="http://www.launchpad.net/"/>

		<test url="http://launchpadlibrarian.net/"/>


	<!--	Not secured by server:
					-->    <securecookie host="^(?:.*\.)?launchpadlibrarian\.net$" name=".+"/>

    <exclusion pattern="^http://blog\.launchpad\.net/"/>
    <exclusion pattern="^http://news\.launchpad\.net/"/>

		<test url="http://blog.launchpad.net/"/>
		<test url="http://news.launchpad.net/"/>

    <!-- For the bazaar.launchpad.net domain, the URL
         http://bazaar.launchpad.net/ (where there is nothing after the final
         slash) should be directed to https://launchpad.net/ as a special case.
         URLs such as http://bazaar.launchpad.net/~example/ where content
         does come after the final slash should be handled as normal. -->
    <rule from="^http://bazaar\.launchpad\.net/$" to="https://launchpad.net/"/>

	<!--	Redirects as so:
					-->
	<rule from="^http://feeds\.launchpad\.net/$" to="https://help.launchpad.net/Feeds"/>

		<test url="http://feeds.launchpad.net//"/>

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

</ruleset>

Launchpad.xml    File a bug

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

<!--
	Problematic domains:

		- blog.launchpad.net *

	* Self-signed


	Partially covered subdomains:

		- feeds *

	* Redirects to http


	Fully covered domains:

		- launchpad.net

		- [\w.-]+.launchpad.net: *

			- answers
			- bazaar
			- blueprints
			- code
			- edge
			- help
			- login
			- translations
			- www

	* Except where excluded below


	These altnames don't exist:

		- www.login.launchpad.net


	Insecure cookies are set for these domains:

		- blog.launchpad.net
		- login.launchpad.net


	Mixed content:

		- Image on blog from ubuntuone.com ¹
		- Bugs on blog, help from i.creativecommons.org ²

	¹ Unsecurable <= supports <=ssl3 only
	² Secured by us

--><ruleset name="Launchpad">
    <target host="launchpad.net"/>
    <target host="*.launchpad.net"/>
    <target host="launchpadlibrarian.net"/>
    <target host="*.launchpadlibrarian.net"/>

		<!--
			We preempt redirect from $:
							-->
		<exclusion pattern="^http://feeds\.launchpad\.net/(?!$)"/>
		<exclusion pattern="^http://ppa\.launchpad\.net/"/>

			<test url="http://feeds.launchpad.net/"/>
			<test url="http://feeds.launchpad.net/rohc/announcements.atom"/>
			<test url="http://ppa.launchpad.net/"/>


		<test url="http://answers.launchpad.net/"/>
		<test url="http://bazaar.launchpad.net/"/>
		<test url="http://blueprints.launchpad.net/"/>
		<test url="http://code.launchpad.net/"/>
		<test url="http://edge.launchpad.net/"/>
		<test url="http://help.launchpad.net/"/>
		<test url="http://login.launchpad.net/"/>
		<test url="http://translations.launchpad.net/"/>
		<test url="http://www.launchpad.net/"/>

		<test url="http://launchpadlibrarian.net/"/>


	<!--	Not secured by server:
					-->    <securecookie host="^(?:.*\.)?launchpadlibrarian\.net$" name=".+"/>

    <exclusion pattern="^http://blog\.launchpad\.net/"/>
    <exclusion pattern="^http://news\.launchpad\.net/"/>

		<test url="http://blog.launchpad.net/"/>
		<test url="http://news.launchpad.net/"/>

    <!-- For the bazaar.launchpad.net domain, the URL
         http://bazaar.launchpad.net/ (where there is nothing after the final
         slash) should be directed to https://launchpad.net/ as a special case.
         URLs such as http://bazaar.launchpad.net/~example/ where content
         does come after the final slash should be handled as normal. -->
    <rule from="^http://bazaar\.launchpad\.net/$" to="https://launchpad.net/"/>

	<!--	Redirects as so:
					-->
	<rule from="^http://feeds\.launchpad\.net/$" to="https://help.launchpad.net/Feeds"/>

		<test url="http://feeds.launchpad.net//"/>

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

</ruleset>

Launchpad.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 ff5b4642 2019-06-27 14:21:20 -0700;
next release 595db303 2019-07-19 21:05:52 +0930;