Usually, companies redirect "domain.com" to "www.domain.com", but that's not a required standard, and it's not always followed.
While you do most of your internet interaction through a web browser, there's other stuff on the Internet besides web pages. While nearly all of this is wrapped up in web pages today, there's still FTP, Telnet, Gopher, news servers, mail servers, SIP (voice over IP) and a few other fun protocols. Anyone remember Finger?
Since all of these services were different, each had a unique hostname assigned to it by convention: you could always count on finding an FTP server at ftp.netscape.net, their gopher server was gopher.netscape.net, and so on.
Of course, in the 80's and early 90's, a server computer cost more than a luxury car. So www.company.com and ftp.company.com probably pointed to the same place, since the entire company would have just a single Internet server.
Then something big happened. In the 90's: server computers got cheaper, and expensive mainframes and minicomputers gave way to commodity systems that cost less than a weekend at Disneyland. Any desktop machine could be a web server, thanks to free Linux, and people started building out their server farms with multiple PC's. Today, you can build a web server for less than $100, and store it in a soda can (hopefully an empty one.)
So the Internet exploded: Facebook today gets more hits in one day than the entirety of the Internet did in 1995. So we use more than one server to handle web requests: entire groups of computers these days will respond to a single host name, thanks to the magic of load balancing, and the Internet seems to have settled on a standard of doing all of our Internet work through a web browser.
What this means is that www.domain.com is no longer on the same computer as ftp.domain.com. So where do we send requests to the "naked" domain of "domain.com"?
Today, people think of "the web" as "the Internet", and so they use a browser for everything they do. That's convenient, since having separate programs for downloading files, reading news, checking email, reading blogs, and checking the weather can be a real pain. It also brings up questions like "why do we have www in front of web pages?" This means that we can usually get away with assuming that a request for a naked domain is the same as a request for that domain's www server.
So now, most companies will respond to naked requests by redirecting "domain.com" to "www.domain.com". However, there's no standard that requires it, and you'll frequently find that small domains hosted on server farms won't respond to naked domains that way. (For example, one hosting company I used dropped users to the hosting company's landing page when someone typed just "mydomain.com".)
Luckily for the lazy among us, there's a keyboard shortcut in most browsers that lets you shorten the process even more: just type "company", press Control-Enter, and the browser expands it to "www.company.com".
27
See here: http://no-www.org/
– gparyani – 2014-01-07T02:53:47.17327
See here: http://www.yes-www.org/
– Michael Hampton – 2014-01-07T17:14:56.24327
Nah, see here: extra-www.org
– chris-l – 2014-01-07T17:53:25.273That might be a question regarding user experience
– Val – 2014-01-07T18:16:00.553I've always been amused that the acronym "www" requires far more syllables to pronounce (at least in English) than the entire phrase it replaces. At least it is easy to type... :-) – RBerteig – 2014-01-07T19:22:56.277
@gparyani It is interesting that www.no-www.org works!
– Nazar554 – 2014-01-07T20:22:18.773@Nazar554 It's a redirect to the non-www version. – gparyani – 2014-01-07T20:43:22.753
I'm pretty sure that an extra-extra-www.org site will spring up soon (e.g.
www.www.www.example.com
). – gparyani – 2014-01-07T20:46:56.283@RBerteig I know some people who pronounce it "triple-U" for that reason. Not sure if that'll ever catch on... – Darrel Hoffman – 2014-01-08T01:32:53.110
@DarrelHoffman I generally never say it at all because the convention seems to be these days that with or without it leads to the same place. – 287352 – 2014-01-08T01:48:49.227
1dub-dub-dub was common for a while - what happened to that? – Phil – 2014-01-08T08:32:03.343
1
try http://vim.org vs. http://www.vim.org
– sehe – 2014-01-08T10:01:39.370@sehe I get redirected to the same site with a black kid holding a drill. – Celeritas – 2014-01-08T10:07:05.920
@Celeritas the first link is dead. If you get redirected, it's your browser doing you "favours" – sehe – 2014-01-08T10:07:58.143
@sehe isn't this bizarre, in Firefox the first link USUALLY works if I click it with the middle mouse button and open it in a new tab, otherwise it doesn't. It also works if I right click on it and select new tab. – Celeritas – 2014-01-08T10:16:03.833
@Celeritas oh joy. Go file some bugs at mozilla. Really, I suppose it could be construed a security issue to open a different link from what the user clicked. Meh. – sehe – 2014-01-08T10:22:20.193
4@MichaelHampton I love that yes-www seems to be saying we should use www to remind people of the difference between hypertext transfer protocol and other internet protocols. It's a shame, really, that no one ever thought to just put http in web URLs just to make it clear ... ;) – StackExchange What The Heck – 2014-01-08T10:25:12.290
2
@chris-l: Nice to see that they redirect www.extra-www.org and extra-www.org to www.www.extra-www.org :-)
– Reinstate Monica - M. Schröder – 2014-01-10T11:48:47.393@DarrelHoffman I usually pronounce it woo-woo-woo and that is usually understood in context. – RBerteig – 2014-01-13T19:32:17.957