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: Offline
Keywords:
Last fetched: 2018-09-05T08:44:57.480446+00:00
HTTP status: 5 Sub-resource URL
See full SSL/TLS security report for static-global-s-msn-com.akamaized.net
Server: Microsoft-IIS/8.5
The header exposes web server version details. These server no purpose apart from making life of security auditors and hackers easier, leading them straight to exploits for this particular version of product
-1
Announces web server software and optionally version details.
Read more...X-XSS-Protection: 1
XSS auditor is enabled in sanitization 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.
X-Frame-Options: SAMEORIGIN
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).
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: *
The header sets permissive AJAX access by using wildcard origin *. It may be OK if the website is a publicly accessible REST API but otherwise it should be not present at all
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.
X-Powered-By: ASP.NET
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
+2The website uses the following advertisement publisher ids: