Web Cookies Scanner
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: Not Configured
Keywords: conf file root files works before itself server should ubuntu apache2 default located package document different reporting respective configuration documentation
Last fetched: 2019-11-29T17:55:14.001976+00:00
HTTP status: 5 Sub-resource URL
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.
X-XSS-Protection: 1; mode=block
XSS auditor is enabled in blocking mode
+1
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.
Strict-Transport-Security: max-age=31536000 ; includeSubDomains
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-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).
Referrer-Policy: no-referrer
Referrer-Policy enabled
+1
The Referrer-Policy HTTP header governs which referrer information, sent in the Referer header, should be included with requests made.
Read more...Feature-Policy: vibrate 'none'; geolocation 'self'
Feature-Policy enabled
+1
Allows web developers selectively enable and disable specific web technologies, especially those that enable two-way communication between the user and web application. For example, the header may inform the user mobile device that the website is not using camera or location tracking by design.
Read more...Transport Layer Security (TLS) is enabled
+2form-action 'self'; base-uri 'none'; img-src *; child-src 'none'; object-src 'none'; report-uri /csp-report-endpoint/
Content-Security-Policy
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
object-src 'none'; report-uri /csp-report-endpoint/
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
object-src 'none'; report-uri /csp-report-endpoint/
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
object-src 'none'; report-uri /csp-report-endpoint/
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
object-src 'none'; report-uri /csp-report-endpoint/
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
form-action 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' https: http:; base-uri 'none'; img-src *; child-src 'none'; object-src 'none'; report-uri /csp-report-endpoint/
Content-Security-Policy
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
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
form-action 'self'; base-uri 'none'; img-src *; child-src 'none'; object-src 'none'; report-uri /csp-report-endpoint/
Content-Security-Policy
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
form-action 'self'; base-uri 'none'; img-src *; child-src 'none'; object-src 'none'; report-uri /csp-report-endpoint/
Content-Security-Policy
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
form-action 'self'; base-uri 'none'; img-src *; child-src 'none'; object-src 'none'; report-uri /csp-report-endpoint/
Content-Security-Policy
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
form-action 'self'; base-uri 'none'; img-src *; child-src 'none'; object-src 'none'; report-uri /csp-report-endpoint/
Content-Security-Policy
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
form-action 'self'; base-uri 'none'; img-src *; child-src 'none'; object-src 'none'; report-uri /csp-report-endpoint/
Content-Security-Policy
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
form-action 'self'; base-uri 'none'; img-src *; child-src 'none'; object-src 'none'; report-uri /csp-report-endpoint/
Content-Security-Policy
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
form-action 'self'; base-uri 'none'; img-src *; child-src 'none'; frame-ancestors 'self'; object-src 'none'; report-uri /csp-report-endpoint/
Content-Security-Policy
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
form-action 'self'; base-uri 'none'; img-src *; child-src 'none'; frame-ancestors 'self'; object-src 'none'; report-uri /csp-report-endpoint/
Content-Security-Policy
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
form-action 'self'; base-uri 'none'; img-src *; child-src 'none'; frame-ancestors 'self'; object-src 'none'; report-uri /csp-report-endpoint/
Content-Security-Policy
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
form-action 'self'; base-uri 'none'; img-src *; child-src 'none'; frame-ancestors 'self'; object-src 'none'; report-uri /csp-report-endpoint/
Content-Security-Policy
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
form-action 'self'; base-uri 'none'; img-src *; child-src 'none'; frame-ancestors 'self'; object-src 'none'; report-uri /csp-report-endpoint/
Content-Security-Policy
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
form-action 'self'; base-uri 'none'; img-src *; child-src 'none'; frame-ancestors 'self'; object-src 'none'; report-uri /csp-report-endpoint/
Content-Security-Policy
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
form-action 'self'; base-uri 'none'; img-src *; child-src 'none'; frame-ancestors 'self'; object-src 'none'; report-uri /csp-report-endpoint/
Content-Security-Policy
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