3 ms·
Browsers are thankfully highlighting the https-verified part of the URL (hostname) relative to the rest, so that a "paypal.com.fake.com" phishing attack is easi
by usrusr 9y ago
Browsers are thankfully highlighting the https-verified part of the URL (hostname) relative to the rest, so that a "paypal.com.fake.com" phishing attack is easier to spot. It was just a matter of time before UX people would put that highlighting to creative use. I like it.
On the technological side, I guess separate hostnames might make some ops things a little easier. But that alone can hardly be the reason. Easier and good looks can. Also: In a large scale outage, an about.x.com that is not running on your main cloud provider could be valuable for status updates, because far more people would know about about.x.com than about some status.x.com you might have if your "about" content was on the main hostname.
- jrimbault 9y agoI don't see this highlighting in the latest Chrome (60.0.3something, I just updated it). Is there a specific flag to enable ?
- IshKebab 9y agoI think it might be a mobile-only thing.
- kuschku 9y agoFirefox and Safari also have it on Desktop: https://i.imgur.com/6lDFgIp.png https://i.imgur.com/6lDFgIp.png
- jrimbault 9y agoAh! I see it. I expected something much more obvious.
- usrusr 9y agoAnd I expected something which includes the subdomain part in the highlighting. Doing a little "TN-display dance" I see that Chrome highlights news.ycombinator.com, whereas Firefox only highlights ycombinator.com which kind of undermines my point (and seems slightly wrong to me, as this seems to be a certificate for the exact third level domain, not a wildcard under the second level).