https://www.facebook.com/v2.7/plugins/share_button.php?app_id=719729204785177&channel=https%3A%2F%2Fstaticxx.facebook.com%2Fconnect%2Fxd_arbiter.php%3Fversion%3D45%23cb%3Df3c3455d907a85%26domain%3Dkoye.hatenadiary.com%26origin%3Dhttps%253A%252F%252Fkoye.hatenadiary.com%252Ff3083f14b5032d4%26relation%3Dparent.parent&container_width=0&href=https%3A%2F%2Fkoye.hatenadiary.com%2Fentry%2F2019%2F08%2F14%2F005750&layout=box_count&locale=ja_JP&sdk=joey

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: 2020-02-14T22:35:52.380885+00:00

HTTP status: 5 Sub-resource URL


TLS/SSL configuration report

TLS score
C
Grade capped at C
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-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...

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

Content Security Policy

  • default-src * data: blob: 'self';script-src *.facebook.com *.fbcdn.net *.facebook.net *.google-analytics.com *.virtualearth.net *.google.com 127.0.0.1:* *.spotilocal.com:* 'unsafe-inline' 'unsafe-eval' blob: data: 'self';style-src data: blob: 'unsafe-inline' *;connect-src *.facebook.com facebook.com *.fbcdn.net *.facebook.net *.spotilocal.com:* wss://*.facebook.com:* https://fb.scanandcleanlocal.com:* attachment.fbsbx.com ws://localhost:* blob: *.cdninstagram.com 'self';block-all-mixed-content;upgrade-insecure-requests;report-uri https://www.facebook.com/csp/reporting/;
  • default-src https: data: wss: blob: chrome-extension: 'unsafe-inline' 'unsafe-eval';report-uri https://www.facebook.com/csp/reporting/;

Want second opinion? Try Google CSP Evaluator.

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