← All Results
Domain History

archive.doc.sitecore.com

Grade C · 63/100 · 4/7 security headers present

Security Score

C
63/ 100

Security Headers

4/ 7

CSP Violations

NoViolations

Issues Found

11Issues

Recommendations

2Available

Security

63 / 100

Moderate security gaps found — unsafe directives or weak source restrictions.

Compliance

78 / 100

Mostly compliant but some directives or headers are missing.

Best Practices

47 / 100

Few best practices adopted — significant room for improvement.

CSP Analysis

Content Security PolicyHIGH
default-src 'self'; base-uri 'self'; object-src 'none'; frame-ancestors 'none';  script-src   'self'   'unsafe-inline'   'unsafe-eval'   https://*.sitecore.com   https://cdnjs.cloudflare.com   https://code.jquery.com   https://customer.cludo.com   https://www.googletagmanager.com   https://www.google-analytics.com;  style-src   'self'   'unsafe-inline'   https://*.sitecore.com   https://cdnjs.cloudflare.com   https://customer.cludo.com;  img-src   'self'   data:   https://*.sitecore.com   https://cdnjs.cloudflare.com   https://www.googletagmanager.com   https://www.google-analytics.com;  font-src   'self'   data:   https://*.sitecore.com   https://cdnjs.cloudflare.com   https://customer.cludo.com;  connect-src   'self'   https://*.sitecore.com   https://cdnjs.cloudflare.com   https://customer.cludo.com   https://www.googletagmanager.com   https://www.google-analytics.com   https://analytics.google.com   https://*.google-analytics.com;  frame-src   'self'   https://*.sitecore.com;
Directive Analysis
default-srcLOW
self
base-uriLOW
self
object-srcLOW
none
frame-ancestorsLOW
none
script-srcHIGH
self unsafe-inline unsafe-eval https://*.sitecore.com https://cdnjs.cloudflare.com https://code.jquery.com https://customer.cludo.com https://www.googletagmanager.com https://www.google-analytics.com
•Unsafe inline execution allowed in script-src
•Unsafe eval() execution allowed in script-src
•HIGH RISK CDN: 'cdnjs.cloudflare.com' in script-src - Hosts Angular and other libraries with JSONP/callback endpoints
•CDN: 'code.jquery.com' in script-src - Controlled source but older jQuery versions have XSS vulnerabilities
•No nonces or hashes used for script-src
⚠cdnjs.cloudflare.com: Hosts Angular and other libraries with JSONP/callback endpoints
⚠code.jquery.com: Controlled source but older jQuery versions have XSS vulnerabilities
style-srcHIGH
self unsafe-inline https://*.sitecore.com https://cdnjs.cloudflare.com https://customer.cludo.com
•Unsafe inline execution allowed in style-src
img-srcLOW
self data: https://*.sitecore.com https://cdnjs.cloudflare.com https://www.googletagmanager.com https://www.google-analytics.com
•Info: 'data:' URI in img-src
font-srcLOW
self data: https://*.sitecore.com https://cdnjs.cloudflare.com https://customer.cludo.com
•Info: 'data:' URI in font-src
connect-srcLOW
self https://*.sitecore.com https://cdnjs.cloudflare.com https://customer.cludo.com https://www.googletagmanager.com https://www.google-analytics.com https://analytics.google.com https://*.google-analytics.com
frame-srcLOW
self https://*.sitecore.com
Missing Directives
⚠MEDIUMMissing MEDIUM directive form-action (Form submission control - prevents form hijacking)

Security Headers

✗Cross-Origin-Opener-PolicyMissing

Isolates the browsing context to prevent Spectre-type side-channel attacks and cross-origin window manipulation.

How to add it:

nginx
add_header Cross-Origin-Opener-Policy "same-origin" always;
apache
Header always set Cross-Origin-Opener-Policy "same-origin"
cloudflare
Rules > Transform Rules > HTTP Response Header Modification > Set Cross-Origin-Opener-Policy to "same-origin"
✓Permissions-PolicyPresent

accelerometer=(), autoplay=(), camera=(), clipboard-read=(), clipboard-write=(), display-capture=(), geolocation=(), gyroscope=(), magnetometer=(), microphone=(), midi=(), payment=(), picture-in-picture=(), publickey-credentials-get=(), usb=(), fullscreen=(*)

Restricts which browser features (camera, microphone, geolocation) the page can use, limiting attack surface.

✓Referrer-PolicyPresent

strict-origin-when-cross-origin

Controls how much referrer information is sent with requests, preventing data leaks to third parties.

✗Strict-Transport-SecurityMissing

Forces browsers to use HTTPS for all future requests, preventing man-in-the-middle attacks and SSL stripping.

How to add it:

nginx
add_header Strict-Transport-Security "max-age=31536000; includeSubDomains; preload" always;
apache
Header always set Strict-Transport-Security "max-age=31536000; includeSubDomains; preload"
cloudflare
SSL/TLS > Edge Certificates > Enable HSTS (toggle on, set max-age to 12 months, enable includeSubDomains)
✓X-Content-Type-OptionsPresent

nosniff

Prevents browsers from MIME-sniffing responses away from the declared Content-Type, blocking drive-by downloads.

✓X-Frame-OptionsPresent

DENY

Prevents the page from being embedded in iframes, protecting against clickjacking attacks.

—X-XSS-ProtectionDeprecated

Legacy XSS filter for older browsers. Modern browsers use CSP instead. Set to "0" to avoid false positives.

2 recommended security headers are missing on archive.doc.sitecore.com.

Issues Found

  • •CDN: 'code.jquery.com' in script-src - Controlled source but older jQuery versions have XSS vulnerabilitieslow
  • •HIGH RISK CDN: 'cdnjs.cloudflare.com' in script-src - Hosts Angular and other libraries with JSONP/callback endpointshigh
  • •Info: 'data:' URI in font-srcinfo
  • •Info: 'data:' URI in img-srcinfo
  • •Missing MEDIUM directive form-action (Form submission control - prevents form hijacking)medium
  • •Missing security header: Cross-Origin-Opener-Policymedium
  • •Missing security header: Strict-Transport-Securitymedium
  • •No nonces or hashes used for script-srcmedium
  • •Unsafe eval() execution allowed in script-srchigh
  • •Unsafe inline execution allowed in script-srchigh
  • •Unsafe inline execution allowed in style-srchigh

Recommendations

  • →Add form-action directive with appropriate restrictions
  • →Consider implementing a stricter Content Security Policy

Beyond headers: infrastructure exposure

via OSN, our sister project

Security headers protect the browser. OSN maps what's exposed underneath — servers, open ports, known CVEs, DNS and WHOIS.

See what the internet sees about archive.doc.sitecore.com

archive.doc.sitecore.com

1 scan since 5/18/2026

C

Latest: 63/100

Total Scans

1

Latest Score

63/100

First Scan

5/18/2026

Last Scan

5/18/2026

Security

63 / 100

Moderate security gaps found — unsafe directives or weak source restrictions.

Compliance

78 / 100

Mostly compliant but some directives or headers are missing.

Best Practices

47 / 100

Few best practices adopted — significant room for improvement.

Scan History

DateScoreCSPHeadersIssuesAction
May 18, 2026
C (63)
Yes
4/711View →

Show off your security grade

Embed this badge on your site or README. It updates automatically after each scan and links back to this report.

HeaderTest security grade: C (63/100) for archive.doc.sitecore.com
HTML
<a href="https://headertest.com/results/archive.doc.sitecore.com" title="Security headers grade for archive.doc.sitecore.com — HeaderTest">
  <img src="https://headertest.com/api/badge/archive.doc.sitecore.com" alt="HeaderTest security grade: C (63/100) for archive.doc.sitecore.com" />
</a>
Markdown
[![HeaderTest security grade: C (63/100) for archive.doc.sitecore.com](https://headertest.com/api/badge/archive.doc.sitecore.com)](https://headertest.com/results/archive.doc.sitecore.com)
archive.doc.sitecore.com Security Headers — Scan History | HeaderTest