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: "Login"
Description: "France"
Category: Engineering
Keywords: asia north south stone walls africa europe french america english russian zealand exterior products rockwool australia technical industrial insulation applications
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 1 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 5 persistent cookies with average life-time of 243 days and longest 730 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 3 session cookies.
Last fetched: 2020-10-06T14:07:37.549593+00:00
HTTP status: 200 200 OK
HTML5 SessionStorage
is client-side storage introduced by HTML5 and supported by all major
browsers.
Data stored there is not sent automatically by the browser (unlike HTTP cookies) but is accessible
to
JavaScript code during the browser session only, so until the browser window or tab is closed.
These object can be thus compared to first-party session cookies from privacy point of
view.
SessionStorage
cookieSessionStorage
cookieSessionStorage
cookieAdvanced user tracking and fingerprinting techniques are used by websites to bypass privacy protection in web browsers and increase tracking persistence.
Server: Apache
Announces web server software and optionally version details.
Read more...Feature-Policy: accelerometer 'none'; camera 'none'; gyroscope 'none'; magnetometer 'none'; microphone 'none'; usb 'none'; vr '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...
Feature-Policy enabled
+1Expect-CT: max-age=0
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...Referrer-Policy: same-origin
The Referrer-Policy HTTP header governs which referrer information, sent in the Referer header, should be included with requests made.
Read more...
Referrer-Policy enabled
+1X-Content-Type-Options: nosniff
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
+1X-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 0
.
XSS auditor is enabled in blocking mode
+1X-Frame-Options: SAMEORIGIN
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
).
Clickjacking protection is enabled
+2X-Permitted-Cross-Domain-Policies: none
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
Location: https://shop.rockwool.com/
The HTTP Location header is being returned by a server to redirect the web browser to a new URL of the requested resource. The URL may be relative (/index.html
) or absolute (https://example.com
).
Transport Layer Security (TLS) is not enabled
-2upgrade-insecure-requests; frame-ancestors 'self'
Content-Security-Policy
No 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
default-src 'self' data:; base-uri 'self'; style-src 'self' 'unsafe-inline' fonts.googleapis.com maps.googleapis.com tagmanager.google.com; script-src 'self' 'sha256-DXV04q1/ORH796oxpXV5EEY+vmondYoLtSAaE0A6S9Q=' 'sha256-cQSwpxbCBaLuR03/UWFCjqR9khSgSZxnCznxU8B464M=' 'sha256-vv8TYJi7ssGM83OmTWya6583Pl7A2jh9rkVQHuFB7ME=' 'sha256-ZNlhfeIP9lY7ob14IDlpDb1kErsiXjqAt6SwMBA0NtY=' 'sha256-Gak3K0zIF40Cy0x7Yv0HkPF6VkUg7T0XSQGl4H/nWx8' 'sha256-Aada+rNBBLco5h5wCa5CH1+EEh9JmNOwb0ZRtNdKm4k=' 'sha256-gCCK47uUID2gFV/f+/eqwN7gyDMmpcBcPU7QC8oYnUs=' 'sha256-YYwr62i7ALqjWxLNdqh63SUR53dhTshs8E9g641BtuQ=' 'sha256-3KEF+2b0ODsLGx06ULUjB6ZA+TGXZD1DQWqdWx/NKv4=' 'sha256-PHKXYxsK8eHjCvrreQBqYQpeqVGar2Tc3gzq8xlMR74=' 'sha256-Dd3WFHb2SFPEXBQSA5JNf3bpZGxV1NptAzZx9/fQ1FQ=' 'sha256-hoaHzyDeUuIXKs20XtvYcqUT4Il4bFu01tiangr7Cr4=' 'sha256-fcJ5iNgfx+qHfeL9zRnVFkB4HdP2XCRsKet3fuTrFbU=' 'nonce-Mkh_AAABzWMAAAFsYbM6ANN6' siteimproveanalytics.com cookieinfo.siteimprove.com fonts.googleapis.com static.zdassets.com www.googleanalytics.com fonts.gstatic.com maps.gstatic.com www.googletagmanager.com www.google-analytics.com widget-mediator.zopim.com *.upscope.io *.msecnd.net consent.cookiebot.com consentcdn.cookiebot.com; media-src static.zdassets.com; font-src 'self' fonts.googleapis.com maps.googleapis.com static.zdassets.com www.googleanalytics.com *.gstatic.com maps.gstatic.com www.googletagmanager.com wss://widget-mediator.zopim.com widget-mediator.zopim.com data:; connect-src 'self' www.google-analytics.com fonts.googleapis.com maps.googleapis.com static.zdassets.com www.googleanalytics.com fonts.gstatic.com maps.gstatic.com www.googletagmanager.com ekr.zdassets.com rockwoolsupport.zendesk.com widget-mediator.zopim.com wss://widget-mediator.zopim.com data.upscope.io wss://data.upscope.io dc.services.visualstudio.com; img-src 'self' data: www.google.com/ads/ga-audiences cdn-img.rockwool.com stats.g.doubleclick.net asset.productmarketingcloud.com cookieinfo.siteimprove.com 667773.global.siteimproveanalytics.io brandcommunity.rockwool.com cdn01-shop.rockwool.com fonts.googleapis.com maps.googleapis.com fonts.gstatic.com maps.gstatic.com www.google-analytics.com *.gstatic.com corerock-rwimg-p-euw-001.azureedge.net; object-src 'none'; frame-src www.googletagmanager.com storage.upscope.io consent.cookiebot.com consentcdn.cookiebot.com; worker-src 'self'; prefetch-src 'none';
<meta http-equiv="Content-Security-Policy">
Consider adding 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
The default-src data:
origin allows bypassing CSP and execution of inlined untrusted scripts
Origin style-src 'unsafe-inline'
allows bypassing of CSP and execution of inlined untrusted scripts. Use 'nonce-'
or 'sha256-'
instead
You should definitely try using 'strict-dynamic'
to eliminate those long lists of trusted third-party scripts
Consider using script-src 'report-sample'
as it significantly helps debugging CSP reports. See specification
Origin script-src fonts.gstatic.com
is known to host JSONP which can be used to bypass CSP and execute untrusted scripts
Origin script-src maps.gstatic.com
is known to host JSONP which can be used to bypass CSP and execute untrusted scripts
Origin script-src www.google-analytics.com
is known to host JSONP which can be used to bypass CSP and execute untrusted scripts
upgrade-insecure-requests; frame-ancestors 'self'
Content-Security-Policy
No 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
Want second opinion? Try Google CSP Evaluator.
The website uses the following advertisement publisher ids:
Most web pages load a number of sub-resources such as images, style sheets (CSS), JavaScript files, web fonts, audio or video files and other web pages in frames. Each of these sub-resources may be loaded from the same server (first-party resource) or servers belonging to other parties (third-party resources). In the latter case, the third-party will see a request coming from your browser with the information on the originating page and it can set its own cookies, both of which are frequently used for user tracking. Note that the cookies set by these sub-resources are already recorded in our cookie statistics for this page.
The page loads 7 third-party JavaScript files and 0 CSS but does not employ Sub-Resource Integrity to prevent breach if a third-party CDN is compromised