https://content-partnersbadge-pa.googleapis.com/static/proxy.html?usegapi=1&jsh=m%3B%2F_%2Fscs%2Fapps-static%2F_%2Fjs%2Fk%3Doz.gapi.en_US.8RodOolT8JU.O%2Fam%3DwQ%2Frt%3Dj%2Fd%3D1%2Frs%3DAGLTcCOIo0_JuSGflMsDv4KwJaDwWj-arA%2Fm%3D__features__#parent=https%3A%2F%2Fwww.gstatic.com&rpctoken=448393917

Category: CDN Resource API Endpoint

Keywords: error found thats found1 server requested


Last fetched: 2019-04-15T12:20:48.549386+00:00

HTTP status: 5 Sub-resource URL


TLS/SSL configuration report

TLS score
C
Grade capped at C
Grade capped due to 64-bit cipher (IDEA, RC2, DES or 3DES)

See full SSL/TLS security report for content-partnersbadge-pa.googleapis.com

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.

    Read more...

  • X-XSS-Protection: 1; mode=block

    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.

    Read more...

  • Server: ESF

    Announces web server software and optionally version details.

    Read more...

Pages loading this URL

Fully automated RESTful API is now available. Subscribe for your free trial today!