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: "404 — Page not found"
Category: Information Security
Keywords: csp ndc blog hpkp hsts http oslo april cheat https sheet table author report storage 201729th response security performance securityheadersio
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 0 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 1 persistent cookies with average life-time of 29 days and longest 29 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 1 session cookies.
Last fetched: 2020-04-08T15:22:52.186695+00:00
HTTP status: 200 200
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
Expect-CT: max-age=604800, report-uri="https://scotthelme.report-uri.com/r/d/ct/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
Feature-Policy: accelerometer 'none'; camera 'none'; geolocation 'none'; gyroscope 'none'; magnetometer 'none'; microphone 'none'; payment 'none'; usb '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...
Network Error Logging (NEL) defines a mechanism enabling web applications to declare a reporting policy that can be used by an user agent to report network errors for a given origin.Read more...
The Referrer-Policy HTTP header governs which referrer information, sent in the Referer header, should be included with requests made.Read more...
The header defines a generic reporting framework which allows web developers to associate a set of named reporting endpoints with an origin. Various platform features (like Content Security Policy, Network Error Reporting, and others) may use these endpoints to deliver feature-specific reports in a consistent manner.Read more...
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
X-XSS-Protection: 1; mode=block; report=https://scotthelme.report-uri.com/r/d/xss/enforce
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
Announces web server software and optionally version details.Read more...
Transport Layer Security (TLS) is enabled+2
X-Frame-Options header is missing
default-src 'self'; script-src 'self' 'report-sample' disqus.com c.disquscdn.com platform.instagram.com cdnjs.cloudflare.com scotthelme.disqus.com a.disquscdn.com go.disqus.com platform.twitter.com cdn.syndication.twimg.com syndication.twitter.com gist.github.com/ScottHelme/ www.googletagmanager.com www.google-analytics.com; style-src 'self' 'report-sample' c.disquscdn.com a.disquscdn.com fonts.googleapis.com cdnjs.cloudflare.com platform.twitter.com assets-cdn.github.com github.githubassets.com; img-src 'self' data: www.gravatar.com links.services.disqus.com referrer.disqus.com a.disquscdn.com cdn.syndication.twimg.com syndication.twitter.com pbs.twimg.com platform.twitter.com abs.twimg.com www.google-analytics.com; child-src www.instagram.com twitter.com fusiontables.googleusercontent.com fusiontables.google.com www.google.com disqus.com www.youtube.com syndication.twitter.com platform.twitter.com www.youtube-nocookie.com; connect-src 'self' syndication.twitter.com links.services.disqus.com; font-src 'self' cdnjs.cloudflare.com fonts.gstatic.com fonts.googleapis.com; form-action 'self' syndication.twitter.com; frame-ancestors 'none'; prefetch-src 'self' c.disquscdn.com disqus.com; upgrade-insecure-requests; report-uri https://scotthelme.report-uri.com/r/d/csp/enforce; report-to default
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
Policy that has
script-src but not
default-src: 'none' 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 www.google-analytics.com is known to host JSONP which can be used to bypass CSP and execute untrusted scripts
Want second opinion? Try Google CSP Evaluator.