Skip to content

HTTP Headers: commissioning.org

Security score: 0/100

đŸ›Ąī¸ Security Headers
HeaderStatus
Strict-Transport-Security❌ Missing
Content-Security-Policy❌ Missing
X-Content-Type-Options❌ Missing
X-Frame-Options❌ Missing
X-XSS-Protection❌ Missing
📋 All Response Headers
Date
Content-Type
Connection
Server
Vary
Access-Control-Allow-Headers
Access-Control-Allow-Methods
Cf-Edge-Cache
Content-Security-Policy
Cross-Origin-Embedder-Policy
Cross-Origin-Embedder-Policy-Report-Only
Cross-Origin-Opener-Policy
Cross-Origin-Opener-Policy-Report-Only
Cross-Origin-Resource-Policy
Link
Permissions-Policy
Referrer-Policy
Strict-Transport-Security
X-Content-Security-Policy
X-Content-Type-Options
X-Frame-Options
X-Permitted-Cross-Domain-Policies
X-Powered-By
X-Xss-Protection
X-Cacheable
Cache-Control
X-Cache
X-Cache-Group
cf-cache-status
Content-Encoding
CF-RAY
alt-svc
â„šī¸ About HTTP Security Headers

Strict-Transport-Security (HSTS) forces browsers to use HTTPS. Content-Security-Policy (CSP) prevents XSS attacks by controlling which resources can load. X-Content-Type-Options stops MIME-type sniffing. X-Frame-Options blocks clickjacking by preventing iframe embedding.

commissioning.org's security score of 0/100 reflects how many of these protective headers are configured. Higher scores indicate better defense against common web attacks.