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: 2020-09-07T23:03:20.863222+00:00
HTTP status: 5 Sub-resource URL
Announces web server software and optionally version details.Read more...
A misspelled and incorrect variant of the
X-Frame-Options header introduced as a result of incorrect interpretation of RFC 7034 standard. The
Frame-Options variant was introduced to be used in Content Security Policy (CSP) while for HTTP headers the
X-Frame-Options remains the valid name.
This is an invalid variant of the
X-Frame-Options header and it has no effect
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 (
Clickjacking protection is enabled+2
X-XSS-Protection: 1; mode=block
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 enabled in blocking mode+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.
Fuzzy content type guessing is disabled+1
Strict-Transport-Security: max-age=16070400; includeSubDomains
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
A non-standard header used by Microsoft ASP.NET platform to advertise its detailed version.Read more...
A non-standard and purely informational, but still very widespread header, whose only purpose is to advertise the name and optionally version of the software used to run the web server.Read more...
Transport Layer Security (TLS) is enabled+2