multireseller.myadminapp.test.aws.d4sp.com
Grade F · 33/100 · 1/7 security headers present
Security Score
Security Headers
CSP Violations
Issues Found
Recommendations
Security
33 / 100Significant security weaknesses detected in CSP configuration.
Compliance
44 / 100Major compliance issues — missing critical directives and headers.
Best Practices
35 / 100Few best practices adopted — significant room for improvement.
CSP Analysis
default-src 'none'; script-src 'self' 'unsafe-inline' 'unsafe-eval'; connect-src 'self' blob: https://*.ingest.us.sentry.io;img-src 'self' data:; font-src 'self' data:; style-src 'self' 'unsafe-inline'; media-src 'self' blob:; worker-src 'self' blob:; base-uri 'self'; form-action 'self'
Directive Analysis
Missing Directives
Security Headers
Isolates the browsing context to prevent Spectre-type side-channel attacks and cross-origin window manipulation.
How to add it:
add_header Cross-Origin-Opener-Policy "same-origin" always;Header always set Cross-Origin-Opener-Policy "same-origin"Rules > Transform Rules > HTTP Response Header Modification > Set Cross-Origin-Opener-Policy to "same-origin"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 valueControls how much referrer information is sent with requests, preventing data leaks to third parties.
How to add it:
add_header Referrer-Policy "strict-origin-when-cross-origin" always;Header always set Referrer-Policy "strict-origin-when-cross-origin"Rules > Transform Rules > HTTP Response Header Modification > Set Referrer-Policy to "strict-origin-when-cross-origin"max-age=31536000; includeSubDomains
Forces browsers to use HTTPS for all future requests, preventing man-in-the-middle attacks and SSL stripping.
Prevents browsers from MIME-sniffing responses away from the declared Content-Type, blocking drive-by downloads.
How to add it:
add_header X-Content-Type-Options "nosniff" always;Header always set X-Content-Type-Options "nosniff"Rules > Transform Rules > Managed Transforms > Enable "Add X-Content-Type-Options header"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.
5 recommended security headers are missing on multireseller.myadminapp.test.aws.d4sp.com.
Issues Found
- •Info: 'blob:' URI in connect-srcinfo
- •Info: 'blob:' URI in media-srcinfo
- •Info: 'blob:' URI in worker-srcinfo
- •Info: 'data:' URI in font-srcinfo
- •Info: 'data:' URI in img-srcinfo
- •Missing HIGH directive frame-ancestors (Framing control - prevents clickjacking)high
- •Missing HIGH directive object-src (Plugin control - should be 'none')high
- •Missing security header: Cross-Origin-Opener-Policymedium
- •Missing security header: Permissions-Policymedium
- •Missing security header: Referrer-Policymedium
- •Missing security header: X-Content-Type-Optionsmedium
- •Missing security header: X-Frame-Optionsmedium
- •No nonces or hashes used for script-srcmedium
- •RISK: 'blob:' in worker-src allows creation of workers from dynamic blob contentmedium
- •Unsafe eval() execution allowed in script-srchigh
- •Unsafe inline execution allowed in script-srchigh
- •Unsafe inline execution allowed in style-srchigh
Recommendations
- →Add frame-ancestors directive with appropriate restrictions
- →Add object-src 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.
multireseller.myadminapp.test.aws.d4sp.com
6 scans since 6/2/2026
Latest: 33/100
Total Scans
6
Latest Score
33/100
First Scan
6/2/2026
Last Scan
6/2/2026
Security
33 / 100Significant security weaknesses detected in CSP configuration.
Compliance
44 / 100Major compliance issues — missing critical directives and headers.
Best Practices
35 / 100Few best practices adopted — significant room for improvement.
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/multireseller.myadminapp.test.aws.d4sp.com" title="Security headers grade for multireseller.myadminapp.test.aws.d4sp.com — HeaderTest">
<img src="https://headertest.com/api/badge/multireseller.myadminapp.test.aws.d4sp.com" alt="HeaderTest security grade: F (33/100) for multireseller.myadminapp.test.aws.d4sp.com" />
</a>[](https://headertest.com/results/multireseller.myadminapp.test.aws.d4sp.com)