www.ssl.org
Grade B · 70/100 · 7/7 security headers present
Security Score
Security Headers
CSP Violations
Issues Found
Recommendations
Security
70 / 100Good security foundation but some CSP hardening recommended.
Compliance
90 / 100CSP implementation follows recommended standards and specifications.
Best Practices
80 / 100Good practices in place but missing some important optimizations.
CSP Analysis
default-src 'self'; script-src 'nonce-H+cF6As+Va5+FXY4ZxKMqg==' 'strict-dynamic' https: http: 'unsafe-inline'; style-src 'self' 'unsafe-inline'; font-src 'self'; img-src 'self' data:; connect-src 'self' https://www.httptracker.com; object-src 'none'; base-uri 'self'; frame-ancestors 'self'; form-action 'self'
Directive Analysis
Strict-Dynamic Analysis
Security Headers
same-origin
Isolates the browsing context to prevent Spectre-type side-channel attacks and cross-origin window manipulation.
accelerometer=(), camera=(), display-capture=(), geolocation=(), gyroscope=(), magnetometer=(), microphone=(), payment=(), usb=()
Restricts which browser features (camera, microphone, geolocation) the page can use, limiting attack surface.
strict-origin-when-cross-origin
Controls how much referrer information is sent with requests, preventing data leaks to third parties.
max-age=31536000; includeSubDomains; preload
Forces browsers to use HTTPS for all future requests, preventing man-in-the-middle attacks and SSL stripping.
nosniff
Prevents browsers from MIME-sniffing responses away from the declared Content-Type, blocking drive-by downloads.
SAMEORIGIN
Prevents the page from being embedded in iframes, protecting against clickjacking attacks.
0
Legacy XSS filter for older browsers. Modern browsers use CSP instead. Set to "0" to avoid false positives.
Issues Found
- •CRITICAL: 'https:' in script-src allows scripts from ANY HTTPS domaincritical
- •DANGER: 'http:' or 'https:' scheme-source alongside strict-dynamic — older browsers that don't support strict-dynamic will fall back to allowing scripts from ANY HTTP/HTTPS origincritical
- •Info: 'data:' URI in img-srcinfo
- •Insecure HTTP source allowed in script-srcmedium
- •Unsafe inline execution allowed in script-srchigh
- •Unsafe inline execution allowed in style-srchigh
- •Whitelist entries ["https:", "http:"]... are ignored when strict-dynamic is present (CSP3 behavior)medium
Recommendations
- →Consider implementing a stricter Content Security Policy
Beyond headers: infrastructure exposure
via OSN, our sister projectSecurity headers protect the browser. OSN maps what's exposed underneath — servers, open ports, known CVEs, DNS and WHOIS.
www.ssl.org
1 scan since 6/18/2026
Latest: 70/100
Total Scans
1
Latest Score
70/100
First Scan
6/18/2026
Last Scan
6/18/2026
Security
70 / 100Good security foundation but some CSP hardening recommended.
Compliance
90 / 100CSP implementation follows recommended standards and specifications.
Best Practices
80 / 100Good practices in place but missing some important optimizations.
Scan History
| Date | Score | CSP | Headers | Issues | Action |
|---|---|---|---|---|---|
| Jun 18, 2026 | B (70) | Yes | 7/7 | 7 | View → |
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.
<a href="https://headertest.com/results/www.ssl.org" title="Security headers grade for www.ssl.org — HeaderTest">
<img src="https://headertest.com/api/badge/www.ssl.org" alt="HeaderTest security grade: B (70/100) for www.ssl.org" />
</a>[](https://headertest.com/results/www.ssl.org)