HTTP Headers: salesforce.com

Security score: 60/100

🛡️ Security Headers

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

📋 All Response Headers

Content-Encoding
Content-Type
ETag
Origin-Agent-Cluster
Referrer-Policy
X-Content-Type-Options
X-Dns-Prefetch-Control
X-Download-Options
X-Frame-Options
X-Permitted-Cross-Domain-Policies
X-Sfdc-Agent-Cohort-Apply-Experiment
X-Sfdc-Agent-Cohort-Decision
X-Sfdc-Agent-Cohort-Source
X-Xss-Protection
Content-Length
MPULSE_CDN_CACHE
MPULSE_ORIGIN_TIME
Cache-Control
Expires
Date
Connection
Vary
Set-Cookie
Strict-Transport-Security
AK-UUID
Server-Timing

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

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

🔧 More Tools for Salesforce

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