I cannot say this conclusively but it appears that the site had been defaced by a hacker and has since been taken offline. [Update: The site is back up using new hosting so my reply is no longer relevant.]
Zone-H creates a mirror/archive of a site after someone reports that a defacement or other hack to a site has occurred.
Zone-H reports:
http://www.zone-h.org/mirror/id/15878149 Notified by: SA3D HaCk3D
Domain:
http://bitlotto.com/cgi-sys/suspendedpage.cgi IP address: 199.58.186.44
System: LinuxWeb server: Apache
Notifier stats
This is a CACHE (mirror) page of the site when it was saved by our robot on 2011-11-26 17:04:14
I see that BitLotto.com's domain registrar lists that the BitLotto domain uses BitcoinWebHost for DNS.
There is no A record for BitLotto on either nameserver:
nameserver: ns1.bitcoinwebhost.com
nameserver: ns2.bitcoinwebhost.com
So it isn't just that the webserver isn't responding but that access to the site has been either explicitly disabled or there is a configuration error.
This all is consistent with there having been a security breach and then the hosting company (possibly by request of the site owner) disabled the site.
I can't find it now but the question of "what if BitLotto site gets hacked" had been asked and the response from BitLotto was that the wallet is not even on the same host as the website. There still are problems that could happen (e.g., where an attacker changes the bitcoin address to one controlled by the attacker and subsequent bitlotto wagers are lost) but the lotto entries purchased prior to the attack would still be controlled by BitLotto. Oftentimes the report to Zone-H is filed by the hacker -- in this case, apparently SA3D HaCk3D. There appears to be thousands of site defacements each month by this attacker so I would think it less than likely that the content of the BitLotto site was altered to scam those attempting to purchase BitLotto entries.
Unfortunately, there is no notice about an attack or other explanation for the outage here nor on the site's Twitter feed:
http://twitter.com/BitLotto Hopefully a full explanation is forthcoming -- from both BitLotto as well as from BitcoinWebHost.
[edited]