At this san you see what is insecure there: -https://asafaweb.com/Scan?Url=htyzs.cn
Custom errors: Fail
Requested URL: -http://htyzs.cn/trace.axd | Response URL: -http://htyzs.cn/trace.axd | Page title: XXXXXXXX | HTTP status code: 403 (Forbidden) | Response size: 1,867 bytes | Duration: 264 ms
Overview
Custom errors are used to ensure that internal error messages are not exposed to end users. Instead, a custom error message should be returned which provides a friendlier user experience and keeps potentially sensitive internal implementation information away from public view.
Excessive headers: Warning
Requested URL: -http://htyzs.cn/ | Response URL: -http://htyzs.cn/ | Page title: | HTTP status code: 200 (OK) | Response size: 22,057 bytes (gzip'd) | Duration: 2,473 ms
Overview
By default, excessive information about the server and frameworks used by an ASP.NET application are returned in the response headers. These headers can be used to help identify security flaws which may exist as a result of the choice of technology exposed in these headers.
Result
The address you entered is unnecessarily exposing the following response headers which divulge its choice of web platform:
Server: Microsoft-IIS/7.5
X-Powered-By: UrlRewriter.NET 2.0.0, ASP.NET
X-AspNet-Version: 2.0.50727
Result
It looks like custom errors are not correctly configured as the requested URL contains the heading "Server Error in".
Custom errors are easy to enable, just configure the web.config to ensure the mode is either "On" or "RemoteOnly" and ensure there is a valid "defaultRedirect" defined for a custom error page as follows:
<customErrors mode="RemoteOnly" defaultRedirect="~/Error" />
Clickjacking: Warning
Requested URL: -http://htyzs.cn/ | Response URL: -http://htyzs.cn/ | Page title: | HTTP status code: 200 (OK) | Response size: 22,057 bytes (gzip'd) | Duration: 2,473 ms
Overview
Websites are at risk of a clickjacking attack when they allow content to be embedded within a frame. An attacker may use this risk to invisibly load the target website into their own site and trick users into clicking on links which they never intended to. An "X-Frame-Options" header should be sent by the server to either deny framing of content, only allow it from the same origin or allow it from a trusted URIs.
Result
It doesn't look like an X-Frame-Options header was returned from the server which means that this website could be at risk of a clickjacking attack. Add a header to explicitly describe the acceptable framing practices (if any) for this site.
polonus