https://codex.nflxext.com/%5E3.0.0/truthBundle/webui/0.0.1-shakti-js-v52397647/js/js/components|login|loginControllerClient.js/2/4Q034o4n4b4p05474x4P070q004R4s4z4q4J4d4y4l4B0b024M15/l/true/none

Category: Sports

Keywords:


Last fetched: 2020-03-25T21:01:39.993856+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 codex.nflxext.com

Security-related HTTP headers

  • Server: nginx

    Announces web server software and optionally version details.

    Read more...

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

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

Sub-resources

Parent pages

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