Security Report Summary
A+
| Site: | https://tommytaylor.co.uk/ |
|---|---|
| IP Address: | 2001:1b40:5fff:ffe0::b |
| Report Time: | 04 Apr 2020 11:35:34 UTC |
| Headers: |
|
Raw Headers
| HTTP/1.1 | 200 OK |
|---|---|
| Date | Sat, 04 Apr 2020 11:35:33 GMT |
| Content-Type | text/html; charset=UTF-8 |
| Transfer-Encoding | chunked |
| Connection | keep-alive |
| Vary | Accept-Encoding |
| X-Content-Type-Options | nosniff |
| X-XSS-Protection | 1; mode=block; report=https://tomtaylorcoltd.report-uri.com/r/d/xss/enforce |
| Referrer-Policy | strict-origin-when-cross-origin |
| Expect-CT | enforce,max-age=30,report-uri="https://tomtaylorcoltd.report-uri.com/r/d/ct/enforce" |
| Content-Security-Policy | frame-ancestors 'self'; report-uri https://tomtaylorcoltd.report-uri.com/r/d/csp/enforce |
| Feature-Policy | accelerometer 'none'; camera 'none'; geolocation 'none'; gyroscope 'none'; magnetometer 'none'; microphone 'none'; payment 'none'; usb 'none' |
| Cache-Control | max-age=600, must-revalidate |
| Expires | Sat, 04 Apr 2020 11:45:33 GMT |
| Strict-Transport-Security | max-age=15768000; preload |
| X-Nginx-Cache-Status | BYPASS |
| Access-Control-Allow-Origin | https://tommytaylor.co.uk |
| Alternate-Protocol | 443:npn-http/2 |
| Alt-Svc | h2=":443"; ma=3600; persist=1 |
| X-Cache-Dynamic-Status | BYPASS |
| X-FRAME-OPTIONS | SAMEORIGIN |
Additional Information
| 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. |
| 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. |
| Expect-CT | Expect-CT allows a site to determine if they are ready for the upcoming Chrome requirements and/or enforce their CT policy. |
| 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. Analyse this policy in more detail. |
| Feature-Policy | Feature Policy is a new header that allows a site to control which features and APIs can be used in the browser. |
| 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. |
| Access-Control-Allow-Origin | The Access-Control-Allow-Origin header is used to configure CORS. |
| Alternate-Protocol | Alternate Protocol advertises that this server is capable of supporting, you guessed it, an alternate protocol! Usually advertising QUIC or SPDY support. SPDY is a great way to reduce the overhead of using TLS. |
| 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. |