https://www.facebook.com/connect/ping?client_id=313017045538537&domain=hk.appledaily.com&origin=1&redirect_uri=https%3A%2F%2Fstaticxx.facebook.com%2Fconnect%2Fxd_arbiter%2Fr%2FRQ7NiRXMcYA.js%3Fversion%3D42%23cb%3Df12c57e768%26domain%3Dhk.appledaily.com%26origin%3Dhttps%253A%252F%252Fhk.appledaily.com%252Ff1e866661c%26relation%3Dparent&response_type=token%2Csigned_request%2Ccode&sdk=joey&version=v2.8

Category: Social Network

Keywords: apps data make share users others people policy account content cookies provide facebook policies services companies including statement advertising information


Last fetched: 2018-05-21T17:46:37.085838+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 www.facebook.com

Security-related HTTP headers

  • X-XSS-Protection: 0

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

  • Location: https://staticxx.facebook.com/connect/xd_arbiter/r/RQ7NiRXMcYA.js?version=42#cb=f12c57e768&domain=hk.appledaily.com&origin=https%3A%2F%2Fhk.appledaily.com%2Ff1e866661c&relation=parent&error=unknown_user

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

  • Strict-Transport-Security: max-age=15552000; preload

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

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