Topic: BTC-e hacked ?? - page 101. (Read 199718 times)
Even I am unable to see it. Anyways - what does this mean for people who had legitimate crypto earnings/savings ? If US has seized it.
I am not seeing that page--at least not yet. Are you joking?
This is no joke, clear your (browser) cache and then go to
http://btc-e.com/banner.png
(Make sure your browser doesn't redirect to the old https page)
I don't see the seizure page yet, but just read an article from the fincen site and a quote from it was FinCEN acted in coordination with law enforcement’s seizure of BTC-e and Vinnik’s arrest. The Internal Revenue Service-Criminal Investigation Division, Federal Bureau of Investigation, United States Secret Service, and Homeland Security Investigations conducted the criminal investigation.
I am not seeing that page--at least not yet. Are you joking?
Shitty paint job didn't give it away?
I am not seeing that page--at least not yet. Are you joking?
Bye bye btc-e :-(
I will never eat another hamburger
Trolls are everywhere
Why do you keep saying this? Do you have the correct info to ease the trolls?
It's called denial, people will try to convince themselves that nothing is wrong regardless of the facts put in front of them.
Sorry for your loss potent, but spreading false hope at this point isn't helping anyone.
Bye bye btc-e :-(
Trolls are everywhere
Why do you keep saying this? Do you have the correct info to ease the trolls?
Trolls are everywhere
Browsers are probably pinned to https so will try to hit it at port 443 by default. But if you use curl or something raw like telnet to port 80 from a command line, you'll see the dreaded "NinjaVideo.net" domain which you might remember from Silk Road and others. Hit that URL and you'll see the banner.
$ telnet btc-e.com 80
Trying 74.208.15.160...
Connected to btc-e.com.
Escape character is '^]'.
HEAD / HTTP/1.0
HTTP/1.1 302 Found
Date: Fri, 28 Jul 2017 21:40:35 GMT
Server: Apache
Location: http://NinjaVideo.net/index.html
Vary: Accept-Encoding
Connection: close
Content-Type: text/html; charset=iso-8859-1
$ telnet btc-e.com 80
Trying 74.208.15.160...
Connected to btc-e.com.
Escape character is '^]'.
HEAD / HTTP/1.0
HTTP/1.1 302 Found
Date: Fri, 28 Jul 2017 21:40:35 GMT
Server: Apache
Location: http://NinjaVideo.net/index.html
Vary: Accept-Encoding
Connection: close
Content-Type: text/html; charset=iso-8859-1
Oh dear, he's right ... that's not very good
Getting those mtgox flashbacks
Browsers are probably pinned to https so will try to hit it at port 443 by default. But if you use curl or something raw like telnet to port 80 from a command line, you'll see the dreaded "NinjaVideo.net" domain which you might remember from Silk Road and others. Hit that URL and you'll see the banner.
$ telnet btc-e.com 80
Trying 74.208.15.160...
Connected to btc-e.com.
Escape character is '^]'.
HEAD / HTTP/1.0
HTTP/1.1 302 Found
Date: Fri, 28 Jul 2017 21:40:35 GMT
Server: Apache
Location: http://NinjaVideo.net/index.html
Vary: Accept-Encoding
Connection: close
Content-Type: text/html; charset=iso-8859-1
$ telnet btc-e.com 80
Trying 74.208.15.160...
Connected to btc-e.com.
Escape character is '^]'.
HEAD / HTTP/1.0
HTTP/1.1 302 Found
Date: Fri, 28 Jul 2017 21:40:35 GMT
Server: Apache
Location: http://NinjaVideo.net/index.html
Vary: Accept-Encoding
Connection: close
Content-Type: text/html; charset=iso-8859-1
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
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?
Is that the same as a fabricated coffin?
You can check dns propagation (ip changes) at https://www.whatsmydns.net/#A/btc-e.com
All right then, I fully retract my previous responses
Guess we'll have to wait.
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?
Is that the same as a fabricated coffin?
You can check dns propagation (ip changes) at https://www.whatsmydns.net/#A/btc-e.com
what about https://btc-e.nz/ domain?
Full of trolls here.
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
No fabricated coffins just st8 cremation
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?
Is that the same as a fabricated coffin?
Jump to: