trade.multibank.io
Grade F · 0/100 · 2/7 security headers present
Security Score
Security Headers
CSP Violations
Issues Found
Recommendations
Security
0 / 100Critical security vulnerabilities — CSP provides minimal protection.
Compliance
42 / 100Major compliance issues — missing critical directives and headers.
Best Practices
5 / 100Best practices largely absent — review CSP configuration.
CSP Analysis
style-src * 'unsafe-inline'; connect-src * 'self' https://*.checkout.com; frame-src * 'self' blob: https://*.checkout.com; script-src * 'self' 'unsafe-eval' 'unsafe-inline' 'wasm-unsafe-eval' https://*.checkout.com; img-src * 'self' data: blob: https://*.checkout.com; worker-src 'self' blob:
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=63072000; includeSubDomains; preload
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"SAMEORIGIN
Prevents the page from being embedded in iframes, protecting against clickjacking attacks.
Legacy XSS filter for older browsers. Modern browsers use CSP instead. Set to "0" to avoid false positives.
4 recommended security headers are missing on trade.multibank.io.
Issues Found
- •CRITICAL: Bare wildcard (*) in connect-src allows ANY sourcecritical
- •CRITICAL: Bare wildcard (*) in frame-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 style-src allows ANY sourcecritical
- •Info: 'blob:' URI in frame-srcinfo
- •Info: 'blob:' URI in img-srcinfo
- •Info: 'blob:' URI in worker-srcinfo
- •Info: 'data:' URI in img-srcinfo
- •Missing CRITICAL directive default-src (Base fallback directive)critical
- •Missing HIGH directive base-uri (Base URI control - prevents base tag injection)high
- •Missing HIGH directive frame-ancestors (Framing control - prevents clickjacking)high
- •Missing HIGH directive object-src (Plugin control - should be 'none')high
- •Missing MEDIUM directive font-src (Font source control)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
- •Missing security header: Referrer-Policymedium
- •Missing security header: X-Content-Type-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 base-uri directive with appropriate restrictions
- →Add default-src directive with appropriate restrictions
- →Add font-src directive with appropriate restrictions
- →Add form-action directive with appropriate restrictions
- →Add frame-ancestors 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.
trade.multibank.io
1 scan since 9/21/2026
Latest: 0/100
Total Scans
1
Latest Score
0/100
First Scan
9/21/2026
Last Scan
9/21/2026
Security
0 / 100Critical security vulnerabilities — CSP provides minimal protection.
Compliance
42 / 100Major compliance issues — missing critical directives and headers.
Best Practices
5 / 100Best practices largely absent — review CSP configuration.
Scan History
| Date | Score | CSP | Headers | Issues | Action |
|---|---|---|---|---|---|
| Sep 21, 2026 | F (0) | Yes | 2/7 | 24 | 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/trade.multibank.io" title="Security headers grade for trade.multibank.io — HeaderTest">
<img src="https://headertest.com/api/badge/trade.multibank.io" alt="HeaderTest security grade: F (0/100) for trade.multibank.io" />
</a>[](https://headertest.com/results/trade.multibank.io)