Topic: ** Official ** Cryptsy funds are safe and secure - page 7. (Read 11087 times)
Thank you for the update
Hmmmmmmmmmm....
Mine is still pointing to secure.4rx.com over here. Interesting that you are getting something different.
Hmmmmmmmmmm....
Chrome just gave me a warning message when I tried to access cryptsy stating that the server was identified as secure.4rx.com. What's the deal with that?
SSL is down
SSL requests not supported for www.cryptsy.com
The site is not configured with SSL support.
It is not down, it is serving an invalid SSL certificate issued to an unrelated entity (secure.4rx.com) which might indicate a quite serious man-in-the-middle attack
Code:
www.cryptsy.com resolves to IP 166.78.0.180 Rackspace Hosting, Texas
secure.4rx.com resolves to IP 199.83.132.157 Incapsula, Delaware
Nobody should try to login even if the site comes back until this is fully resolved
UPDATE: now www.cryptsy.com also resolves to IP 199.83.132.157 Incapsula, Delaware
Seems like Incapsula.com offers some DDoS protection and general web security and cryptsy.com just put them in front of their site? So at least not a MITM attack but possibly just some Incapsula fuckup
Please confirm BitJohn
still wading through details Ill have vern give the whole write up once the madness is over for now just wait for an official we are up before logging in
Chrome just gave me a warning message when I tried to access cryptsy stating that the server was identified as secure.4rx.com. What's the deal with that?
SSL is down
SSL requests not supported for www.cryptsy.com
The site is not configured with SSL support.
It is not down, it is serving an invalid SSL certificate issued to an unrelated entity (secure.4rx.com) which might indicate a quite serious man-in-the-middle attack
Code:
www.cryptsy.com resolves to IP 166.78.0.180 Rackspace Hosting, Texas
secure.4rx.com resolves to IP 199.83.132.157 Incapsula, Delaware
Nobody should try to login even if the site comes back until this is fully resolved
UPDATE EDIT: now www.cryptsy.com resolves to IP 199.83.128.157, also Incapsula, North Carolina
Seems like Incapsula.com offers some DDoS protection and general web security and cryptsy.com just put them in front of their site? So at least not a MITM attack but possibly just some Incapsula fuckup
Please confirm BitJohn
Chrome just gave me a warning message when I tried to access cryptsy stating that the server was identified as secure.4rx.com. What's the deal with that?
SSL is down
SSL requests not supported for www.cryptsy.com
The site is not configured with SSL support.
It is not down, it is serving an invalid SSL certificate issued to an unrelated entity (secure.4rx.com) which might indicate a quite serious man-in-the-middle attack
Code:
www.cryptsy.com resolves to IP 166.78.0.180 Rackspace Hosting, Texas
secure.4rx.com resolves to IP 199.83.132.157 Incapsula, Delaware
Nobody should try to login even if the site comes back until this is fully resolved
Yes please wait until we confirm that our servers are back online.
Can you tell us who your service provider is?
Chrome just gave me a warning message when I tried to access cryptsy stating that the server was identified as secure.4rx.com. What's the deal with that?
SSL is down
SSL requests not supported for www.cryptsy.com
The site is not configured with SSL support.
It is not down, it is serving an invalid SSL certificate issued to an unrelated entity (secure.4rx.com) which might indicate a quite serious man-in-the-middle attack
Code:
www.cryptsy.com resolves to IP 166.78.0.180 Rackspace Hosting, Texas
secure.4rx.com resolves to IP 199.83.132.157 Incapsula, Delaware
Nobody should try to login even if the site comes back until this is fully resolved
Yes please wait until we confirm that our servers are back online.
I can confirm invalid SSL certificate. I'm getting SSL cert for *.professionalperformanceonline.nl -- definitely not going to log in.
Expect another hour of downtime attack seems to be subsiding we are using the downtime to enable additional protections to prevent this in the future. Sorry for the delay. Some folks just want to see the world burn.
have you tried the ddos protect implementation in your htaccess file? i think apache comes with a template and tutorial that shows you how to do it.
Waiting for you to come back on
actually that does work versus botnets. if you recall trollzilla, my ddos protect stopped a flood of 1100+ chinese ips at my website. however they still chewed up 430 gb bandwidth in an hour attempting to flood the server. it worked and my account was cancelled.
Chrome just gave me a warning message when I tried to access cryptsy stating that the server was identified as secure.4rx.com. What's the deal with that?
SSL is down
SSL requests not supported for www.cryptsy.com
The site is not configured with SSL support.
It is not down, it is serving an invalid SSL certificate issued to an unrelated entity (secure.4rx.com) which might indicate a quite serious man-in-the-middle attack
Code:
www.cryptsy.com resolves to IP 166.78.0.180 Rackspace Hosting, Texas
secure.4rx.com resolves to IP 199.83.132.157 Incapsula, Delaware
Nobody should try to login even if the site comes back until this is fully resolved
Chrome just gave me a warning message when I tried to access cryptsy stating that the server was identified as secure.4rx.com. What's the deal with that?
SSL is down
SSL requests not supported for www.cryptsy.com
The site is not configured with SSL support.
Expect another hour of downtime attack seems to be subsiding we are using the downtime to enable additional protections to prevent this in the future. Sorry for the delay. Some folks just want to see the world burn.
have you tried the ddos protect implementation in your htaccess file? i think apache comes with a template and tutorial that shows you how to do it.
Waiting for you to come back on
its some kind of pharmaceutical phishing website
Good thing I didn't go on to the site then...
Chrome just gave me a warning message when I tried to access cryptsy stating that the server was identified as secure.4rx.com. What's the deal with that?
Yeah I wouldn't log in until this question gets answered.Yes I just got the same thing. I cannot find anything on 4rx.
That sounds like a smart way to trick users into putting their data through another source.
its some kind of pharmaceutical phishing website
I will announce when the site is fully operational. Again your funds and accounts are fine just a nice DDOS attack. We are implementing additional features with this downtime to deter this attack in the future.
Chrome just gave me a warning message when I tried to access cryptsy stating that the server was identified as secure.4rx.com. What's the deal with that?
Yeah I wouldn't log in until this question gets answered.Yes I just got the same thing. I cannot find anything on 4rx.
That sounds like a smart way to trick users into putting their data through another source.
Expect another hour of downtime attack seems to be subsiding we are using the downtime to enable additional protections to prevent this in the future. Sorry for the delay. Some folks just want to see the world burn.
have you tried the ddos protect implementation in your htaccess file? i think apache comes with a template and tutorial that shows you how to do it.
Expect another hour of downtime attack seems to be subsiding we are using the downtime to enable additional protections to prevent this in the future. Sorry for the delay. Some folks just want to see the world burn.
Chrome just gave me a warning message when I tried to access cryptsy stating that the server was identified as secure.4rx.com. What's the deal with that?
Yeah I wouldn't log in until this question gets answered. Jump to: