That's an error condition I've never seen before; that page only appears when no corresponding virtual server can be found (leftover from when I used to host friends' websites, a very long time ago), but I'm not sure what would cause it to be displayed without fuzzing the domain name. If the application got overloaded and fell over and died, it should've thrown a 50x error of some sort. Thank you for pointing it out! I'll look into it :) It was already back up when I checked, so I guess whatever happened auto-recovered (hopefully it did that quickly).
