It looks like we made a bit of a mess of the DNS server. It is pointing to the wrong ip address which is loading the incorrect site. We are working to resolve this as quickly as possible. DNS changes take a bit of time to propagate.
UPDATE: This problem is now resolving.
We became notified of the issue a few minutes before the site started resolving to another IP address. The IP address was our ip address, but ending in .0, instead of .176. The rest of the numbers were the same, so it was not a malicious attack- simply a problem in our development in adding the wrong IP address for the DNS server.
Things are looking ok now. You may need to restart your comp if it is still resolving incorrectly.
Shannon