claro.com.gt

Readiness by lane

Green: claro.com.gt. Thin bar: Telecommunications & Internet peer median.

Priority fixes for claro.com.gt

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.

   54% of Telecommunications & Internet 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

   Offscreen images lazy-loaded

   Observed: The homepage had 18 images and none used loading="lazy".

   What to do: Add loading="lazy" to images below the fold. Do not lazy-load the main hero image, because that delays the largest visible element.

   66% of Telecommunications & Internet peers do this.

   Guide: Lazy Loading Without Broken Pages

3. Priority 3 · Harden

   X-Content-Type-Options: nosniff

   Observed: The homepage response did not include X-Content-Type-Options: nosniff.

   What to do: Send X-Content-Type-Options: nosniff on all responses and make sure each file is served with the correct Content-Type.

   64% of Telecommunications & Internet peers do this.

   Guide: A Practical Website Health Check for Owners

4. Priority 4 · Harden

   CAA records limit who can issue certificates

   Observed: No CAA record was found for claro.com.gt, 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.

   15% of Telecommunications & Internet peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

What claro.com.gt already does well

Practices fewer than half of Telecommunications & Internet peers use.

• Nameservers spread across providersNameservers spread across more than one operator.16% of peers
• Referrer-Policy setReferrer-Policy present.33% of peers
• No render-blocking scripts in <head>Head scripts load without blocking.37% of peers

What we saw

Homepage checked

https://www.claro.com.gt/

Homepage response

HTTP 200, after 1 redirect

TLS

TLSv1.3, HTTP/2

Certificate

DigiCert, 198-day validity, expiring 2027-04-07

DNS operators

3 self-run or other nameserver domains

DMARC policy

p=reject

Homepage HTML

635 KB, gzip

Images on homepage

18 (svg 10, png 4, jpg 4)

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 Telecommunications & Internet sites

• fizz.ca77
• jazztel.com77
• verizon.com79
• vodafone.nl79
• windtre.it79

Telecommunications & Internet readiness benchmark