Domain History

dhima.net

Grade B · 70/100 · 6/7 security headers present

Security Score

70/ 100

Security Headers

6/ 7

CSP Violations

NoViolations

Issues Found

10Issues

Recommendations

4Available

Security

70 / 100

Good security foundation but some CSP hardening recommended.

Compliance

73 / 100

Mostly compliant but some directives or headers are missing.

Best Practices

69 / 100

Basic practices followed but missing important optimizations.

CSP Analysis

Content Security PolicyHIGH

default-src 'self'; base-uri 'none'; object-src 'none'; require-trusted-types-for 'script'; font-src 'self'; img-src 'self' data:; script-src 'strict-dynamic' 'nonce-rAnd0m123' 'unsafe-inline' https:;; style-src 'self'; report-uri https://dhima.net;

Directive Analysis

default-srcLOW

self

base-uriLOW

none

object-srcLOW

none

require-trusted-types-forLOW

script

font-srcLOW

self

img-srcLOW

self data:

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

script-srcHIGH

strict-dynamic nonce-rAnd0m123 unsafe-inline https:

•Unsafe inline execution allowed in script-src

•CRITICAL: 'https:' in script-src allows scripts from ANY HTTPS domain

style-srcLOW

self

report-uriLOW

https://dhima.net

•Deprecated: 'report-uri' is deprecated in CSP Level 3. Use 'report-to' directive instead.

Missing Directives

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

Strict-Dynamic Analysis

✓Properly Configured

✓'strict-dynamic' properly configured - allows trusted scripts to load dependencies securely

•Whitelist entries ["https:"]... are ignored when strict-dynamic is present (CSP3 behavior)

•DANGER: 'http:' or 'https:' scheme-source alongside strict-dynamic — older browsers that don't support strict-dynamic will fall back to allowing scripts from ANY HTTP/HTTPS origin

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

geolocation=(),midi=(),sync-xhr=(),microphone=(),camera=(),magnetometer=(),gyroscope=(),fullscreen=(self),payment=()

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

✓Referrer-PolicyPresent

strict-origin

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

✓Strict-Transport-SecurityPresent

max-age=15552000; preload

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.

1 recommended security header is missing on dhima.net.

Issues Found

•CRITICAL: 'https:' in script-src allows scripts from ANY HTTPS domaincritical
•DANGER: 'http:' or 'https:' scheme-source alongside strict-dynamic — older browsers that don't support strict-dynamic will fall back to allowing scripts from ANY HTTP/HTTPS origincritical
•Deprecated: 'report-uri' is deprecated in CSP Level 3. Use 'report-to' directive instead.info
•Info: 'data:' URI in img-srcinfo
•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
•Unsafe inline execution allowed in script-srchigh
•Whitelist entries ["https:"]... are ignored when strict-dynamic is present (CSP3 behavior)medium

Recommendations

→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 dhima.net

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

dhima.net

1 scan since 10/26/2026

Latest: 70/100

Total Scans

Latest Score

70/100

First Scan

10/26/2026

Last Scan

10/26/2026

Security

70 / 100

Good security foundation but some CSP hardening recommended.

Compliance

73 / 100

Mostly compliant but some directives or headers are missing.

Best Practices

69 / 100

Basic practices followed but missing important optimizations.

Scan History

Date	Score	CSP	Headers	Issues	Action
Oct 26, 2026	B (70)	Yes	6/7	10	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.

HeaderTest security grade: B (70/100) for dhima.net

HTML

<a href="https://headertest.com/results/dhima.net" title="Security headers grade for dhima.net — HeaderTest">
  <img src="https://headertest.com/api/badge/dhima.net" alt="HeaderTest security grade: B (70/100) for dhima.net" />
</a>

Markdown

[![HeaderTest security grade: B (70/100) for dhima.net](https://headertest.com/api/badge/dhima.net)](https://headertest.com/results/dhima.net)