polonus
1
See: http://www.domxssscanner.com/scan?url=http%3A%2F%2F204.232.149.59%2Fshutdown.htm
giving: http://204.232.149.59/s_code.js
Re: http://www.domxssscanner.com/scan?url=http%3A%2F%2F204.232.149.59
Netcraft isn’t too happy with site risks involved: http://toolbar.netcraft.com/site_report?url=http://204.232.149.59
Does not resolve: -http://2014storeoutletonlinescoach.com/
Again GoDaddy involved :o → http://toolbar.netcraft.com/site_report?url=http%3A%2F%2F2014storeoutletonlinescoach.com%2F
While the original site is being kept up by Akamai Amsterdam: http://toolbar.netcraft.com/site_report?url=http://www.coach.com
with 7 trackers on!
The server they tried to compromise was a Microsoft IIS httpd 6.0
Potentially risky methods: TRACE Targetname = Webname = 242322-WEB1 Meta Data Source Key. MS:Windows.
Custom errors:Fail 2 Warnings: https://asafaweb.com/Scan?Url=2014storeoutletonlinescoach.com
Time to do a DNS scan → secureserver dot net issues: http://www.dnsinspect.com/2014storeoutletonlinescoach.com/1441620737
All this could be established through 100% third party cold reconnaissance scanning - conclusion: issues by sort of “elastic tape” hosting 
that must be remedied/backed-up by partners like Akamai’s.
polonus (volunteer website security analyst and website error-hunter)
