http://lookingfor.filthyoverfiftydating.com.au/assets/generic/scripts/referral.js


Last fetched: 2017-12-16T16:16:30.463240+00:00

HTTP status: 5 Sub-resource URL


Security-related HTTP headers

  • Server: nginx

    Announces web server software and optionally version details.

    Read more...

  • P3P: CP="WLD Desktop does not have a P3P policy."

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

  • Content-Security-Policy: default-src * 'unsafe-inline' 'unsafe-eval' data: blob:

    Content Security Policy is used by a web server to declare a list of trusted content types (images, scripts, media etc) and origins from which they can be safely loaded as intended by the website authors. The Content-Security-Policy-Report-Only header instruct the browser to enable CSP in enforcement mode.

    Read more...

  • X-Frame-Options: SAMEORIGIN

    Instructs the browser if the current website can be embedded in HTML frame by another website. Since this allows the parent website to control the framed page, this creates a potential for data theft attacks ("clickjacking") and most sensitive websites won't allow them to be framed at all (deny) or just allow parts of them to be embedded in frames created by themselves only (samesite).

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

Content Security Policy

  • default-src * 'unsafe-inline' 'unsafe-eval' data: blob:

Publisher identifiers

The website uses the following advertisement publisher ids:

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