HTTP Headers: corona.cl

Security score: 0/100

🛡️ Security Headers

Header	Status
Strict-Transport-Security	❌ Missing
Content-Security-Policy	❌ Missing
X-Content-Type-Options	❌ Missing
X-Frame-Options	❌ Missing
X-XSS-Protection	❌ Missing

📋 All Response Headers

Age
Cache-Control
Connection
Content-Encoding
Content-Type
Date
ETag
Link
Set-Cookie
Strict-Transport-Security
Vary
Via
X-Amz-Cf-Id
X-Amz-Cf-Pop
X-Cache
X-Frame-Options
X-Powered-By-VTEX-Cache
X-Router-Cache
X-VTEX-Cache-Server
X-VTEX-Cache-Status
X-VTEX-Cache-Time
X-VTEX-Janus-Router-Backend-App
X-Vtex-Io-Cluster-Id
X-Vtex-Router-Elapsed-Time
X-Vtex-Router-Version
x-vtex-etag-control
x-vtex-product
x-vtex-renderer

ℹ️ 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.

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

🔧 More Tools for Corona

📊 Full Analysis 📋 WHOIS Lookup 🌐 DNS Records 🔒 SSL Certificate ⬆️ Uptime Status 📑 Full Report