<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Good point, John! I'm guessing the reasoning here is that some
companies have an instance of their domain in each of many
countries. Google has google.ac, google.ad, google.ae, and so on, as
seen at <a
href="https://chromium.googlesource.com/chromium/src/net/+/master/http/transport_security_state_static.json">https://chromium.googlesource.com/chromium/src/net/+/master/http/transport_security_state_static.json</a>.<br>
<br>
Although Google has a listing they keep up to date, for most
companies it would be hard to generate this list and keep it up to
date.<br>
<br>
Perhaps a more explicit implementation would allow you to specify:<br>
<br>
<target host="<span class="moz-txt-link-abbreviated"><a class="moz-txt-link-abbreviated" href="http://www.google.PUBLIC_SUFFIX">www.google.PUBLIC_SUFFIX</a></span>"><br>
<br>
HTTPS Everywhere could bundle the latest version of the Public
Suffix List (
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
<a href="http://publicsuffix.org/">http://publicsuffix.org/</a>).
Then, to look up a given hostname it would first try the literal
hostname, then replace any public suffix at the end of the hostname
with the string ".PUBLIC_SUFFIX" and try again.<br>
<br>
BTW, I was surprised how many rules follow this pattern - 1899 by my
naive grep!
</body>
</html>