Domain History

sandbox.billstopay.in

Grade F · 35/100 · 0/7 security headers present

Security Score

35/ 100

Security Headers

0/ 7

CSP Violations

NoViolations

Issues Found

14Issues

Recommendations

6Available

Security

35 / 100

Significant security weaknesses detected in CSP configuration.

Compliance

25 / 100

Non-compliant — CSP implementation is incomplete or report-only.

Best Practices

35 / 100

Few best practices adopted — significant room for improvement.

CSP Analysis

Content Security PolicyHIGH

script-src 'self' 'sha256-nfxawAcBuaGaLs5ybLb58v1zg7klCQLJlOmjZRjz5uM='; style-src 'self' https://fonts.googleapis.com 'unsafe-inline'; font-src 'self' https://fonts.gstatic.com data:; img-src 'self' data:; frame-ancestors 'self';

Directive Analysis

script-srcLOW

self sha256-nfxawAcBuaGaLs5ybLb58v1zg7klCQLJlOmjZRjz5uM=

style-srcHIGH

self https://fonts.googleapis.com unsafe-inline

•Unsafe inline execution allowed in style-src

font-srcLOW

self https://fonts.gstatic.com data:

•Info: 'data:' URI in font-src

img-srcLOW

self data:

•Info: 'data:' URI in img-src

frame-ancestorsLOW

self

Missing Directives

⚠CRITICALMissing CRITICAL directive default-src (Base fallback directive)

⚠HIGHMissing HIGH directive object-src (Plugin control - should be 'none')

⚠HIGHMissing HIGH directive base-uri (Base URI control - prevents base tag injection)

⚠MEDIUMMissing MEDIUM directive form-action (Form submission control - prevents form hijacking)

⚠MEDIUMMissing MEDIUM directive connect-src (API/XHR control - prevents data exfiltration)

Security Headers

✗Cross-Origin-Opener-PolicyMissing

Isolates the browsing context to prevent Spectre-type side-channel attacks and cross-origin window manipulation.

How to add it:

nginx

add_header Cross-Origin-Opener-Policy "same-origin" always;

apache

Header always set Cross-Origin-Opener-Policy "same-origin"

cloudflare

Rules > Transform Rules > HTTP Response Header Modification > Set Cross-Origin-Opener-Policy to "same-origin"

✗Permissions-PolicyMissing

Restricts which browser features (camera, microphone, geolocation) the page can use, limiting attack surface.

How to add it:

nginx

add_header Permissions-Policy "camera=(), microphone=(), geolocation=()" always;

apache

Header always set Permissions-Policy "camera=(), microphone=(), geolocation=()"

cloudflare

Rules > Transform Rules > HTTP Response Header Modification > Set Permissions-Policy value

✗Referrer-PolicyMissing

Controls how much referrer information is sent with requests, preventing data leaks to third parties.

How to add it:

nginx

add_header Referrer-Policy "strict-origin-when-cross-origin" always;

apache

Header always set Referrer-Policy "strict-origin-when-cross-origin"

cloudflare

Rules > Transform Rules > HTTP Response Header Modification > Set Referrer-Policy to "strict-origin-when-cross-origin"

✗Strict-Transport-SecurityMissing

Forces browsers to use HTTPS for all future requests, preventing man-in-the-middle attacks and SSL stripping.

How to add it:

nginx

add_header Strict-Transport-Security "max-age=31536000; includeSubDomains; preload" always;

apache

Header always set Strict-Transport-Security "max-age=31536000; includeSubDomains; preload"

cloudflare

SSL/TLS > Edge Certificates > Enable HSTS (toggle on, set max-age to 12 months, enable includeSubDomains)

✗X-Content-Type-OptionsMissing

Prevents browsers from MIME-sniffing responses away from the declared Content-Type, blocking drive-by downloads.

How to add it:

nginx

add_header X-Content-Type-Options "nosniff" always;

apache

Header always set X-Content-Type-Options "nosniff"

cloudflare

Rules > Transform Rules > Managed Transforms > Enable "Add X-Content-Type-Options header"

✗X-Frame-OptionsMissing

Prevents the page from being embedded in iframes, protecting against clickjacking attacks.

How to add it:

nginx

add_header X-Frame-Options "DENY" always;

apache

Header always set X-Frame-Options "DENY"

cloudflare

Rules > Transform Rules > HTTP Response Header Modification > Set X-Frame-Options to "DENY"

—X-XSS-ProtectionDeprecated

Legacy XSS filter for older browsers. Modern browsers use CSP instead. Set to "0" to avoid false positives.

6 recommended security headers are missing on sandbox.billstopay.in.

Issues Found

•Info: 'data:' URI in font-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 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
•Missing security header: Referrer-Policymedium
•Missing security header: Strict-Transport-Securitymedium
•Missing security header: X-Content-Type-Optionsmedium
•Missing security header: X-Frame-Optionsmedium
•Unsafe inline execution allowed in style-srchigh

Recommendations

→Add base-uri directive with appropriate restrictions
→Add connect-src directive with appropriate restrictions
→Add default-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

Beyond headers: infrastructure exposure

via OSN, our sister project

Security headers protect the browser. OSN maps what's exposed underneath — servers, open ports, known CVEs, DNS and WHOIS.

See what the internet sees about sandbox.billstopay.inWeak headers often come with other exposure — check the full picture.

See full exposure report on OSN →Free, no signup.