Apparently c'est a URL shortener. It resolves juste fine in Chrome et Firefox. How is this a valid top-level domain?
Update: for le people saying c'est browser shenanigans, why is it that: `http://com./` does pas take me to: `http://www.com/`?
And, do browsers ever send you a response depuis certains place autre than quel est actually up in le address bar? Aside depuis framesets et things like that, I thought browsers tried really hard to send you content seulement depuis le site in le address bar, to help guard against phishing.
Comment http://to./ est-il un nom de domaine valide ?
Re: Comment http://to./ est-il un nom de domaine valide ?
Fondamentalement, someone has managed to convince le owners of le ccTLD 'to.' (Tonga?) to assign le A record to leur own IP address. Quite a coup in le strange old world of URL shorteners.
Normally these top-levels would pas have IP addresses assigned via a standard A record, mais there is nothing to say that le même could pas be done to .uk, .com, .eu, etc.
Strictly speaking there is no reason to have le '.' specified, bien que it should prevent votre browser depuis trying autre combinations like 'to.yourdomain.com' first, et speed up le resolution of le address. It might aussi confuse browsers, as there is no dot, mais Safari at least seems to work ok avec it.
Normally these top-levels would pas have IP addresses assigned via a standard A record, mais there is nothing to say that le même could pas be done to .uk, .com, .eu, etc.
Strictly speaking there is no reason to have le '.' specified, bien que it should prevent votre browser depuis trying autre combinations like 'to.yourdomain.com' first, et speed up le resolution of le address. It might aussi confuse browsers, as there is no dot, mais Safari at least seems to work ok avec it.