uidai.gov.in

Readiness by lane

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

Priority fixes for uidai.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: Strict-Transport-Security was sent with a max-age of 186 days, below the one-year benchmark.

   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.

   On Next.js: Add the header in the headers() option of next.config.js for all routes.

   51% of Government Services peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

3. Priority 3 · Accelerate

   No render-blocking scripts in <head>

   Observed: The homepage <head> loaded 1 external script without async or defer.

   What to do: Add defer to scripts that need the DOM, async to independent ones such as analytics, or move them to the end of the body.

   On Next.js: Use the next/script component with an appropriate loading strategy.

   39% of Government Services peers do this.

   Guide: Control Third-Party Scripts Before They Control Your Page

4. Priority 4 · Harden

   Certificate lifetime of 100 days or less

   Observed: The certificate from Sectigo Limited had a 198-day validity period, longer than the 100-day maximum that applies from March 2027.

   What to do: Move to automated issuance and renewal now, while you still have time to test it.

   34% of Government Services peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

What uidai.gov.in already does well

Practices fewer than half of Government Services peers use.

• Modern image formats in useWebP or AVIF images detected.15% of peers
• Structured data presentJSON-LD structured data found.15% of peers
• CAA records limit who can issue certificatesCAA limits issuance to digicert.com, emsign.com, pki.goog and others.17% of peers

What we saw

Homepage checked

https://uidai.gov.in/

Homepage response

HTTP 200, after 1 redirect

TLS

TLSv1.3, http/1.1

Certificate

Sectigo, 198-day validity, expiring 2027-05-07

Platform or framework

Next.js

DNS operators

1 self-run or other nameserver domain

HSTS

max-age 186 days, includeSubDomains

DMARC policy

p=reject

Homepage HTML

545 KB, gzip

Images on homepage

67 (svg 44, webp 37, png 6)

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

• bls.gov71
• cnj.jus.br71
• diia.gov.ua72
• ontario.ca73
• pishkhan24.com73

Government Services readiness benchmark