All-in-one free web application security tool. Web application vulnerability and privacy scanner with support for HTTP cookies, Flash, HTML5 localStorage, sessionStorage, CANVAS, Supercookies, Evercookies. Includes a free SSL/TLS, HTML and HTTP vulnerability scanner and URL malware scanner.
Category: Social Network
Keywords: apps data make share users others people policy account content cookies provide facebook policies services companies including statement advertising information
Third-party domains is the count of organisations allowed by the webmaster to trace your across the site. These cookies may be set for various purposes, like tracking ads displayed on the website, collection of statistics, targeted advertising etc. This website allows 0 other websites to track your activity.
Persistent cookies are the cookies that are preserved through browser shutdowns. This means, even if you close this page today and ever return there in future, the website will know you're a returning visitor. This may be used for "remember me" features, as well as persistent user tracking. These cookies, especially if set by third party organisations, are powerful tool for monitoring your activities across all the websites you visit. This website sets 0 persistent cookies with average life-time of 0 days and longest 0 days.
Session cookies are cleared when you close your browser and allow the website to identify user's state — such as logged-in users. They are mostly considered harmless because they cannot be used for long-term user tracking. This site sets 0 session cookies.
Last fetched: 2016-02-17T10:20:38.678297+00:00
HTTP status: 200 200
X-XSS-Protection: 0
XSS auditor is disabled
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
.
X-Frame-Options: DENY
Clickjacking protection is enabled
+2
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
).
Strict-Transport-Security: max-age=15552000; preload
HTTP Strict Transport Security is enabled
+2
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
Fuzzy content type guessing is disabled
+1
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.
Access-Control-Allow-Origin: https://www.facebook.com
Controls origins (websites) that are allowed to load data from this web service over JavaScript-based APIs as part of Cross-Origin Resource Sharing (CORS) standard. By default, a web browser will refuse to load data over XmlHttpRequest
from a website that is not in the same origin, which is a precaution against various types of data stealing attacks. The target server has to explicitly allow the origin domain using the Access-Control-Allow-Origin
(ACAO) header, or it may allow all origins to access it using a wildcard *
. The latter however creates a potential security issue if the website in question is transactional and processing sensitive data, so the wildcard should be only used on websites consciously offering public APIs.
Transport Layer Security (TLS) is enabled
+2default-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';
Content-Security-Policy
No base-uri
allows attackers to inject base
tags which override the base URI to an attacker-controlled origin. Set to 'none'
unless you need to handle tricky relative URLs scheme
Consider adding block-all-mixed-content
directive if your website is only accessible over TLS and you are certain it doesn not have any legacy plaintext resources. Otherwise you may add adding upgrade-insecure-requests
directive if your website may still have some legacy plaintext HTTP resources and you want them to be still available rather than blocked
Policy that has script-src
but not object-src
allows script execution by injecting plugin resources. Please read our CSP guidance for more details for more details
The default-src data:
origin allows bypassing CSP and execution of inlined untrusted scripts
The script-src data:
origin allows bypassing CSP and execution of inlined untrusted scripts
You should definitely try using 'strict-dynamic'
to eliminate those long lists of trusted third-party scripts
Consider using script-src 'report-sample'
as it significantly helps debugging CSP reports. See specification
Origin script-src 'unsafe-inline'
allows bypassing of CSP and execution of inlined untrusted scripts. Use 'nonce-'
or 'sha256-'
instead
Origin script-src 'unsafe-eval'
allows bypassing of CSP and execution of inlined untrusted scripts. Use 'nonce-'
or 'sha256-'
instead
The style-src data:
origin allows bypassing CSP and execution of inlined untrusted scripts
Origin style-src 'unsafe-inline'
allows bypassing of CSP and execution of inlined untrusted scripts. Use 'nonce-'
or 'sha256-'
instead
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';
Content-Security-Policy
No base-uri
allows attackers to inject base
tags which override the base URI to an attacker-controlled origin. Set to 'none'
unless you need to handle tricky relative URLs scheme
Consider adding block-all-mixed-content
directive if your website is only accessible over TLS and you are certain it doesn not have any legacy plaintext resources. Otherwise you may add adding upgrade-insecure-requests
directive if your website may still have some legacy plaintext HTTP resources and you want them to be still available rather than blocked
Policy that has script-src
but not object-src
allows script execution by injecting plugin resources. Please read our CSP guidance for more details for more details
The default-src data:
origin allows bypassing CSP and execution of inlined untrusted scripts
The script-src data:
origin allows bypassing CSP and execution of inlined untrusted scripts
You should definitely try using 'strict-dynamic'
to eliminate those long lists of trusted third-party scripts
Consider using script-src 'report-sample'
as it significantly helps debugging CSP reports. See specification
Origin script-src 'unsafe-inline'
allows bypassing of CSP and execution of inlined untrusted scripts. Use 'nonce-'
or 'sha256-'
instead
Origin script-src 'unsafe-eval'
allows bypassing of CSP and execution of inlined untrusted scripts. Use 'nonce-'
or 'sha256-'
instead
The style-src data:
origin allows bypassing CSP and execution of inlined untrusted scripts
Origin style-src 'unsafe-inline'
allows bypassing of CSP and execution of inlined untrusted scripts. Use 'nonce-'
or 'sha256-'
instead
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';
Content-Security-Policy
No base-uri
allows attackers to inject base
tags which override the base URI to an attacker-controlled origin. Set to 'none'
unless you need to handle tricky relative URLs scheme
Consider adding block-all-mixed-content
directive if your website is only accessible over TLS and you are certain it doesn not have any legacy plaintext resources. Otherwise you may add adding upgrade-insecure-requests
directive if your website may still have some legacy plaintext HTTP resources and you want them to be still available rather than blocked
Policy that has script-src
but not object-src
allows script execution by injecting plugin resources. Please read our CSP guidance for more details for more details
The default-src data:
origin allows bypassing CSP and execution of inlined untrusted scripts
The script-src data:
origin allows bypassing CSP and execution of inlined untrusted scripts
You should definitely try using 'strict-dynamic'
to eliminate those long lists of trusted third-party scripts
Consider using script-src 'report-sample'
as it significantly helps debugging CSP reports. See specification
Origin script-src 'unsafe-inline'
allows bypassing of CSP and execution of inlined untrusted scripts. Use 'nonce-'
or 'sha256-'
instead
Origin script-src 'unsafe-eval'
allows bypassing of CSP and execution of inlined untrusted scripts. Use 'nonce-'
or 'sha256-'
instead
The style-src data:
origin allows bypassing CSP and execution of inlined untrusted scripts
Origin style-src 'unsafe-inline'
allows bypassing of CSP and execution of inlined untrusted scripts. Use 'nonce-'
or 'sha256-'
instead
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';
Content-Security-Policy
No base-uri
allows attackers to inject base
tags which override the base URI to an attacker-controlled origin. Set to 'none'
unless you need to handle tricky relative URLs scheme
Consider adding block-all-mixed-content
directive if your website is only accessible over TLS and you are certain it doesn not have any legacy plaintext resources. Otherwise you may add adding upgrade-insecure-requests
directive if your website may still have some legacy plaintext HTTP resources and you want them to be still available rather than blocked
Policy that has script-src
but not object-src
allows script execution by injecting plugin resources. Please read our CSP guidance for more details for more details
The default-src data:
origin allows bypassing CSP and execution of inlined untrusted scripts
The script-src data:
origin allows bypassing CSP and execution of inlined untrusted scripts
You should definitely try using 'strict-dynamic'
to eliminate those long lists of trusted third-party scripts
Consider using script-src 'report-sample'
as it significantly helps debugging CSP reports. See specification
Origin script-src 'unsafe-inline'
allows bypassing of CSP and execution of inlined untrusted scripts. Use 'nonce-'
or 'sha256-'
instead
Origin script-src 'unsafe-eval'
allows bypassing of CSP and execution of inlined untrusted scripts. Use 'nonce-'
or 'sha256-'
instead
The style-src data:
origin allows bypassing CSP and execution of inlined untrusted scripts
Origin style-src 'unsafe-inline'
allows bypassing of CSP and execution of inlined untrusted scripts. Use 'nonce-'
or 'sha256-'
instead
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';
Content-Security-Policy
No base-uri
allows attackers to inject base
tags which override the base URI to an attacker-controlled origin. Set to 'none'
unless you need to handle tricky relative URLs scheme
Consider adding block-all-mixed-content
directive if your website is only accessible over TLS and you are certain it doesn not have any legacy plaintext resources. Otherwise you may add adding upgrade-insecure-requests
directive if your website may still have some legacy plaintext HTTP resources and you want them to be still available rather than blocked
Policy that has script-src
but not object-src
allows script execution by injecting plugin resources. Please read our CSP guidance for more details for more details
The default-src data:
origin allows bypassing CSP and execution of inlined untrusted scripts
The script-src data:
origin allows bypassing CSP and execution of inlined untrusted scripts
You should definitely try using 'strict-dynamic'
to eliminate those long lists of trusted third-party scripts
Consider using script-src 'report-sample'
as it significantly helps debugging CSP reports. See specification
Origin script-src 'unsafe-inline'
allows bypassing of CSP and execution of inlined untrusted scripts. Use 'nonce-'
or 'sha256-'
instead
Origin script-src 'unsafe-eval'
allows bypassing of CSP and execution of inlined untrusted scripts. Use 'nonce-'
or 'sha256-'
instead
The style-src data:
origin allows bypassing CSP and execution of inlined untrusted scripts
Origin style-src 'unsafe-inline'
allows bypassing of CSP and execution of inlined untrusted scripts. Use 'nonce-'
or 'sha256-'
instead
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';
Content-Security-Policy
No base-uri
allows attackers to inject base
tags which override the base URI to an attacker-controlled origin. Set to 'none'
unless you need to handle tricky relative URLs scheme
Consider adding block-all-mixed-content
directive if your website is only accessible over TLS and you are certain it doesn not have any legacy plaintext resources. Otherwise you may add adding upgrade-insecure-requests
directive if your website may still have some legacy plaintext HTTP resources and you want them to be still available rather than blocked
Policy that has script-src
but not object-src
allows script execution by injecting plugin resources. Please read our CSP guidance for more details for more details
The default-src data:
origin allows bypassing CSP and execution of inlined untrusted scripts
The script-src data:
origin allows bypassing CSP and execution of inlined untrusted scripts
You should definitely try using 'strict-dynamic'
to eliminate those long lists of trusted third-party scripts
Consider using script-src 'report-sample'
as it significantly helps debugging CSP reports. See specification
Origin script-src 'unsafe-inline'
allows bypassing of CSP and execution of inlined untrusted scripts. Use 'nonce-'
or 'sha256-'
instead
Origin script-src 'unsafe-eval'
allows bypassing of CSP and execution of inlined untrusted scripts. Use 'nonce-'
or 'sha256-'
instead
The style-src data:
origin allows bypassing CSP and execution of inlined untrusted scripts
Origin style-src 'unsafe-inline'
allows bypassing of CSP and execution of inlined untrusted scripts. Use 'nonce-'
or 'sha256-'
instead
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';
Content-Security-Policy
No base-uri
allows attackers to inject base
tags which override the base URI to an attacker-controlled origin. Set to 'none'
unless you need to handle tricky relative URLs scheme
Consider adding block-all-mixed-content
directive if your website is only accessible over TLS and you are certain it doesn not have any legacy plaintext resources. Otherwise you may add adding upgrade-insecure-requests
directive if your website may still have some legacy plaintext HTTP resources and you want them to be still available rather than blocked
Policy that has script-src
but not object-src
allows script execution by injecting plugin resources. Please read our CSP guidance for more details for more details
The default-src data:
origin allows bypassing CSP and execution of inlined untrusted scripts
The script-src data:
origin allows bypassing CSP and execution of inlined untrusted scripts
You should definitely try using 'strict-dynamic'
to eliminate those long lists of trusted third-party scripts
Consider using script-src 'report-sample'
as it significantly helps debugging CSP reports. See specification
Origin script-src 'unsafe-inline'
allows bypassing of CSP and execution of inlined untrusted scripts. Use 'nonce-'
or 'sha256-'
instead
Origin script-src 'unsafe-eval'
allows bypassing of CSP and execution of inlined untrusted scripts. Use 'nonce-'
or 'sha256-'
instead
The style-src data:
origin allows bypassing CSP and execution of inlined untrusted scripts
Origin style-src 'unsafe-inline'
allows bypassing of CSP and execution of inlined untrusted scripts. Use 'nonce-'
or 'sha256-'
instead
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';
Content-Security-Policy
No base-uri
allows attackers to inject base
tags which override the base URI to an attacker-controlled origin. Set to 'none'
unless you need to handle tricky relative URLs scheme
Consider adding block-all-mixed-content
directive if your website is only accessible over TLS and you are certain it doesn not have any legacy plaintext resources. Otherwise you may add adding upgrade-insecure-requests
directive if your website may still have some legacy plaintext HTTP resources and you want them to be still available rather than blocked
Policy that has script-src
but not object-src
allows script execution by injecting plugin resources. Please read our CSP guidance for more details for more details
The default-src data:
origin allows bypassing CSP and execution of inlined untrusted scripts
The script-src data:
origin allows bypassing CSP and execution of inlined untrusted scripts
You should definitely try using 'strict-dynamic'
to eliminate those long lists of trusted third-party scripts
Consider using script-src 'report-sample'
as it significantly helps debugging CSP reports. See specification
Origin script-src 'unsafe-inline'
allows bypassing of CSP and execution of inlined untrusted scripts. Use 'nonce-'
or 'sha256-'
instead
Origin script-src 'unsafe-eval'
allows bypassing of CSP and execution of inlined untrusted scripts. Use 'nonce-'
or 'sha256-'
instead
The style-src data:
origin allows bypassing CSP and execution of inlined untrusted scripts
Origin style-src 'unsafe-inline'
allows bypassing of CSP and execution of inlined untrusted scripts. Use 'nonce-'
or 'sha256-'
instead
Most web pages load a number of sub-resources such as images, style sheets (CSS), JavaScript files, web fonts, audio or video files and other web pages in frames. Each of these sub-resources may be loaded from the same server (first-party resource) or servers belonging to other parties (third-party resources). In the latter case, the third-party will see a request coming from your browser with the information on the originating page and it can set its own cookies, both of which are frequently used for user tracking. Note that the cookies set by these sub-resources are already recorded in our cookie statistics for this page.