HomeFeaturesGuidesBlogResultsAPISign Up
← All Results
Domain History

kgare.co.bw

Grade F · 1/100 · 1/7 security headers present

Security Score

F
1/ 100

Security Headers

1/ 7

CSP Violations

NoViolations

Issues Found

18Issues

Recommendations

9Available

Security

1 / 100

Critical security vulnerabilities — CSP provides minimal protection.

Compliance

28 / 100

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

Best Practices

27 / 100

Best practices largely absent — review CSP configuration.

CSP Analysis

Content Security PolicyHIGH
default-src 'self' 'unsafe-inline' 'unsafe-eval' data: ; img-src 'self' data: secure.gravatar.com www.gravatar.com; report-uri https://www.kgare.co.bw;
Directive Analysis
default-srcHIGH
self unsafe-inline unsafe-eval data:
•Unsafe inline execution allowed in default-src
•Unsafe eval() execution allowed in default-src
•CRITICAL: 'data:' URI in default-src allows arbitrary JavaScript execution
img-srcLOW
self data: secure.gravatar.com www.gravatar.com
•Info: 'data:' URI in img-src
report-uriLOW
https://www.kgare.co.bw
•Deprecated: 'report-uri' is deprecated in CSP Level 3. Use 'report-to' directive instead.
Missing Directives
⚠CRITICALMissing CRITICAL directive script-src (JavaScript source control)
⚠HIGHMissing HIGH directive object-src (Plugin control - should be 'none')
⚠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)
⚠MEDIUMMissing MEDIUM directive style-src (Stylesheet source control)
⚠MEDIUMMissing MEDIUM directive font-src (Font source control)

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-OptionsPresent

nosniff

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

✗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.

5 recommended security headers are missing on kgare.co.bw.

Issues Found

  • •CRITICAL: 'data:' URI in default-src allows arbitrary JavaScript executioncritical
  • •Deprecated: 'report-uri' is deprecated in CSP Level 3. Use 'report-to' directive instead.info
  • •Info: 'data:' URI in img-srcinfo
  • •Missing CRITICAL directive script-src (JavaScript source control)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 connect-src (API/XHR control - prevents data exfiltration)medium
  • •Missing MEDIUM directive font-src (Font source control)medium
  • •Missing MEDIUM directive form-action (Form submission control - prevents form hijacking)medium
  • •Missing MEDIUM directive style-src (Stylesheet source control)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-Frame-Optionsmedium
  • •Unsafe eval() execution allowed in default-srchigh
  • •Unsafe inline execution allowed in default-srchigh

Recommendations

  • →Add base-uri directive with appropriate restrictions
  • →Add connect-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
  • →Add script-src directive with appropriate restrictions
  • →Add style-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 kgare.co.bwWeak headers often come with other exposure — check the full picture.
See full exposure report on OSN →Free, no signup.

kgare.co.bw

4 scans since 6/30/2026

F

Latest: 1/100

Total Scans

4

Latest Score

1/100

First Scan

6/30/2026

Last Scan

6/30/2026

Security

1 / 100

Critical security vulnerabilities — CSP provides minimal protection.

Compliance

28 / 100

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

Best Practices

27 / 100

Best practices largely absent — review CSP configuration.

Score Trend

Security score progression over 4 scans

Scan History

DateScoreCSPHeadersIssuesAction
Jun 30, 2026
F (1)
Yes
1/718View →
Jun 30, 2026
F (1)
Yes
1/718View →
Jun 30, 2026
F (1)
Yes
1/718View →
Jun 30, 2026
F (0)
Yes
1/718View →

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.

HeaderTest security grade: F (1/100) for kgare.co.bw
HTML
<a href="https://headertest.com/results/kgare.co.bw" title="Security headers grade for kgare.co.bw — HeaderTest">
  <img src="https://headertest.com/api/badge/kgare.co.bw" alt="HeaderTest security grade: F (1/100) for kgare.co.bw" />
</a>
Markdown
[![HeaderTest security grade: F (1/100) for kgare.co.bw](https://headertest.com/api/badge/kgare.co.bw)](https://headertest.com/results/kgare.co.bw)