← All Results
Domain History

www.jharkhandhighcourt.nic.in

Grade C · 69/100 · 6/7 security headers present

Security Score

C
69/ 100

Security Headers

6/ 7

CSP Violations

NoViolations

Issues Found

11Issues

Recommendations

4Available

Security

69 / 100

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

Compliance

82 / 100

Mostly compliant but some directives or headers are missing.

Best Practices

10 / 100

Best practices largely absent — review CSP configuration.

CSP Analysis

Content Security PolicyHIGH
default-src 'self'; script-src 'self' 'unsafe-inline'; style-src 'self' 'unsafe-inline'; img-src 'self' data:; connect-src 'self'; font-src 'self'; object-src 'self' blob:; frame-src 'self' blob: data:;
Directive Analysis
default-srcLOW
self
script-srcHIGH
self unsafe-inline
•Unsafe inline execution allowed in script-src
•No nonces or hashes used for script-src
style-srcHIGH
self unsafe-inline
•Unsafe inline execution allowed in style-src
img-srcLOW
self data:
•Info: 'data:' URI in img-src
connect-srcLOW
self
font-srcLOW
self
object-srcLOW
self blob:
•Info: 'blob:' URI in object-src
frame-srcLOW
self blob: data:
•Info: 'blob:' URI in frame-src
•Info: 'data:' URI in frame-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)

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

camera=(), microphone=(), geolocation=(), payment=(), usb=(), magnetometer=(), gyroscope=(), accelerometer=()

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

✓Referrer-PolicyPresent

strict-origin-when-cross-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.

1 recommended security header is missing on www.jharkhandhighcourt.nic.in.

Issues Found

  • •Info: 'blob:' URI in frame-srcinfo
  • •Info: 'blob:' URI in object-srcinfo
  • •Info: 'data:' URI in frame-srcinfo
  • •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 form-action (Form submission control - prevents form hijacking)medium
  • •Missing security header: Cross-Origin-Opener-Policymedium
  • •No nonces or hashes used for script-srcmedium
  • •Unsafe inline execution allowed in script-srchigh
  • •Unsafe inline execution allowed in style-srchigh

Recommendations

  • →Add base-uri 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 www.jharkhandhighcourt.nic.in

www.jharkhandhighcourt.nic.in

1 scan since 7/20/2026

C

Latest: 69/100

Total Scans

1

Latest Score

69/100

First Scan

7/20/2026

Last Scan

7/20/2026

Security

69 / 100

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

Compliance

82 / 100

Mostly compliant but some directives or headers are missing.

Best Practices

10 / 100

Best practices largely absent — review CSP configuration.

Scan History

DateScoreCSPHeadersIssuesAction
Jul 20, 2026
C (69)
Yes
6/711View →

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: C (69/100) for www.jharkhandhighcourt.nic.in
HTML
<a href="https://headertest.com/results/www.jharkhandhighcourt.nic.in" title="Security headers grade for www.jharkhandhighcourt.nic.in — HeaderTest">
  <img src="https://headertest.com/api/badge/www.jharkhandhighcourt.nic.in" alt="HeaderTest security grade: C (69/100) for www.jharkhandhighcourt.nic.in" />
</a>
Markdown
[![HeaderTest security grade: C (69/100) for www.jharkhandhighcourt.nic.in](https://headertest.com/api/badge/www.jharkhandhighcourt.nic.in)](https://headertest.com/results/www.jharkhandhighcourt.nic.in)