cun.es

Readiness by lane

Green: cun.es. Thin bar: Fitness & Health peer median.

Priority fixes for cun.es

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

1. Priority 1 · Harden

   TLS 1.3 negotiated

   Observed: The TLS connection negotiated TLSv1.2.

   Why it matters: TLS 1.3 removes legacy cipher suites and completes the handshake in fewer round trips, so it is both safer and faster for new connections.

   What to do: Enable TLS 1.3 on your CDN or server. Keep TLS 1.2 available for older clients unless you have checked your audience.

   89% of Fitness & Health peers do this. Limit: Certificate and protocol were observed from one vantage point; CDNs can present different certificates by region.

   Guide: HTTPS and TLS 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 0 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.

   43% of Fitness & Health peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

3. Priority 3 · Harden

   DMARC policy enforces quarantine or reject

   Observed: No DMARC record was found at _dmarc.cun.es.

   What to do: Publish DMARC with p=none and a reporting address first, fix any legitimate senders that fail SPF or DKIM alignment, then move to quarantine and finally reject.

   44% of Fitness & Health peers do this.

   Guide: A Practical Website Health Check for Owners

4. Priority 4 · Harden

   Certificate lifetime of 100 days or less

   Observed: The certificate from Hellenic Academic and Research Institutions CA 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.

   59% of Fitness & Health peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

What cun.es already does well

Practices fewer than half of Fitness & Health peers use.

• Nameservers spread across providersNameservers spread across more than one operator.9.9% of peers
• Referrer-Policy setReferrer-Policy present.33% of peers
• Content Security Policy presentContent-Security-Policy present.38% of peers

What we saw

Homepage checked

https://www.cun.es/

Homepage response

HTTP 200

TLS

TLSv1.2, HTTP/2

Certificate

Hellenic Academic and Research Institutions CA, 198-day validity, expiring 2027-03-11

DNS operators

2 self-run or other nameserver domains

HSTS

max-age 0 days

Homepage HTML

78 KB, gzip

Images on homepage

32 (webp 14, svg 7, png 4, jpg 3)

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

• baby-calendar.jp73
• centromedicopastore.com.br73
• express-scripts.com73
• hexahealth.com73
• vinmec.com74

Fitness & Health readiness benchmark