Fetching response headers and parsing CSP, HSTS, and friends...
Fetching response headers and parsing CSP, HSTS, and friends...
Security headers for
https://www.salesforce.com/?bc=DB · status 200 · checked 5/14/2026, 11:57:45 PM · 175ms
followed 2 redirects: 301 salesforce.com/ → 302 www.salesforce.com/ → 200 www.salesforce.com/ → 200
Major gaps in defensive headers.
max-age=86400
SAMEORIGIN
nosniff
strict-origin-when-cross-origin
add_header Content-Security-Policy "default-src 'self'; object-src 'none'; base-uri 'self'; frame-ancestors 'none'" always; # Tight starting policy. Iterate by inspecting CSP-Report-Only violations on a staging branch first. add_header Permissions-Policy "camera=(), microphone=(), geolocation=(), interest-cohort=()" always; # Disables features you almost certainly do not need. Add features back inside the parens if your site does need them.
AI-assisted remediation
Wiredepth Pro sends this report to our AI engine and streams back a 30-day rollout plan tailored to salesforce.com, with provider-specific tips when we can infer them from the data. 10 playbooks per month on Pro, 100 on MSP.
Or share this URL with the team that owns the records.