https://www.google.com/recaptcha/api2/anchor?ar=1&k=6LdGTYwUAAAAAHpill2IvupH7t4shqRXu1iT3a-x&co=aHR0cHM6Ly9pd2ltLmNvbS5hdTo0NDM.&hl=en&v=NMoy4HgGiLr5NAQaEQa2ho8X&size=invisible&cb=4n89f8pfia9g

Category: Search Engine Clean Browsing

Keywords: data play learn share store using google policy search account collect content example privacy service started personal services including information


Last fetched: 2020-06-30T04:35:53.301620+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.

    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: GSE

    Announces web server software and optionally version details.

    Read more...

Content Security Policy

  • script-src 'nonce-P31Q9RXklZHZICSrgk0mWw' 'unsafe-inline' 'strict-dynamic' https: http: 'unsafe-eval';object-src 'none';base-uri 'self';report-uri https://csp.withgoogle.com/csp/recaptcha/1

Want second opinion? Try Google CSP Evaluator.

Sub-resources

Parent pages

Parent pages loading this resource.