Domain History

beaconinformationsecurity.co.za

Grade D · 57/100 · 5/7 security headers present

Security Score

57/ 100

Security Headers

5/ 7

CSP Violations

NoViolations

Issues Found

11Issues

Recommendations

5Available

Security

57 / 100

Moderate security gaps found — unsafe directives or weak source restrictions.

Compliance

70 / 100

Mostly compliant but some directives or headers are missing.

Best Practices

25 / 100

Best practices largely absent — review CSP configuration.

CSP Analysis

Content Security PolicyHIGH

default-src 'self'; object-src 'none'; script-src 'self' 'unsafe-inline' 'unsafe-eval'; style-src 'self' 'unsafe-inline' https://googleapis.com; font-src 'self' https://gstatic.com; img-src 'self' data:;

Directive Analysis

default-srcLOW

self

object-srcLOW

none

script-srcHIGH

self unsafe-inline unsafe-eval

•Unsafe inline execution allowed in script-src

•Unsafe eval() execution allowed in script-src

•No nonces or hashes used for script-src

style-srcHIGH

self unsafe-inline https://googleapis.com

•Unsafe inline execution allowed in style-src

font-srcLOW

self https://gstatic.com

img-srcLOW

self data:

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

Missing Directives

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

⚠HIGHMissing HIGH directive frame-ancestors (Framing control - prevents clickjacking)

⚠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-PolicyPresent

same-origin

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

✓Strict-Transport-SecurityPresent

max-age=31536000; includeSubDomains

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

✓X-Content-Type-OptionsPresent

nosniff

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

✓X-Frame-OptionsPresent

SAMEORIGIN

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

✓X-XSS-ProtectionPresent

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 beaconinformationsecurity.co.za.

Issues Found

•Info: 'data:' URI in img-srcinfo
•Missing HIGH directive base-uri (Base URI control - prevents base tag injection)high
•Missing HIGH directive frame-ancestors (Framing control - prevents clickjacking)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
•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 connect-src directive with appropriate restrictions
→Add form-action directive with appropriate restrictions
→Add frame-ancestors 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 beaconinformationsecurity.co.zaWeak headers often come with other exposure — check the full picture.

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