isro.gov.in

Readiness by lane

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

Priority fixes for isro.gov.in

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

1. Priority 1 · Harden

   HSTS kept for at least a year

   Observed: Strict-Transport-Security was sent with a max-age of 180 days, below the one-year benchmark.

   Why it matters: HSTS tells browsers to use HTTPS for your host on every later visit, which removes the window where a first HTTP request can be intercepted.

   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 Cloudflare: Enable HSTS under SSL/TLS > Edge Certificates > HTTP Strict Transport Security and raise max-age gradually.

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

   Guide: HTTPS and TLS Guide for Website Owners

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

3. Priority 3 · Accelerate

   Static files cached for 30 days or more

   Observed: A same-site stylesheet or script was cacheable for 4 hours, 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.

   On Cloudflare: Use Cache Rules to set edge and browser TTLs for static file paths.

   30% of Government Services peers do this.

   Guide: Browser Caching Guide for Website Owners

4. Priority 4 · Enable

   XML sitemap discoverable

   Observed: No sitemap was listed in robots.txt or found at /sitemap.xml.

   What to do: Generate an XML sitemap of canonical URLs, reference it in robots.txt and submit it in Google Search Console.

   42% of Government Services peers do this.

   Guide: XML Sitemap Guide: Include Only URLs You Stand Behind

What isro.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
• CAA records limit who can issue certificatesCAA limits issuance to digicert.com, entrust.net, letsencrypt.org.17% of peers
• Nameservers spread across providersNameservers spread across more than one operator.25% of peers

What we saw

Homepage checked

https://www.isro.gov.in/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

Let's Encrypt, 89-day validity, expiring 2026-11-30

CDN or edge

Cloudflare

DNS operators

ClouDNS, plus 1 self-run or other nameserver domain

HSTS

max-age 180 days, preload

DMARC policy

p=quarantine

Homepage HTML

349 KB, br

Images on homepage

78 (webp 91, gif 10, png 1)

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

• ctet.nic.in62
• goias.gov.br62
• mppe.gob.ve62
• najah.iq62
• sssalud.gob.ar63

Government Services readiness benchmark