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.
Title: "- Zacks.com"
Privacy Impact Score is a score reflecting overall cookie-related impact of the website relative to other websites, primarily taking into account the number of third-party domains it reports to and number of persistent cookies it sets. See Privacy Impact Score article for more details.
Third-party domains is the count of organisations allowed by the webmaster to trace your across the site. These cookies may be set for various purposes, like tracking ads displayed on the website, collection of statistics, targeted advertising etc. This website allows 7 other websites to track your activity.
Persistent cookies are the cookies that are preserved through browser shutdowns. This means, even if you close this page today and ever return there in future, the website will know you're a returning visitor. This may be used for "remember me" features, as well as persistent user tracking. These cookies, especially if set by third party organisations, are powerful tool for monitoring your activities across all the websites you visit. This website sets 20 persistent cookies with average life-time of 572 days and longest 3651 days.
Session cookies are cleared when you close your browser and allow the website to identify user's state — such as logged-in users. They are mostly considered harmless because they cannot be used for long-term user tracking. This site sets 4 session cookies.
Last fetched: 2019-05-09T11:56:17.124068+00:00
HTTP status: 200 200 OK
LocalStorage is client-side storage introduced by HTML5 and supported by all major
Data stored there is not sent automatically by the browser (unlike HTTP cookies) but is accessible
These object can be thus compared to first-party persistent cookies from privacy point of
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.
HTTP Strict Transport Security is enabled+2
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...
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
The Referrer-Policy HTTP header governs which referrer information, sent in the Referer header, should be included with requests made.Read more...
Public-Key-Pins: pin-sha256="jUsu/VjvX2kf9Uon878kdUaRWXWvdaVR79bL1+CCpK0="; pin-sha256="5kJvNEMw0KjrCAu7eXY5HZdvyCS13BbA0VJG1RSP91w="; max-age=5184000; includeSubDomains
HTTP Public Key Pinning is in enforcement mode. Note that Chrome is deprecating HPKP starting from version 69 but other browsers declared no plans to deprecate+2
Announces a list of X.509 certificate hashes that are allowed to appear in the website's TLS certification path (HTTP Public Key Pinning or HPKP). This prevents malicious proxy servers from transparently replacing the public certificates with their own and wiretapping the TLS connection of the unsuspecting user. This header sets HPKP in enforcement mode.Read more...
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
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.
Announces web server software and optionally version details.Read more...
Transport Layer Security (TLS) is enabled+2
default-src https:; script-src https: 'unsafe-eval' 'unsafe-inline';media-src blob: https:; worker-src blob:; style-src https: 'unsafe-inline'; img-src https: data: 'self'; frame-ancestors 'self' zacks.com *.zacks.com;
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
Policy that has
script-src but not
object-src allows script execution by injecting plugin resources. Please read our CSP guidance for more details for more details
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
script-src 'unsafe-eval' allows bypassing of CSP and execution of inlined untrusted scripts. Use
script-src 'unsafe-inline' allows bypassing of CSP and execution of inlined untrusted scripts. Use
style-src 'unsafe-inline' allows bypassing of CSP and execution of inlined untrusted scripts. Use
img-src data: origin allows bypassing CSP and execution of inlined untrusted scripts
The website uses the following advertisement publisher ids: