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.
Last fetched: 2017-12-16T16:16:30.463240+00:00
HTTP status: 5 Sub-resource URL
Announces web server software and optionally version details.Read more...
P3P: CP="WLD Desktop does not have a P3P policy."
Content-Security-Policy: default-src * 'unsafe-inline' 'unsafe-eval' data: blob:
Content Security Policy is used by a web server to declare a list of trusted content types (images, scripts, media etc) and origins from which they can be safely loaded as intended by the website authors. The
Content-Security-Policy-Report-Only header instruct the browser to enable CSP in enforcement mode.
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 (
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
Transport Layer Security (TLS) is not enabled-2
default-src * 'unsafe-inline' 'unsafe-eval' data: blob:
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
default-src 'unsafe-inline' allows bypassing of CSP and execution of inlined untrusted scripts. Use
default-src 'unsafe-eval' allows bypassing of CSP and execution of inlined untrusted scripts. Use
The website uses the following advertisement publisher ids: