Category: Cloud Service/Hosting

Keywords: data dont uses those using google rights account changes content license privacy service policies services software available permitted additional information

Last fetched: 2019-10-02T21:03:22.187880+00:00

HTTP status: 5 Sub-resource URL

Security-related HTTP headers

  • Server: ESF

    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.


Content Security Policy

  • script-src 'report-sample' 'nonce-6Gsbx3v1S84yM7lL8QlA1g' 'unsafe-inline' 'strict-dynamic' https: http: 'unsafe-eval';object-src 'none';base-uri 'self';report-uri /o/cspreport

Want second opinion? Try Google CSP Evaluator.


Parent pages

Parent pages loading this resource.