https://pix.impdesk.com/csync/bluekai

Category: Uncategorized

Keywords: found


Last fetched: 2018-01-18T19:43:31.731973+00:00

HTTP status: 5 Sub-resource URL


TLS/SSL configuration report

TLS score
F
Grade capped at F
Certificate path cannot be verified to a known root certificate

See full SSL/TLS security report for pix.impdesk.com

Security-related HTTP headers

  • Location: /csync/bluekai?_cc=1

    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="http://pix.impdesk.com/p3p.xml", CP="NOI DSP COR ADM PSAo PSDo OURo SAMo UNRo OTRo BUS COM NAV DEM STA PRE"

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

  • Strict-Transport-Security: max-age=25920000; includeSubDomains

    HTTP Strict Transport Security (HSTS) is an opt-in security enhancement that is specified by a web application through the use of a special response header.

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

  • X-XSS-Protection: 1

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

Sub-resources

Parent pages

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