Security Report Summary
B
Site: http://wecanwedo2.loki.media/ - (Scan again over https)
IP Address: 13.251.105.237
Report Time: 10 Aug 2020 07:41:45 UTC
Headers:
  • Feature-Policy
  • Referrer-Policy
  • X-Content-Type-Options
  • Content-Security-Policy
  • X-Frame-Options
Warning: Grade capped at A, please see warnings below.
Supported By
Report URI
Quickly and easily enable reporting for CSP and other Security Headers!
Raw Headers
HTTP/1.1200 OK
DateMon, 10 Aug 2020 07:41:45 GMT
ServerApache
Feature-Policymicrophone 'none'; payment 'none'; sync-xhr 'self' https://wecanwedo2.loki.media
Referrer-Policyno-referrer
Expect-CTenforce, max-age=300, report-uri='https://wecanwedo2.loki.media/'
VaryAccept-Encoding
Access-Control-Allow-Originnull
Cache-Controlno-cache, no-store, must-revalidate
Pragmano-cache
Expires0
X-XSS-Protection1; mode=block
X-Content-Type-Optionsnosniff
Strict-Transport-Securitymax-age=31536000; includeSubDomains; preload
Content-Security-Policydefault-src * data:; img-src * data:;style-src * 'unsafe-inline'; font-src * data:; script-src * 'unsafe-inline' 'unsafe-eval';
X-Content-Security-Policydefault-src * data:; img-src * data:;style-src * 'unsafe-inline'; font-src * data:; script-src * 'unsafe-inline' 'unsafe-eval';
X-WebKit-CSPdefault-src * data:; img-src * data:;style-src * 'unsafe-inline'; font-src * data:; script-src * 'unsafe-inline' 'unsafe-eval';
Transfer-Encodingchunked
Content-Typetext/html; charset=UTF-8
Missing Headers
X-Frame-OptionsX-Frame-Options tells the browser whether you want to allow your site to be framed or not. By preventing a browser from framing your site you can defend against attacks like clickjacking. Recommended value "X-Frame-Options: SAMEORIGIN".
Warnings
Site is using HTTPThis site was served over HTTP and did not redirect to HTTPS.
Content-Security-PolicyThis policy contains 'unsafe-inline' which is dangerous in the style-src directive. This policy contains 'unsafe-inline' which is dangerous in the script-src directive. This policy contains 'unsafe-eval' which is dangerous in the script-src directive.
Additional Information
ServerThis Server header seems to advertise the software being run on the server but you can remove or change this value.
Feature-PolicyFeature Policy is a new header that allows a site to control which features and APIs can be used in the browser.
Referrer-PolicyReferrer Policy is a new header that allows a site to control how much information the browser includes with navigations away from a document and should be set by all sites.
Expect-CTExpect-CT allows a site to determine if they are ready for the upcoming Chrome requirements and/or enforce their CT policy, but it should not be sent over HTTP.
Access-Control-Allow-OriginThe Access-Control-Allow-Origin header is used to configure CORS.
X-XSS-ProtectionX-XSS-Protection sets the configuration for the XSS Auditor built into older browser. The recommended value was "X-XSS-Protection: 1; mode=block" but you should now look at Content Security Policy instead.
X-Content-Type-OptionsX-Content-Type-Options stops a browser from trying to MIME-sniff the content type and forces it to stick with the declared content-type. The only valid value for this header is "X-Content-Type-Options: nosniff".
Strict-Transport-SecurityHTTP Strict Transport Security is an excellent feature to support on your site and strengthens your implementation of TLS. That said, the HSTS header must not be returned over a HTTP connection, only HTTPS.
Content-Security-PolicyContent Security Policy is an effective measure to protect your site from XSS attacks. By whitelisting sources of approved content, you can prevent the browser from loading malicious assets. Analyse this policy in more detail. You can sign up for a free account on Report URI to collect reports about problems on your site.
X-Content-Security-PolicyX Content Security Policy is required for CSP support in IE 10 and IE 11. For other modern browsers the Content-Security-Policy header should be used.
X-WebKit-CSPX-Webkit-CSP is required for CSP support in older Chrome, Safari and other Webkit based browsers. For other modern browsers the Content-Security-Policy header should be used.