delhipolice.gov.in

Readiness by lane

Green: delhipolice.gov.in. Thin bar: Government Services peer median.

Priority fixes for delhipolice.gov.in

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

1. Priority 1 · Accelerate

   HTTP/2 negotiated

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

   Why it matters: HTTP/2 sends many files over one connection, which speeds up pages with lots of images, styles and scripts.

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

   55% of Government Services peers do this. Limit: Certificate and protocol were observed from one vantage point; CDNs can present different certificates by region.

   Guide: CDN Guide for Website Owners

2. Priority 2 · Harden

   HSTS kept for at least a year

   Observed: The homepage response did not include a Strict-Transport-Security header.

   What to do: Send Strict-Transport-Security on HTTPS responses. Start with a short max-age (for example 300 seconds), confirm every subdomain works over HTTPS, then raise it in steps to 31536000. Add includeSubDomains only when all subdomains are HTTPS. HSTS preload is optional and hard to undo; hstspreload.org itself does not recommend it by default.

   51% of Government Services peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

3. Priority 3 · 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.

   Guide: Robots.txt Guide: Control Crawling Without Hiding Mistakes

4. Priority 4 · Accelerate

   Static files cached for 30 days or more

   Observed: A same-site stylesheet or script was cacheable for no max-age, short of the 30-day benchmark.

   What to do: Give versioned (fingerprinted) CSS, JavaScript, fonts and images Cache-Control: public, max-age=31536000, immutable, and change the file name whenever the content changes.

   30% of Government Services peers do this.

   Guide: Browser Caching Guide for Website Owners

What delhipolice.gov.in already does well

Practices fewer than half of Government Services peers use.

• CAA records limit who can issue certificatesCAA limits issuance to digicert.com.17% of peers
• Nameservers spread across providersNameservers spread across more than one operator.25% of peers
• Offscreen images lazy-loadedNative lazy loading in use.36% of peers

What we saw

Homepage checked

https://delhipolice.gov.in/

Homepage response

HTTP 200

TLS

TLSv1.3

Certificate

DigiCert, 198-day validity, expiring 2027-03-13

DNS operators

4 self-run or other nameserver domains

DMARC policy

p=reject

Homepage HTML

132 KB, gzip

Images on homepage

80 (png 53, jpg 13, svg 7)

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

Compare with other Government Services sites

• buenosaires.gob.ar46
• ceir.gov.in46
• empresafacil.pr.gov.br46
• eshram.gov.in46
• udiseplus.gov.in47

Government Services readiness benchmark