Security Report Summary
A
Site: | https://mastrchef.rocks/ |
---|---|
IP Address: | 129.21.49.89 |
Report Time: | 12 Dec 2019 13:20:06 UTC |
Headers: |
|
Raw Headers
HTTP/1.1 | 200 OK |
---|---|
Server | GNU Netcat 0.7.1 |
Date | Thu, 12 Dec 2019 13:20:06 GMT |
Content-Type | text/html; charset=utf-8 |
Content-Length | 10671 |
Last-Modified | Tue, 19 Nov 2019 01:21:31 GMT |
Connection | keep-alive |
Vary | Accept-Encoding |
ETag | "5dd3439b-29af" |
X-Frame-Options | sameorigin |
X-Content-Type-Options | nosniff |
X-XSS-Protection | 1; mode=block |
Strict-Transport-Security | max-age=63072000 |
Referrer-Policy | strict-origin |
Feature-Policy | geolocation 'none'; midi 'none'; sync-xhr 'none'; microphone 'none'; camera 'none'; magnetometer 'none'; gyroscope 'none'; speaker 'none'; fullscreen 'self'; payment 'none' |
Access-Control-Allow-Origin | * |
Accept-Ranges | bytes |
Missing Headers
Content-Security-Policy | Content 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. |
---|
Upcoming Headers
Expect-CT | Expect-CT allows a site to determine if they are ready for the upcoming Chrome requirements and/or enforce their CT policy. |
---|
Additional Information
Server | Server value has been changed. Typically you will see values like "Microsoft-IIS/8.0" or "nginx 1.7.2". |
---|---|
X-Frame-Options | X-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. |
X-Content-Type-Options | X-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". |
X-XSS-Protection | X-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. |
Strict-Transport-Security | HTTP 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. |
Referrer-Policy | Referrer 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. |
Feature-Policy | Feature Policy is a new header that allows a site to control which features and APIs can be used in the browser. |
Access-Control-Allow-Origin | This is a very lax CORS policy. Such a policy should only be used on a public CDN. |