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: Search Engine
Last fetched: 2019-12-17T02:37:24.416396+00:00
HTTP status: 5 Sub-resource URL
The Referrer-Policy HTTP header governs which referrer information, sent in the Referer header, should be included with requests made.Read more...
Feature-Policy: ambient-light-sensor 'none'; fullscreen 'none'; geolocation 'self'; magnetometer 'none'; display-capture 'none'; vibrate 'none'; sync-xhr 'self' https://api.qwant.com; speaker 'self'; oversized-images 'none'; encrypted-media 'none'; usb 'none'; midi 'none'; microphone 'none'; payment 'none'; autoplay 'self'; gyroscope 'none'; camera 'none'; vr 'none'; accelerometer 'none'; document-domain '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...
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
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
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
Announces web server software and optionally version details.Read more...
Transport Layer Security (TLS) is enabled+2
default-src 'self' data: blob:; media-src blob: *.qwant.com *.apple.com *.qobuz.com; script-src-elem 'self' 'unsafe-inline' 'unsafe-eval' data: *.qwant.com; object-src 'self'; connect-src *.qobuz.com *.apple.com wss://masq-ws.qwant.com *.qwant.com extras.qwantjunior.com; font-src 'self'; base-uri 'self'; block-all-mixed-content; worker-src blob: 'self' www.youtube-nocookie.com www.youtube.com; img-src blob: 'self' s1.qwant.com s2.qwant.com s.qwant.com data: s-boards.qwant.com s-lite.qwant.com www.qwant.com; script-src 'self' 'unsafe-inline' 'unsafe-eval' data: *.qwant.com; frame-src viewer.dood3d.com *.vid.web.acsta.net player.twitch.tv player.vimeo.com www.dailymotion.com *.qwant.com *.qwantjunior.com www.youtube-nocookie.com *.tvlocale.fr *.smartrezo.com *.femmesetcitoyennete.fr *.jeunesreporterssansfrontieres.fr *.medias-francophones.com *.trendy-community.fr *.tvcitoyenne.com *.veitech.com *.localetv.eu player.myvideoplace.tv; style-src 'unsafe-inline' data: *.qwant.com *.qwantjunior.com *.kamoov.com; form-action 'self'; frame-ancestors *.qwant.com *.qwantjunior.com lmqt.fyi;
default-src data: origin allows bypassing CSP and execution of inlined untrusted scripts
script-src-elem 'unsafe-inline' allows bypassing of CSP and execution of inlined untrusted scripts. Use
script-src-elem 'unsafe-eval' allows bypassing of CSP and execution of inlined untrusted scripts. Use
script-src data: origin allows bypassing CSP and execution of inlined untrusted scripts
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-inline' allows bypassing of CSP and execution of inlined untrusted scripts. Use
script-src 'unsafe-eval' 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
Want second opinion? Try Google CSP Evaluator.
The website uses the following advertisement publisher ids: