This won't work because to me this is similar in concept to URL shorteners. The difference being in the shortening algorithm and the use of expensive domains.

This won't work because to me this is similar in concept to URL shorteners. The difference being in the shortening algorithm and the use of expensive domains. So for example with current shorteners you have: http://shorturl.com/{algorithm http://shorturl.com/{algorithm for unique URL goes here} In the above case using a browser plug in can also eliminate any server side resolution of domains. With this proof of concept: http://{algorithm http://{algorithm for unique URL goes here}.com ... Except the implementation costs $ if it is to be accepted... And to be accepted it needs to have a benefit that isn't solved by URL shorteners.