# domain.com vs www.domain.com
**URL:** https://boards.straightdope.com/t/domain-com-vs-www-domain-com/375303
**Category:** Factual Questions
**Created:** [October 4, 2006, 8:44pm UTC](https://boards.straightdope.com/t/domain-com-vs-www-domain-com/375303 "2006-10-04T20:44:20Z")
**Posts on this page:** 6
**Page:** 1
### Author:  [@Will\_Repair](https://boards.straightdope.com/u/Will_Repair)
#### Post date: [October 4, 2006, 8:44pm UTC](https://boards.straightdope.com/t/domain-com-vs-www-domain-com/375303/1 "2006-10-04T20:44:20Z")
What’s broken when a server requires the www before the domain name.
Example:
[pinballmachine.com](http://pinballmachine.com) does not work
[www.pinballmachine.com](http://www.pinballmachine.com) works
(I think I fixed one by complaining.
[newark.com](http://newark.com) now works)
---
### Author:  [@friedo](https://boards.straightdope.com/u/friedo)
#### Post date: [October 4, 2006, 9:10pm UTC](https://boards.straightdope.com/t/domain-com-vs-www-domain-com/375303/2 "2006-10-04T21:10:02Z")
Nothing is broken. It just means that it isn’t configured how you want.
Either the IPs for [www.domain.com](http://www.domain.com) and [domain.com](http://domain.com) are set to different values, or the web server is not configured to serve the same content for both domains.
You can check the former by doing an nslookup or ping of the domains and seeing what IPs they resolve to. If they’re the same, then the latter is probably the cause.
---
### Author:  [@GorillaMan](https://boards.straightdope.com/u/GorillaMan)
#### Post date: [October 4, 2006, 9:14pm UTC](https://boards.straightdope.com/t/domain-com-vs-www-domain-com/375303/3 "2006-10-04T21:14:36Z")
The www. prefix indicating a web server (as opposed to an ftp server, for example) is just a convention. Traces from before the convention was established do exist: web.mit.edu still functions, mirroring www.mit.edu
---
### Author:  [@Chronos](https://boards.straightdope.com/u/Chronos)
#### Post date: [October 5, 2006, 11:29pm UTC](https://boards.straightdope.com/t/domain-com-vs-www-domain-com/375303/4 "2006-10-05T23:29:09Z")
The Internet is used for many different things, and the Web was not always the biggest (or even one of them at all). So MIT would have, for instance, a server for FTP, and a server for Gopher, and a server for SMTP e-mail, and so on. These were probably called something like ftp.mit.edu, gopher.mit.edu, smtp.mit.edu, and so on. When the Web came on the scene, they added a new server for that, too, and called it web.mit.edu (MIT was, of course, an early adopter, and at the time they set that server up, “www” wasn’t yet standard). If you just tried to access mit.edu , it wouldn’t know which of those servers you wanted. Nowadays, the Web is the most common use for the Internet, so most sites are configured to assume that you want the webserver, and [site.com](http://site.com) will take you to the same place as [www.site.com](http://www.site.com) . But depending on the site, it might not be wrong to assume the FTP server as the default, or something else, or nothing at all. In that case, going to [site.com](http://site.com) without the www would give you an error message.
---
### Author:  [@GorillaMan](https://boards.straightdope.com/u/GorillaMan)
#### Post date: [October 5, 2006, 11:38pm UTC](https://boards.straightdope.com/t/domain-com-vs-www-domain-com/375303/5 "2006-10-05T23:38:07Z")
> [@Chronos](#):
>
> But depending on the site, it might not be wrong to assume the FTP server as the default, or something else, or nothing at all. In that case, going to [site.com](http://site.com) without the www would give you an error message.
Sadly, many sites where it would be perfectly logical to forward the request to the www. site do not do so. One I’ve encountered recently - [dfes.gov.uk](http://dfes.gov.uk) fails to connect to [www.dfes.gov.uk](http://www.dfes.gov.uk), and the added problem here is that the suffix has to be typed manually, rather than relying on Firefox to add the ‘www.’ and ‘.com’ to something typed into the address field.
---
### Author:  [@SuperNelson](https://boards.straightdope.com/u/SuperNelson)
#### Post date: [October 6, 2006, 12:02am UTC](https://boards.straightdope.com/t/domain-com-vs-www-domain-com/375303/6 "2006-10-06T00:02:59Z")
Here’s another relevant example. [www.straightdope.com](http://www.straightdope.com) goes one place, while [boards.straightdope.com](http://boards.straightdope.com) goes another. For all I know, there’s a [mail.straightdope.com](http://mail.straightdope.com) out there as well. [straightdope.com](http://straightdope.com) goes to the same place as [www.straightdope.com](http://www.straightdope.com), but only because somebody took the care to define it that way.