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 release branch contains the following rules that are enabled by default:
For other JPMorgan Chase coverage, see Chase.xml.
Insecure cookies are set for these hosts:
--><ruleset name="The Explorer Card.com">
<!-- Not secured by server:
<!--securecookie host="^www\.theexplorercard\.com$" name="^(ASP\.NET_SessionID|cookiecheck)$" /-->
<securecookie host="^www\.theexplorercard\.com$" name=".+"/>
<rule from="^http:" to="https:"/>
File a bug
The HTTPS Everywhere developers welcome corrections and updates to rules. Please see our
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 2d5e1314 2020-08-13 11:58:12 -0700;
next release a3e09c59 2021-01-22 10:53:38 -0800;