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.
Keywords: blog work shall rights bitcoin without ethereum exchange litecoin policies property services trade247 contracts employees preferred intellectual cryptotrading cryptoexchange trade247exchange
Last fetched: 2018-06-28T22:20:10.934554+00:00
HTTP status: 5 Sub-resource URL
Announces web server software and optionally version details.Read more...
Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
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
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
The Referrer-Policy HTTP header governs which referrer information, sent in the Referer header, should be included with requests made.Read more...
Feature-Policy: camera 'none'; microphone 'none'; gyroscope 'none';
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...
Header used by Adobe Flash engine to control cross-site access for Flash applications. Most websites not using Flash would prefer to set it with the value of
none as an additional precaution against using them in advanced Flash-based XSS vectors. Flash-serving websites can use them to declare the scope of detailed Flash cross-site policies per Adobe specification.
The header reduces exposure to Adobe Flash based XSS and does not have side effects, so it is worth setting it to
none if you are not using Flash
Expect-CT: max-age=3600, report-uri="https://trade247.report-uri.com/r/d/ct/enforce", enforce
The Expect-CT header allows sites to opt in to reporting and/or enforcement of Certificate Transparency requirements, which prevents the use of misissued certificates for that site from going unnoticed. When a site enables the Expect-CT header, they are requesting that the browser check that any certificate for that site appears in public CT logs.Read more...
Expect-CT is in enforcement mode+2
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.
Transport Layer Security (TLS) is enabled+2
default-src 'none'; style-src 'self'; base-uri 'self'; frame-ancestors 'self'; frame-src 'self'; worker-src 'self'; script-src 'self'; img-src data: 'self' https://trade247.exchange; form-action 'self'; block-all-mixed-content; font-src 'self'; manifest-src 'self'; object-src 'self';
You should definitely try using
'strict-dynamic' to eliminate those long lists of trusted third-party scripts
script-src 'report-sample' as it significantly helps debugging CSP reports. See specification
Want second opinion? Try Google CSP Evaluator.