medanta.org

Readiness by lane

Green: medanta.org. Thin bar: Fitness & Health peer median.

Priority fixes for medanta.org

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

1. Priority 1 · Harden

   HSTS kept for at least a year

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

   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.

   43% of Fitness & Health 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 · Accelerate

   Static files cached for 30 days or more

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

   56% of Fitness & Health peers do this.

   Guide: Browser Caching Guide for Website Owners

3. Priority 3 · Accelerate

   HTTP/3 advertised

   Observed: The homepage did not advertise HTTP/3 through an Alt-Svc header.

   What to do: Turn on HTTP/3 at your CDN. Browsers fall back to HTTP/2 automatically, so the risk is low.

   29% of Fitness & Health peers do this.

   Guide: CDN Guide for Website Owners

4. Priority 4 · Harden

   CAA records limit who can issue certificates

   Observed: No CAA record was found for medanta.org, so any public certificate authority may issue for it.

   What to do: Publish CAA records naming every CA you actually use, including the CAs your CDN uses for managed certificates. Add an iodef contact if you want reports.

   11% of Fitness & Health peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

What medanta.org already does well

Practices fewer than half of Fitness & Health peers use.

• Referrer-Policy setReferrer-Policy present.33% of peers
• Content Security Policy presentContent-Security-Policy present.38% of peers
• DMARC policy enforces quarantine or rejectDMARC policy p=reject.44% of peers

What we saw

Homepage checked

https://www.medanta.org/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

GlobalSign, 90-day validity, expiring 2026-11-23

CDN or edge

Imperva

DNS operators

Amazon Route 53

DMARC policy

p=reject

Homepage HTML

308 KB, gzip

Images on homepage

272 (svg 171, png 52, webp 39, jpg 14)

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 Fitness & Health sites

• doctor-yab.ir78
• drdr.ir78
• medicoverhospitals.in79
• minhavida.com.br78
• msdmanuals.com78

Fitness & Health readiness benchmark