3 ms·
Google owns the .google TLD, could they theoretically use https://google https://google or is that not allowed?
by jsheard 2y ago
Google owns the .google TLD, could they theoretically use https://google https://google or is that not allowed?
- redserk 2y agoNot sure if that’s allowed, but that sure feels like a throwback to AOL keywords if it was — just at the DNS level.
- deleted 2y ago[deleted]
- equinoxnemesis 2y agoNot allowed for gTLDs. Some ccTLDs do it, http://ai/ http://ai/ resolved as recently as a year ago though I can't get it to right now.
- jsheard 2y agoGoing by the Wayback Machine it looks like it used to redirect to http://www.ai http://www.ai, which still works, but only over HTTP.
- Thorrez 2y agoWell of course http://www.ai http://www.ai would work. That's no different from http://foo.ai http://foo.ai . http://uz./ http://uz./ serves a 500 error.
- sph 2y agoYou need a dot at the end for it to resolve correctly https://ai https://ai. It’s unreachable anyway
- weird-eye-issue 2y agoThat is cursed
- Natfan 2y agoYou're currently browsing `news.ycombinator.com.`[0]. [0]: https://jvns.ca/blog/2022/09/12/why-do-domain-names-end-with-a-dot-/ https://jvns.ca/blog/2022/09/12/why-do-domain-names-end-with...
- sph 2y agoIt is not, it is for your local resolver to distinguish a top-level domain from a subdomain (i.e. `foo` gets rewritten to `foo.mydomain.com` or `foo.local`) man resolv.conf, read up on search domains and the ndots option
- banana_giraffe 2y agohttps://xn--l1acc./ https://xn--l1acc./ and https://uz./ https://uz./ connect, though there's a cert issues in both cases.