Loved this one, but also expected https://google or https://google. to resolve. Instead I get an nxdomain, shouldn't it return noerror, since google clearly exists? Will we ever see bare tlds?
For a while, there was a URL shortener running on http://to. Ultimately it was scrapped because browser support was unstable, to say the least. In chrome, you had to add the dot or it would do a Google search, for example.
Edit: Actually, I just checked, and to. still resolves, to 216.74.32.107 to be exact. But if you access it, there's only a default Apache2 "It works" page.
Wouldn't these type of addresses conflict with browser that have "omnibar" feature? e.g. you type "google" to location field and it doesn't go to "https://google." but instead performs web search for "google".
3 comments
[ 4.2 ms ] story [ 19.5 ms ] threadFor a while, there was a URL shortener running on http://to. Ultimately it was scrapped because browser support was unstable, to say the least. In chrome, you had to add the dot or it would do a Google search, for example.
Edit: Actually, I just checked, and to. still resolves, to 216.74.32.107 to be exact. But if you access it, there's only a default Apache2 "It works" page.