Hacker News Reader

Cool to know, i guess.

TIL that dotless record on newer gTLDs is forbidden, which explains my age-old question: "if google holds google., why are they only using it on domains.google? Surely having the url https://google would be desirable for the folks in marketing?". The answer is that they can't possibly because the ban was added precisely because of this.

View on HN

It's not really the same, but Microsoft has https://www.microsoft/ as a redirect to their .com, which causes some weird side effects in Chrome's omnibox, because it automatically adds the www subdomain: https://imgur.com/a/2cVxnYf

Google actually serves a bunch of pages through their TLD:

https://en.wikipedia.org/wiki/.google

Google Search is actually a useful way to find sites on a TLD:

https://www.google.com/search?q=site%3Agoogle https://www.google.com/search?q=site%3Agle https://www.google.com/search?q=site%3Agoog

This works with DuckDuckGo as well: https://news.ycombinator.com/item?id=32473643

You can combine the exclusion `-` syntax with this as well. If you want to find different sites on the TLD `.test` but only URLs on `home.test` are being shown, you can use this search:

site:test -site:home.test

I think it’s obvious that they use their TLD, just not via a root A record, so resources aren’t loaded via https://google/some.js

Reply on news.ycombinator.com