STATUS IS UPREADINESS PROFILE

Website readiness profile · Snapshot 23 October 2026

himkosh.nic.in

himkosh.nic.in's public homepage, certificate and DNS checked against 31 practices and compared with 954 Government Services sites.

Readiness index
41/100

Government Services median 53

Ahead of
21%

of measured Government Services sites

Practices observed
11/28

3 of 31 could not be measured

Popularity band
Top 50K

Chrome UX Report top-sites list

Measured 2026-10-23 11:42:42 UTC from one location. How we measure

Readiness by lane

Green: himkosh.nic.in. Thin bar: Government Services peer median.

Enable

26/100

Peers 59

Harden

75/100

Peers 59

Accelerate

13/100

Peers 41

Recover

n/a/100

Peers 25

Priority fixes for himkosh.nic.in

Ordered by impact and by how common each practice is among peers.

  1. Priority 1 · Accelerate

    HTML compressed

    Observed: The homepage HTML (40 KB) was delivered without gzip, Brotli or zstd compression.

    Why it matters: Compression usually shrinks HTML several times over, so the first bytes of the page arrive sooner on slow connections.

    What to do: Enable Brotli or gzip for text responses (HTML, CSS, JavaScript, JSON, SVG) at the CDN or origin.

    74% of Government Services peers do this. Limit: Read from the homepage response only; other pages or regions may send different headers.

  2. Priority 2 · Harden

    TLS 1.3 negotiated

    Observed: The TLS connection negotiated TLSv1.2.

    What to do: Enable TLS 1.3 on your CDN or server. Keep TLS 1.2 available for older clients unless you have checked your audience.

    77% of Government Services peers do this.

  3. Priority 3 · Accelerate

    HTTP/2 negotiated

    Observed: The TLS handshake selected http/1.1 instead of HTTP/2.

    What to do: Enable HTTP/2 on your CDN or server. Most CDNs do this by default.

    55% of Government Services peers do this.

  4. Priority 4 · Enable

    robots.txt published

    Observed: No robots.txt file was returned at the site root.

    What to do: Publish /robots.txt with any crawl rules you need and a Sitemap: line pointing to your XML sitemap.

    61% of Government Services peers do this.

What himkosh.nic.in already does well

Practices fewer than half of Government Services peers use.

  • CAA records limit who can issue certificatesCAA limits issuance to globalsign.com.17% of peers
  • Referrer-Policy setReferrer-Policy present.39% of peers
  • No render-blocking scripts in <head>Head scripts load without blocking.39% of peers

What we saw

Homepage checked
https://himkosh.nic.in/
Homepage response
HTTP 200
TLS
TLSv1.2, http/1.1
Certificate
GlobalSign, 199-day validity, expiring 2026-12-06
HSTS
max-age 365 days, includeSubDomains
DMARC policy
p=reject
Homepage HTML
40 KB, uncompressed
Images on homepage
18 (png 12, jpg 4, gif 2)

Limits: homepage only, one location, one moment. Header checks reflect the homepage response; other pages may differ.

Stack and providers

Seen in the homepage response, certificate and DNS. Provider pages compare how their customers configure the same checks.

All 31 checks

Select a gap for the method and fix. How each check works

Observed 11

  • HSTS kept for at least a year
  • Certificate has more than 14 days left
  • CAA records limit who can issue certificates
  • DMARC policy enforces quarantine or reject
  • X-Content-Type-Options: nosniff
  • Framing restricted
  • Content Security Policy present
  • Referrer-Policy set
  • No render-blocking scripts in <head>
  • Mobile viewport configured
  • At most one redirect to the homepage

Not measured 3

  • HTTP requests move to HTTPS
  • DNSSEC signed
  • Nameservers spread across providers

Own himkosh.nic.in?

Re-run the checks after a change, or verify the site in a free workspace to save reports with history, compare against similar sites and competitors, and track a private action plan. What owners get.

Live status for this site: Status Is Down: himkosh.nic.in. This profile covers configuration only.

Compare with other Government Services sites