Skip to content

HTTP Headers: shorelinebeacon.com

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
Alt-Svc
Transfer-Encoding
Via
access-control-allow-origin
cache-control
content-encoding
content-security-policy
content-type
date
expires
last-modified
permissions-policy
referrer-policy
server
strict-transport-security
vary
x-content-type-options
x-dcs-cache-page
x-envoy-decorator-operation
x-envoy-upstream-service-time
x-frame-options
x-pmd-backend
x-pmd-cache
â„šī¸ 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.

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