Security Report Summary
A
| Site: | https://isfsb.com/ | ||
|---|---|---|---|
| IP Address: | 47.254.197.186 | ||
| Report Time: | 02 May 2024 11:38:18 UTC | ||
| Headers: |
|
||
| Advanced: |
|
Missing Headers
| 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 |
|---|---|
| server | nginx |
| date | Thu, 02 May 2024 11:38:17 GMT |
| content-type | text/html; charset=UTF-8 |
| content-length | 28241 |
| link | <https://isfsb.com/wp-json/>; rel="https://api.w.org/", <https://isfsb.com/wp-json/wp/v2/pages/15>; rel="alternate"; type="application/json", <https://isfsb.com/>; rel=shortlink |
| referrer-policy | no-referrer-when-downgrade |
| expect-ct | max-age=7776000, enforce |
| content-security-policy | report-uri https://isfsb.com/ |
| vary | Accept-Encoding |
| content-encoding | gzip |
| cache-control | private, no-cache, no-store, proxy-revalidate, no-transform |
| expires | Thu, 27 Jun 2024 11:38:16 GMT |
| referrer-policy | strict-origin-when-cross-origin |
| x-frame-options | sameorigin |
| x-xss-protection | 1; mode=block |
| x-content-type-options | nosniff |
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
| access-control-allow-origin | null |
| access-control-allow-methods | GET,PUT,POST,DELETE |
| access-control-allow-headers | Content-Type, Authorization |
| x-content-security-policy | img-src *; media-src * data:; |
| cross-origin-embedder-policy-report-only | unsafe-none; report-to="default" |
| cross-origin-embedder-policy | unsafe-none; report-to="default" |
| cross-origin-opener-policy-report-only | same-origin; report-to="default" |
| cross-origin-opener-policy | same-origin; report-to="default" |
| cross-origin-resource-policy | cross-origin |
| strict-dynamic | https: 'self'; default-src 'self' |
| x-permitted-cross-domain-policies | none |
| pragma | no-cache |
| x-powered-by | PleskLin |
Additional Information
| server | This Server header seems to advertise the software being run on the server but you can remove or change this value. |
|---|---|
| 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 will soon be deprecated and can be removed. |
| 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. You can sign up for a free account on Report URI to collect reports about problems on your site. |
| 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. |
| 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-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. |
| 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". |
| 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. |
| x-content-security-policy | X 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. |
| cross-origin-embedder-policy-report-only | 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-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. |
| cross-origin-opener-policy-report-only | Cross-Origin Opener Policy allows a site to opt-in to Cross-Origin Isolation in the browser. |
| cross-origin-opener-policy | Cross-Origin Opener Policy allows a site to opt-in to Cross-Origin Isolation in the browser. |
| cross-origin-resource-policy | Cross-Origin Resource Policy allows a resource owner to specify who can load the resource. |
| x-powered-by | X-Powered-By can usually be seen with values like "PHP/5.5.9-1ubuntu4.5" or "ASP.NET". Trying to minimise the amount of information you give out about your server is a good idea. This header seems to have been altered to remove such information, but could still be removed. |