root# ping btc-e.com
PING btc-e.com (74.208.15.160): 56 data bytes
64 bytes from 74.208.15.160: seq=0 ttl=55 time=175.390 ms
64 bytes from 74.208.15.160: seq=1 ttl=55 time=172.723 ms
64 bytes from 74.208.15.160: seq=2 ttl=55 time=170.876 ms
74.208.15.160/index.html - check this
PING btc-e.com (74.208.15.160): 56 data bytes
64 bytes from 74.208.15.160: seq=0 ttl=55 time=175.390 ms
64 bytes from 74.208.15.160: seq=1 ttl=55 time=172.723 ms
64 bytes from 74.208.15.160: seq=2 ttl=55 time=170.876 ms
74.208.15.160/index.html - check this
Nice try?
92%%%ping btc-e.com
PING btc-e.com (104.23.132.83) 56(84) bytes of data.
Ever heard of DNS propagation?
Yup, however, if this person is suggestion it's been seized, the seizure probably would have taken place more than 48 hours ago, and the propagation would be close to if not completed already.
Or it could be that he is trying to panic people by spreading misinformation.
How about this, tell me the DNS server he used, and I can check directly against it
