https://www.google.com/ads/ga-audiences?v=1&aip=1&t=sr&_r=4&tid=UA-18632931-1&cid=467201760.1527351148&jid=972548177&_v=j68&z=196678179

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: 2018-05-26T16:13:23.541495+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 www.google.com

Security-related HTTP headers

  • Location: https://www.google.it/ads/ga-audiences?v=1&aip=1&t=sr&_r=4&tid=UA-18632931-1&cid=467201760.1527351148&jid=972548177&_v=j68&z=196678179&slf_rd=1&random=1469754399

    The HTTP Location header is being returned by a server to redirect the web browser to a new URL of the requested resource. The URL may be relative (/index.html) or absolute (https://example.com).

    Read more...

  • P3P: policyref="https://www.googleadservices.com/pagead/p3p.xml", CP="NOI DEV PSA PSD IVA IVD OTP OUR OTR IND OTC"

    Largely abandoned format for declaring website's privacy policy in machine-readable format. The only reason for many websites to use the header was that old versions of Microsoft Internet Explorer disallowed third-party cookies on websites missing P3P.

    Read more...

  • 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...

  • Server: cafe

    Announces web server software and optionally version details.

    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...

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