Security Report Summary
A
Site: https://www.tomelloso.info/
IP Address: 207.180.240.135
Report Time: 16 Jun 2019 20:53:38 UTC
Headers:
  • Content-Security-Policy
  • X-Frame-Options
  • Referrer-Policy
  • X-XSS-Protection
  • Feature-Policy
  • Strict-Transport-Security
  • X-Content-Type-Options
Warning: Grade capped at A, please see warnings below.
Supported By
Netsparker - security scanner
Go beyond secure http headers and scan your website for critical vulnerabilities malicious hackers can exploit.
Raw Headers
HTTP/1.1200 OK
Servernginx
DateSun, 16 Jun 2019 20:53:38 GMT
Content-Typetext/html
Content-Length3102
Connectionkeep-alive
Keep-Alivetimeout=60
VaryAccept-Encoding
Content-Security-Policydefault-src https: data: 'unsafe-inline' 'unsafe-eval'
X-Frame-OptionsSAMEORIGIN
Last-ModifiedFri, 17 May 2019 18:29:10 GMT
Accept-Rangesbytes
Cache-Controlmax-age=31536000
ExpiresMon, 15 Jun 2020 20:53:38 GMT
Referrer-Policystrict-origin-when-cross-origin
X-XSS-Protection1; mode=block
X-Permitted-Cross-Domain-Policiesmaster-only
X-Content-Security-Policyallow 'self';
Feature-Policyaccelerometer 'self' ; ambient-light-sensor 'self' ; autoplay 'self' ; camera 'self' ; encrypted-media 'self' ; fullscreen 'self' ; geolocation 'self' ; gyroscope 'self' ; magnetometer 'self' ; microphone 'self' ; midi 'self' ; payment 'self' ; picture-in-picture * ; speaker 'self' ; sync-xhr 'self' ; usb 'self' ; vr 'self';
X-CacheHIT from Backend
Strict-Transport-Securitymax-age=31536000
X-Content-Type-Optionsnosniff
Warnings
Content-Security-PolicyThis policy contains 'unsafe-inline' which is dangerous in the default-src directive. This policy contains 'unsafe-eval' which is dangerous in the default-src directive.
Upcoming Headers
Expect-CTExpect-CT allows a site to determine if they are ready for the upcoming Chrome requirements and/or enforce their CT policy.
Additional Information
ServerThis Server header seems to advertise the software being run on the server but you can remove or change this value.
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-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.
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.
X-XSS-ProtectionX-XSS-Protection sets the configuration for the cross-site scripting filters built into most browsers. The best configuration is "X-XSS-Protection: 1; mode=block".
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.
Feature-PolicyFeature Policy is a new header that allows a site to control which features and APIs can be used in the browser.
Strict-Transport-SecurityHTTP Strict Transport Security is an excellent feature to support on your site and strengthens your implementation of TLS by getting the User Agent to enforce the use of HTTPS.
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".