nowwwSo you might be wondering what this post is all about with such a weird title. Basically, me being the little web developer that I am, I’m pushing myself to learn new standards and actually use these standards as I further my knowledge of web design. I mean this both in the visual sense as well as the behind the scenes or backbone coding sense.

I strive to apply standards to everything that I have on this site. It is actually evolving as I learn more and understand how to implement some of the standards that I’ve learned. I know by now you’re wondering what this has to do with No-WWW and, so I’ll break it down for you..

I just recently (as in today) did some server side work to force a domain redirect from to This is in theory how most all websites should handle the www sub-domain. The reason being that it is redundant for most all websites. For example, with my website I have no other sub-domains served to the public. When visiting or browsing this site you will never need to enter a sub-domain to navigate this site. Therefore the use of ‘www’ is understood. This is how the majority of public websites on the Internet are today. The exceptional websites would be sites such as yahoo, google, ms, etc…that actually take advantage of sub-domains such as ‘’ or ‘’. However, it is still understood that when visiting for instance that the ‘www’ can be left off. If you’ve ever seen websites do this in the past then it was probably because they had a crafty URI and wanted it to stand out by removing the ‘www’ automatically.

If you would like to learn more about No-WWW then visit their website at You can also test your site there to see what class level your site is in. The most common is Class A, but the small editing that I did moved mine to a Class B. Class A means that the site is accessible with and without the www, however, it does not redirect to the non-www URI (or from the non-www to the www for that matter). Class B means that the site does redirect to the non-www from the www sub-domain. Class C (which is very strict, but according to standards is how websites should be designed) means that visiting a site with ‘www’ at the beginning will get you a 404 file not found page, but non-www version will pull up the site perfectly find. If you want to see one of these sites in the exact opposite form then try visiting the following links (their implementation is the strict like Class C, however they have the allowed sub-domain and blocked sub-domain backwards.): <- Should work, implemented wrong <- Works for them

If you have any questions about this or any other standards (this one being supported less than most) then please do ask questions or feel free to look into their site and find a bit more information!

3 thoughts on “ and”

  1. Opera 9.50 Opera 9.50 GNU/Linux x64 GNU/Linux x64
    Opera/9.50 (X11; Linux x86_64; U; en)

    I think I would find Class C kind of annoying since I tend to use/not use www kind of interchangeably, haha.

  2. Opera 9.50 Opera 9.50 GNU/Linux x64 GNU/Linux x64
    Opera/9.50 (X11; Linux x86_64; U; en)

    I agree. I think the Class C level is a bit ridiculous. I kind of like the Class B though. My domain works with and without the www, just like a Class A would. For my case though, is just more memorable.

Leave a Reply

Your email address will not be published. Required fields are marked *