www.topview.ai
Grade F · 0/100 · 5/7 security headers present
Security Score
Security Headers
CSP Violations
Issues Found
Recommendations
Security
0 / 100Critical security vulnerabilities — CSP provides minimal protection.
Compliance
70 / 100Mostly compliant but some directives or headers are missing.
Best Practices
20 / 100Best practices largely absent — review CSP configuration.
CSP Analysis
default-src 'self' * blob: data: http: https:; style-src 'unsafe-inline' * blob: data: http: https:; script-src-elem 'unsafe-inline' * blob: data: http: https:; script-src 'unsafe-inline' 'unsafe-eval' * blob: data: http: https:; worker-src * blob: data: http: https:; font-src 'self' * blob: data: http: https:; img-src 'self' * blob: data: http: https:; frame-ancestors 'self' https://*.jkp6puff.uat.jeekup.top https://*.puffmedia.co https://topview-dashboard-preview.vercel.app https://*.topview-dashboard-preview.vercel.app;
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 valuestrict-origin-when-cross-origin
Controls how much referrer information is sent with requests, preventing data leaks to third parties.
max-age=63072000; 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.
DENY
Prevents the page from being embedded in iframes, protecting against clickjacking attacks.
1; mode=block
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 www.topview.ai.
Issues Found
- •CRITICAL: 'data:' URI in default-src allows arbitrary JavaScript executioncritical
- •CRITICAL: 'data:' URI in script-src allows arbitrary JavaScript executioncritical
- •CRITICAL: 'data:' URI in script-src-elem allows arbitrary JavaScript executioncritical
- •CRITICAL: 'https:' in default-src allows scripts from ANY HTTPS domaincritical
- •CRITICAL: 'https:' in font-src allows scripts from ANY HTTPS domaincritical
- •CRITICAL: 'https:' in img-src allows scripts from ANY HTTPS domaincritical
- •CRITICAL: 'https:' in script-src allows scripts from ANY HTTPS domaincritical
- •CRITICAL: 'https:' in script-src-elem allows scripts from ANY HTTPS domaincritical
- •CRITICAL: 'https:' in style-src allows scripts from ANY HTTPS domaincritical
- •CRITICAL: 'https:' in worker-src allows scripts from ANY HTTPS domaincritical
- •CRITICAL: Bare wildcard (*) in default-src allows ANY sourcecritical
- •CRITICAL: Bare wildcard (*) in font-src allows ANY sourcecritical
- •CRITICAL: Bare wildcard (*) in img-src allows ANY sourcecritical
- •CRITICAL: Bare wildcard (*) in script-src allows ANY sourcecritical
- •CRITICAL: Bare wildcard (*) in script-src-elem allows ANY sourcecritical
- •CRITICAL: Bare wildcard (*) in style-src allows ANY sourcecritical
- •CRITICAL: Bare wildcard (*) in worker-src allows ANY sourcecritical
- •HIGH RISK: 'blob:' URI in default-src allows script execution from dynamic blobshigh
- •HIGH RISK: 'blob:' URI in script-src allows script execution from dynamic blobshigh
- •HIGH RISK: 'blob:' URI in script-src-elem allows script execution from dynamic blobshigh
- •Info: 'blob:' URI in font-srcinfo
- •Info: 'blob:' URI in img-srcinfo
- •Info: 'blob:' URI in style-srcinfo
- •Info: 'blob:' URI in worker-srcinfo
- •Info: 'data:' URI in font-srcinfo
- •Info: 'data:' URI in img-srcinfo
- •Info: 'data:' URI in style-srcinfo
- •Info: 'data:' URI in worker-srcinfo
- •Insecure HTTP source allowed in default-srcmedium
- •Insecure HTTP source allowed in font-srcmedium
- •Insecure HTTP source allowed in img-srcmedium
- •Insecure HTTP source allowed in script-srcmedium
- •Insecure HTTP source allowed in script-src-elemmedium
- •Insecure HTTP source allowed in style-srcmedium
- •Insecure HTTP source allowed in worker-srcmedium
- •Missing HIGH directive base-uri (Base URI control - prevents base tag injection)high
- •Missing HIGH directive object-src (Plugin control - should be 'none')high
- •Missing MEDIUM directive connect-src (API/XHR control - prevents data exfiltration)medium
- •Missing MEDIUM directive form-action (Form submission control - prevents form hijacking)medium
- •Missing security header: Cross-Origin-Opener-Policymedium
- •Missing security header: Permissions-Policymedium
- •No nonces or hashes used for script-srcmedium
- •Overly permissive default-src directivehigh
- •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 script-src-elemhigh
- •Unsafe inline execution allowed in style-srchigh
Recommendations
- →Add base-uri directive with appropriate restrictions
- →Add connect-src directive with appropriate restrictions
- →Add form-action directive with appropriate restrictions
- →Add object-src directive with appropriate restrictions
- →Consider implementing a stricter Content Security Policy
- →Replace wildcards (*) with specific source lists
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.topview.ai
1 scan since 5/29/2026
Latest: 0/100
Total Scans
1
Latest Score
0/100
First Scan
5/29/2026
Last Scan
5/29/2026
Security
0 / 100Critical security vulnerabilities — CSP provides minimal protection.
Compliance
70 / 100Mostly compliant but some directives or headers are missing.
Best Practices
20 / 100Best practices largely absent — review CSP configuration.
Scan History
| Date | Score | CSP | Headers | Issues | Action |
|---|---|---|---|---|---|
| May 29, 2026 | F (0) | Yes | 5/7 | 48 | 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.topview.ai" title="Security headers grade for www.topview.ai — HeaderTest">
<img src="https://headertest.com/api/badge/www.topview.ai" alt="HeaderTest security grade: F (0/100) for www.topview.ai" />
</a>[](https://headertest.com/results/www.topview.ai)