https://www.google.co.uk/pagead/1p-user-list/996994227/?random=1590185741363&cv=9&fst=1590184800000&num=1&guid=ON&u_h=600&u_w=800&u_ah=600&u_aw=800&u_cd=32&u_his=1&u_tz=0&u_java=false&u_nplug=0&u_nmime=0&frm=0&url=https%3A%2F%2Fwww.axa.be%2Fab%2FNL%2Fparticulieren%2FPages%2FHomeB.aspx&tiba=AXA+-+verzekeringen+-+overzicht+van+ons+aanbod+voor+particulieren&fmt=3&is_vtc=1&random=1954470418&resp=GooglemKTybQhCsO&rmt_tld=1&ipr=y

Category: Search Engine Shopping

Keywords: data play learn share store google people policy search account collect cookies example privacy started personal services including advertising information


Last fetched: 2020-05-22T22:15:45.741414+00:00

HTTP status: 5 Sub-resource URL


TLS/SSL configuration report

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

See full SSL/TLS security report for www.google.co.uk

Advanced trackers

Advanced user tracking and fingerprinting techniques are used by websites to bypass privacy protection in web browsers and increase tracking persistence.

b'GIF8' … b'\x01\x00\x01\x00'

Security-related HTTP headers

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

    Read more...

Content Security Policy

  • script-src 'none'; object-src 'none'

Want second opinion? Try Google CSP Evaluator.

Sub-resources

Parent pages

Parent pages loading this resource.
Fully automated RESTful API is now available. Subscribe for your free trial today!