sapphire.net
Grade A · 82/100 · 4/7 security headers present
Security Score
Security Headers
CSP Violations
Issues Found
Recommendations
Security
82 / 100Good security foundation but some CSP hardening recommended.
Compliance
72 / 100Mostly compliant but some directives or headers are missing.
Best Practices
33 / 100Few best practices adopted — significant room for improvement.
CSP Analysis
default-src 'self'; script-src 'self' https://ajax.cloudflare.com https://*.cookiebot.com https://fonts.googleapis.com https://*.cloudflareinsights.com https://*.googletaganager.com; object-src 'none'; font-src 'self' https://fonts.gstatic.com; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; connect-src 'self' https://*.cookiebot.com; img-src 'self' https://*.cookiebot.com; frame-src 'self' https://*.cookiebot.com; upgrade-insecure-requests;
Directive Analysis
Missing Directives
Security Headers
same-site; report-to="default";
Isolates the browsing context to prevent Spectre-type side-channel attacks and cross-origin window manipulation.
private-state-token-redemption=(self "https://www.google.com" "https://www.gstatic.com" "https://recaptcha.net" "https://challenges.cloudflare.com" "https://hcaptcha.com"), private-state-token-issuance=(self "https://www.google.com" "https://www.gstatic.com" "https://recaptcha.net" "https://challenges.cloudflare.com" "https://hcaptcha.com")
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.
Forces browsers to use HTTPS for all future requests, preventing man-in-the-middle attacks and SSL stripping.
How to add it:
add_header Strict-Transport-Security "max-age=31536000; includeSubDomains; preload" always;Header always set Strict-Transport-Security "max-age=31536000; includeSubDomains; preload"SSL/TLS > Edge Certificates > Enable HSTS (toggle on, set max-age to 12 months, enable includeSubDomains)nosniff
Prevents browsers from MIME-sniffing responses away from the declared Content-Type, blocking drive-by downloads.
Prevents the page from being embedded in iframes, protecting against clickjacking attacks.
How to add it:
add_header X-Frame-Options "DENY" always;Header always set X-Frame-Options "DENY"Rules > Transform Rules > HTTP Response Header Modification > Set X-Frame-Options to "DENY"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 sapphire.net.
Issues Found
- •Missing HIGH directive base-uri (Base URI control - prevents base tag injection)high
- •Missing HIGH directive frame-ancestors (Framing control - prevents clickjacking)high
- •Missing MEDIUM directive form-action (Form submission control - prevents form hijacking)medium
- •Missing security header: Strict-Transport-Securitymedium
- •Missing security header: X-Frame-Optionsmedium
- •No nonces or hashes used for script-srcmedium
- •Unsafe inline execution allowed in style-srchigh
Recommendations
- →Add base-uri directive with appropriate restrictions
- →Add form-action directive with appropriate restrictions
- →Add frame-ancestors directive with appropriate restrictions
- →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.
sapphire.net
10 scans since 2/16/2026
Latest: 82/100
Total Scans
10
Latest Score
82/100
First Scan
2/16/2026
Last Scan
2/23/2026
Security
82 / 100Good security foundation but some CSP hardening recommended.
Compliance
72 / 100Mostly compliant but some directives or headers are missing.
Best Practices
33 / 100Few best practices adopted — significant room for improvement.
Score Trend
Security score progression over 10 scans
Scan History
| Date | Score | CSP | Headers | Issues | Action |
|---|---|---|---|---|---|
| Feb 23, 2026 | A (82) | Yes | 4/7 | 7 | View → |
| Feb 16, 2026 | B (79) | Yes | 4/7 | 7 | View → |
| Feb 16, 2026 | B (74) | Yes | 4/7 | 8 | View → |
| Feb 16, 2026 | D (51) | Yes | 4/7 | 10 | View → |
| Feb 16, 2026 | F (0) | No | 4/7 | 5 | View → |
| Feb 16, 2026 | F (0) | No | 4/7 | 5 | View → |
| Feb 16, 2026 | D- (48) | Yes | 4/7 | 12 | View → |
| Feb 16, 2026 | D- (48) | Yes | 4/7 | 12 | View → |
| Feb 16, 2026 | D- (46) | Yes | 4/7 | 14 | View → |
| Feb 16, 2026 | D- (46) | Yes | 4/7 | 14 | 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/sapphire.net" title="Security headers grade for sapphire.net — HeaderTest">
<img src="https://headertest.com/api/badge/sapphire.net" alt="HeaderTest security grade: A (82/100) for sapphire.net" />
</a>[](https://headertest.com/results/sapphire.net)