Security Report Summary
D
| Site: | https://abc.xyz/ | ||
|---|---|---|---|
| IP Address: | 2607:f8b0:4005:80c::200e | ||
| Report Time: | 20 Apr 2024 15:31:23 UTC | ||
| Headers: |
|
||
| Advanced: |
|
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. |
|---|---|
| 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. Recommended value "X-Frame-Options: SAMEORIGIN". |
| 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. |
| Permissions-Policy | Permissions Policy is a new header that allows a site to control which features and APIs can be used in the browser. |
Raw Headers
| HTTP/2 | 200 |
|---|---|
| accept-ranges | bytes |
| vary | Accept-Encoding |
| content-encoding | gzip |
| content-type | text/html |
| access-control-allow-origin | * |
| content-security-policy-report-only | require-trusted-types-for 'script'; report-uri https://csp.withgoogle.com/csp/uxe-owners-acl/abc_xyz |
| cross-origin-resource-policy | cross-origin |
| cross-origin-opener-policy | same-origin; report-to="uxe-owners-acl/abc_xyz" |
| report-to | {"group":"uxe-owners-acl/abc_xyz","max_age":2592000,"endpoints":[{"url":"https://csp.withgoogle.com/csp/report-to/uxe-owners-acl/abc_xyz"}]} |
| content-length | 22689 |
| date | Sat, 20 Apr 2024 15:31:23 GMT |
| expires | Sat, 20 Apr 2024 15:31:23 GMT |
| cache-control | private, max-age=0 |
| last-modified | Tue, 16 Apr 2024 00:03:07 GMT |
| strict-transport-security | max-age=31536000 |
| x-content-type-options | nosniff |
| server | sffe |
| x-xss-protection | 0 |
| alt-svc | h3=":443"; ma=2592000,h3-29=":443"; ma=2592000 |
Upcoming Headers
| Cross-Origin-Embedder-Policy | Cross-Origin Embedder Policy allows a site to prevent assets being loaded that do not grant permission to load them via CORS or CORP. |
|---|
Additional Information
| access-control-allow-origin | This is a very lax CORS policy. Such a policy should only be used on a public CDN. |
|---|---|
| content-security-policy-report-only | Content Security Policy Report Only is used to test a Content Security Policy before making it live. The browser will report on actions that would have been taken based on the policy. 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. |
| cross-origin-resource-policy | Cross-Origin Resource Policy allows a resource owner to specify who can load the resource. |
| cross-origin-opener-policy | Cross-Origin Opener Policy allows a site to opt-in to Cross-Origin Isolation in the browser. |
| report-to | Report-To enables the Reporting API. This allows a website to collect reports from the browser about various errors that may occur. You can sign up for a free account on Report URI to collect these reports. |
| 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. |
| 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". |
| server | Server value has been changed. Typically you will see values like "Microsoft-IIS/8.0" or "nginx 1.7.2". |
| x-xss-protection | X-XSS-Protection sets the configuration for the XSS Auditor built into older browsers. The recommended value was "X-XSS-Protection: 1; mode=block" but you should now look at Content Security Policy instead. |