If you put 172.67.220.135 in your hosts file as hexbear.net and www.hexbear.net (and your browser hasn't cached the redirect), the site is still running. Accessing the IP directly won't work. So it's just a DNS problem. But it's not good. Hopefully the registrar can reverse it because it looks hacked.
If you put 172.67.220.135 in your hosts file as hexbear.net and www.hexbear.net (and your browser hasn't cached the redirect), the site is still running. Accessing the IP directly won't work. So it's just a DNS problem. But it's not good. Hopefully the registrar can reverse it because it looks hacked.