<story><title>Chrome hides www and https:// in the address bar again</title><url>https://www.bleepingcomputer.com/news/google/google-chrome-hides-www-and-https-in-the-address-bar-again/</url></story><parent_chain><item><author>privateSFacct</author><text>Google sees folks falling for google-secure-payments.google.via.net type URLS. They see all the gaming people do with URLs in search results (including abusing the names of other brands like Amazon).&lt;p&gt;There are lots of developers who like distinguishing these subtle topics. I can tell you in a larger enterprise deployment most of these changes will be welcomed (yes, people do still click on bogus URLs believe it or not - FAR more often than I would expect). Or think that the url amazon.lowprice.com is an amazon website in a search result.&lt;p&gt;Folks claiming google is hiding the owner of the website forget that the actual owner of the website is reflected by the END of the domain name, not the earlier parts. In some shared hosting situations this is confusing, but in the end whoever controls the end actually is in control.</text></item><item><author>Rebelgecko</author><text>Google must really hate URLs. My search results recently stopped showing the full path of the URL, just the domain name. It was a huge pain because I was looking for an item at Ikea and couldn&amp;#x27;t tell if a result went to their American site or to their UK, Saudi Arabian, Qatari, etc. site (apparently the same item can have small differences in different countries— I almost bought the wrong lightbulbs because the UK version of my lamp uses a different size bulb).</text></item></parent_chain><comment><author>dwild</author><text>Can you tell me what&amp;#x27;s more secure and why?&lt;p&gt;&lt;pre&gt;&lt;code&gt;    Before the change: www.google.com
    After the change: google.com

    Before the change: google-secure-payments.google.via.net
    After the change: google-secure-payments.google.via.net
&lt;/code&gt;&lt;/pre&gt;
Seems to me like the same trick is available.&lt;p&gt;Now do it like Firefox:&lt;p&gt;&lt;pre&gt;&lt;code&gt;    Grey: www
    Black google.com

    Grey: google-secure-payments.google
    Black: via.net
&lt;/code&gt;&lt;/pre&gt;
Warning: Check the black portion of the URL and make sure it&amp;#x27;s the right one!</text></comment>
<story><title>Chrome hides www and https:// in the address bar again</title><url>https://www.bleepingcomputer.com/news/google/google-chrome-hides-www-and-https-in-the-address-bar-again/</url></story><parent_chain><item><author>privateSFacct</author><text>Google sees folks falling for google-secure-payments.google.via.net type URLS. They see all the gaming people do with URLs in search results (including abusing the names of other brands like Amazon).&lt;p&gt;There are lots of developers who like distinguishing these subtle topics. I can tell you in a larger enterprise deployment most of these changes will be welcomed (yes, people do still click on bogus URLs believe it or not - FAR more often than I would expect). Or think that the url amazon.lowprice.com is an amazon website in a search result.&lt;p&gt;Folks claiming google is hiding the owner of the website forget that the actual owner of the website is reflected by the END of the domain name, not the earlier parts. In some shared hosting situations this is confusing, but in the end whoever controls the end actually is in control.</text></item><item><author>Rebelgecko</author><text>Google must really hate URLs. My search results recently stopped showing the full path of the URL, just the domain name. It was a huge pain because I was looking for an item at Ikea and couldn&amp;#x27;t tell if a result went to their American site or to their UK, Saudi Arabian, Qatari, etc. site (apparently the same item can have small differences in different countries— I almost bought the wrong lightbulbs because the UK version of my lamp uses a different size bulb).</text></item></parent_chain><comment><author>ljoshua</author><text>I&amp;#x27;m wondering how the particular &lt;i&gt;address bar&lt;/i&gt; change helps alleviate this though. As I&amp;#x27;ve seen it implemented, the only subdomain they&amp;#x27;ll &amp;quot;elide&amp;quot; is www, so if it is google-secure-payments.google.via.net it will still show as such in the address bar, not as via.net. So I don&amp;#x27;t understand their reasoning in how this will help from a security standpoint.</text></comment>