cherrywedding.de
Grade F · 0/100 · 4/7 security headers present
Security Score
Security Headers
CSP Violations
Issues Found
Recommendations
Security
0 / 100Critical security vulnerabilities — CSP provides minimal protection.
Compliance
0 / 100Non-compliant — CSP implementation is incomplete or report-only.
Best Practices
0 / 100Best practices largely absent — review CSP configuration.
CSP Analysis
This site does not set a Content-Security-Policy HTTP header. Without CSP, browsers allow all inline scripts, eval(), and resources from any origin, leaving the site vulnerable to Cross-Site Scripting (XSS) attacks.
Security Headers
same-origin
Isolates the browsing context to prevent Spectre-type side-channel attacks and cross-origin window manipulation.
Restricts which browser features (camera, microphone, geolocation) the page can use, limiting attack surface.
How to add it:
add_header Permissions-Policy "camera=(), microphone=(), geolocation=()" always;Header always set Permissions-Policy "camera=(), microphone=(), geolocation=()"Rules > Transform Rules > HTTP Response Header Modification > Set Permissions-Policy valueno-referrer
Controls how much referrer information is sent with requests, preventing data leaks to third parties.
max-age=31536000; includeSubDomains
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.
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 cherrywedding.de.
Issues Found
- •No Content Security Policy (CSP) header detected - site is vulnerable to XSS attackscritical
- •Without CSP, browsers allow all inline scripts, eval(), and resources from any origincritical
- •Missing security header: X-XSS-Protectionmedium
- •Missing security header: Permissions-Policymedium
- •Missing security header: X-Frame-Optionsmedium
Recommendations
- →Implement a Content Security Policy header to protect against XSS and data injection attacks
- →Start with a report-only policy (Content-Security-Policy-Report-Only) to identify required resources before enforcing
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.
cherrywedding.de
6 scans since 6/25/2026
Latest: 0/100
Total Scans
6
Latest Score
0/100
First Scan
6/25/2026
Last Scan
6/25/2026
Security
0 / 100Critical security vulnerabilities — CSP provides minimal protection.
Compliance
0 / 100Non-compliant — CSP implementation is incomplete or report-only.
Best Practices
0 / 100Best practices largely absent — review CSP configuration.
Score Trend
Security score progression over 6 scans
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/cherrywedding.de" title="Security headers grade for cherrywedding.de — HeaderTest">
<img src="https://headertest.com/api/badge/cherrywedding.de" alt="HeaderTest security grade: F (0/100) for cherrywedding.de" />
</a>[](https://headertest.com/results/cherrywedding.de)