Security Report Summary
C
Site: https://stavropolnews.ru/
IP Address: 94.228.120.123
Report Time: 24 Apr 2024 00:19:56 UTC
Headers:
  • X-Frame-Options
  • X-Content-Type-Options
  • Content-Security-Policy
  • Strict-Transport-Security
  • Referrer-Policy
  • Permissions-Policy
Advanced:
Not bad… Maybe you should perform a deeper security analysis of your website and APIs:
Missing Headers
Strict-Transport-SecurityHTTP 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. Recommended value "Strict-Transport-Security: max-age=31536000; includeSubDomains".Note that CSP frame-ancestors is used but the value is considered too lax to substitue for XFO.
Referrer-PolicyReferrer 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.Note that CSP frame-ancestors is used but the value is considered too lax to substitue for XFO.
Permissions-PolicyPermissions Policy is a new header that allows a site to control which features and APIs can be used in the browser.Note that CSP frame-ancestors is used but the value is considered too lax to substitue for XFO.
Warnings
X-Frame-OptionsThere was a duplicate X-Frame-Options header.
Raw Headers
HTTP/1.1200 OK
Servernginx/1.20.2
DateWed, 24 Apr 2024 00:19:56 GMT
Content-Typetext/html; charset=utf-8
Transfer-Encodingchunked
Connectionkeep-alive
X-Powered-ByPHP/7.4.33
ExpiresSun, 19 Nov 1978 05:00:00 GMT
Cache-Controlno-cache, must-revalidate
Content-Languageru
X-Frame-OptionsDENY
X-Content-Type-Optionsnosniff
Link<https://stavropolnews.ru/>; rel="canonical"
VaryAccept-Encoding
Content-Encodinggzip
Access-Control-Allow-Origin*
Access-Control-Allow-Headersorigin, x-requested-with, content-type
Access-Control-Allow-MethodsPUT, GET, POST, DELETE, OPTIONS
Content-Security-Policyframe-ancestors 'self' aviso.bz chrome-extension://*
X-Frame-OptionsSAMEORIGIN
X-Content-Security-Policyallow 'self';
Upcoming Headers
Cross-Origin-Embedder-PolicyCross-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-PolicyCross-Origin Opener Policy allows a site to opt-in to Cross-Origin Isolation in the browser.
Cross-Origin-Resource-PolicyCross-Origin Resource Policy allows a resource owner to specify who can load the resource.
Additional Information
ServerThis Server header seems to advertise the software being run on the server but you can remove or change this value.
X-Powered-ByX-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 should be removed or the value changed.
X-Frame-OptionsX-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-OptionsX-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".
Access-Control-Allow-OriginThis is a very lax CORS policy. Such a policy should only be used on a public CDN.
Content-Security-PolicyContent 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-Frame-OptionsX-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-Security-PolicyX 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.