$ nslookup bitmit.net
bitmit.net canonical name = dns-blocked.sonic.net.
$ ping bitmit.net
PING dns-blocked.sonic.net (18.104.22.168) 56(84) bytes of data.
64 bytes from dns-blocked.tld (22.214.171.124): icmp_req=1 ttl=58 time=29.2 ms
64 bytes from dns-blocked.tld (126.96.36.199): icmp_req=2 ttl=58 time=32.3 ms
64 bytes from dns-blocked.tld (188.8.131.52): icmp_req=3 ttl=58 time=30.9 ms
As you can see, when looking up bitmit.net using the Sonic.net DNS resolvers you will get redirected to dns-blocked.sonic.net
If you really want to access the site bitmit.net you can do so by using some other DNS server (such as Google DNS 184.108.40.206):
> server 220.127.116.11
Default server: 18.104.22.168
$ ping 22.214.171.124
PING 126.96.36.199 (188.8.131.52) 56(84) bytes of data.
64 bytes from 184.108.40.206: icmp_req=4 ttl=56 time=28.6 ms
64 bytes from 220.127.116.11: icmp_req=5 ttl=56 time=26.8 ms
64 bytes from 18.104.22.168: icmp_req=6 ttl=56 time=24.9 ms
As you can see from the ping response, the access is not blocked but I'm not curious enough to see what malware that website may contain to actually connect with a browser.--
Got some spare cpu cycles ? Join Team Helix or Team Starfire!