ipindiaonline.gov.in

Readiness by lane

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

Priority fixes for ipindiaonline.gov.in

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

1. Priority 1 · Accelerate

   HTML compressed

   Observed: The homepage HTML (21 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.

   Guide: How to Set a Website Performance Budget That Teams Can Keep

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

   Guide: CDN Guide for Website Owners

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

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.

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

What ipindiaonline.gov.in already does well

Practices fewer than half of Government Services peers use.

• CAA records limit who can issue certificatesCAA limits issuance to emsign.com.17% of peers
• Nameservers spread across providersNameservers spread across more than one operator.25% of peers
• Certificate lifetime of 100 days or lessShort-lived 89-day certificate from eMudhra Technologies Limited, already inside the 2027 limit.34% of peers

What we saw

Homepage checked

https://ipindiaonline.gov.in/

Homepage response

HTTP 200, after 1 redirect

TLS

TLSv1.3, http/1.1

Certificate

eMudhra Technologies Limited, 89-day validity, expiring 2027-01-13

DNS operators

4 self-run or other nameserver domains

DMARC policy

p=reject

Homepage HTML

21 KB, uncompressed

Images on homepage

6 (gif 3, jpg 1, png 1)

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

All 31 checks

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

Compare with other Government Services sites

• admission.gov.sd35
• bps.gub.uy35
• entdata.co.in35
• myspike.my35
• rcomunicipios.pr.gov.br35

Government Services readiness benchmark