https://st.hybrid.ai/match?id=122&vid=00fdeb21-2318-432f-aaa9-b5ac38a6c108

Category: Offline

Keywords:


Last fetched: 2018-08-20T14:09:33.791096+00:00

HTTP status: 5 Sub-resource URL


TLS/SSL configuration report

TLS score
A

See full SSL/TLS security report for st.hybrid.ai

Security-related HTTP headers

  • Access-Control-Allow-Origin: *

    Controls origins (websites) that are allowed to load data from this web service over JavaScript-based APIs as part of Cross-Origin Resource Sharing (CORS) standard. By default, a web browser will refuse to load data over XmlHttpRequest from a website that is not in the same origin, which is a precaution against various types of data stealing attacks. The target server has to explicitly allow the origin domain using the Access-Control-Allow-Origin (ACAO) header, or it may allow all origins to access it using a wildcard *. The latter however creates a potential security issue if the website in question is transactional and processing sensitive data, so the wildcard should be only used on websites consciously offering public APIs.

    Read more...

  • Location: https://pixel.quantserve.com/pixel/p-gsmZhdaUra0N6.gif

    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: CP='NOI DSP COR CUR ADMa DEVo TAIo PSAo PSDo IVAo IVDo OUR IND COM NAV INT STA 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-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: Hybrid Web Server

    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!