Security Report Summary
|02 Mar 2024 06:47:48 UTC
|Permissions Policy is a new header that allows a site to control which features and APIs can be used in the browser.
|Sat, 02 Mar 2024 06:47:48 GMT
|max-age=90, stale-while-revalidate=30, stale-if-error=86400
|1.1 ip-10-0-64-124.eu-west-1.compute.internal (Varnish/7.2), 1.1 ip-10-0-64-124.eu-west-1.compute.internal (Varnish/7.2), 1.1 af9d66efe7802df1efbc8106c86a13e6.cloudfront.net (CloudFront)
|Miss from cloudfront
|frame-ancestors 'self' https://*.t-online.de;
|max-age=31536000; includeSubDomains; preload
|Header not set, see Additional Information below.
|Cross-Origin Embedder Policy allows a site to prevent assets being loaded that do not grant permission to load them via CORS or CORP.
|Cross-Origin Opener Policy allows a site to opt-in to Cross-Origin Isolation in the browser.
|Cross-Origin Resource Policy allows a resource owner to specify who can load the resource.
|Server value has been changed. Typically you will see values like "Microsoft-IIS/8.0" or "nginx 1.7.2".
|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.
|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.
|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. You can sign up for a free account on Report URI to collect reports about problems on your site.
|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".
|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.
|The XFO header was not sent but frame-ancestors in Content Security Policy was used instead.