https://disqus.com/embed/comments/?base=default&f=hracingcouk&t_u=https%3A%2F%2Fwww.hracing.co.uk%2F&t_d=Best+Horse+Racing+Betting+UK+Websites&t_t=Best+Horse+Racing+Betting+UK+Websites&s_o=default#version=4fd81c9e35c659f1046a0c8a1b32ae30

Category: Community & Forums

Keywords: build ndash sorry disqus browser audience unsupported


Last fetched: 2019-11-02T13:28:07.532790+00:00

HTTP status: 5 Sub-resource URL


Security-related HTTP headers

  • Server: nginx

    Announces web server software and optionally version details.

    Read more...

  • Link: <https://c.disquscdn.com>;rel=preconnect

    Indicates location of sub-resources for the given page, in machine-readable format. It may come in a number of types, for example next page, previous page, index page, preloading resources etc.

    Read more...

  • Link: <https://c.disquscdn.com>;rel=dns-prefetch

    Indicates location of sub-resources for the given page, in machine-readable format. It may come in a number of types, for example next page, previous page, index page, preloading resources etc.

    Read more...

  • P3P: CP="DSP IDC CUR ADM DELi STP NAV COM UNI INT PHY DEM"

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

  • 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=300; 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...

Content Security Policy

  • script-src https://*.twitter.com:* https://www.gstatic.com/recaptcha/ https://a.disquscdn.com https://c.disquscdn.com c.disquscdn.com https://*.services.disqus.com:* https://cdn.boomtrain.com/p13n/ 'unsafe-inline' https://cdn.syndication.twimg.com/tweets.json https://connect.facebook.net/en_US/sdk.js https://referrer.disqus.com/juggler/ https://apis.google.com https://www.google.com/recaptcha/ https://disqus.com

Want second opinion? Try Google CSP Evaluator.

Publisher identifiers

The website uses the following advertisement publisher ids:

Sub-resources

Parent pages

Parent pages loading this resource.