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.
User tracking using web beacons
Category: Search Engine Clean Browsing
Keywords: data play learn share store using google policy search account collect content example privacy service started personal services including information
Last fetched: 2020-07-26T20:54:17.304167+00:00
HTTP status: 5 Sub-resource URL
Advanced user tracking and fingerprinting techniques are used by websites to bypass privacy protection in web browsers and increase tracking persistence.
b'navigator.sendBeacon' … b'navigator.sendBeacon'
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 (
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...
HTTP Strict Transport Security is enabled+2
Announces web server software and optionally version details.Read more...
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
XSS auditor is disabled0
P3P: CP="This is not a P3P policy! See g.co/p3phelp for more info."
Transport Layer Security (TLS) is enabled+2
X-Frame-Options header is missing
X-Content-Type-Options header is missing
default-src https: data:; options eval-script inline-script; report-uri /csp_report; referrer origin
Content-Security-Policyheader for policy delivery instead.
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
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
default-src data: origin allows bypassing CSP and execution of inlined untrusted scripts
options is not part of the latest W3C CSP standard
referrer is not part of the latest W3C CSP standard
Want second opinion? Try Google CSP Evaluator.