https://play.eslgaming.com/interface/ajax/tePageVisit.php

Category: Sports

Keywords: echo jedi play team arena black clash north combat league mobile search account america legends premium trusted tournament information tournaments


Last fetched: 2019-05-31T03:57:37.801947+00:00

HTTP status: 5 Sub-resource URL


TLS/SSL configuration report

TLS score
A

See full SSL/TLS security report for play.eslgaming.com

Security-related HTTP headers

  • Feature-Policy: geolocation *;midi *;notifications *;push *;sync-xhr *;gyroscope *;speaker *;magnetometer *;vibrate *;payment *;autoplay none;fullscreen *;microphone none;camera none;

    Allows web developers selectively enable and disable specific web technologies, especially those that enable two-way communication between the user and web application. For example, the header may inform the user mobile device that the website is not using camera or location tracking by design.

    Read more...

  • Referrer-Policy: strict-origin-when-cross-origin

    The Referrer-Policy HTTP header governs which referrer information, sent in the Referer header, should be included with requests made.

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

  • Strict-Transport-Security: max-age=31536000; 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...

Content Security Policy

  • block-all-mixed-content; report-uri https://tet.report-uri.io/r/default/csp/enforce
  • block-all-mixed-content; report-uri https://tet.report-uri.io/r/default/csp/enforce
  • block-all-mixed-content; report-uri https://tet.report-uri.io/r/default/csp/enforce
  • block-all-mixed-content; report-uri https://tet.report-uri.io/r/default/csp/enforce
  • block-all-mixed-content; report-uri https://tet.report-uri.io/r/default/csp/enforce
  • block-all-mixed-content; report-uri https://tet.report-uri.io/r/default/csp/enforce
  • block-all-mixed-content; report-uri https://tet.report-uri.io/r/default/csp/enforce

Publisher identifiers

The website uses the following advertisement publisher ids:

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