Category: Uncategorized

Keywords: bkxr jfif zvv8 woq[x7uvt f0et9pzn1msvtvu 12arabqruqbd?@t2424 f[h?xygj?1^f4vum`l^u 6l`siu7u^zuw[la?ynmnk:z `fb6jpvz7c:ufvwlrh8ezzwie4eec: _jsjjtu^m2\o7mvvvzre8?4ql5izv2e tjkukk5_s[8tedkl]i5yinf3mmx[7]riz6zrqzcvst

Last fetched: 2020-10-07T23:27:47.474548+00:00

HTTP status: 5 Sub-resource URL

Security-related HTTP headers

  • X-Content-Type-Options: nosniff

    A non-standard but widely accepted header introduced originally by Microsoft to disable "content sniffing" or heuristic content type discovery in absence or mismatch of a proper HTTP Content-Type declaration, which led to a number of web attacks. In general, presence of the header with its only defined value of nosniff is considered as part of a properly secured HTTP response.


  • Server: sffe

    Announces web server software and optionally version details.


  • X-XSS-Protection: 0

    Controls an Cross-Site Scripting (XSS) filters built into the majority of web browsers. The filter is usually turned on by default anyway, but requirement to set the header to 1 became part of canonical set of "secure" HTTP headers. Over time, vulnerabilities in the "sanitizing" mode filter were found, so 1; mode=block became the recommended value. Some companies decided that they don't really need a browser-side XSS filter to mess with their web services which are XSS-free anyway and they became consciously disabling the XSS filter by setting the header to 0.