STATUS IS UPREADINESS PROFILE

Website readiness profile · Snapshot 23 October 2026

entel.cl

entel.cl's public homepage, certificate and DNS checked against 31 practices and compared with 285 Telecommunications & Internet sites.

Readiness index
88/100

Telecommunications & Internet median 67

Ahead of
97%

of measured Telecommunications & Internet sites

Practices observed
24/29

2 of 31 could not be measured

Popularity band
Top 10K

Chrome UX Report top-sites list

Measured 2026-10-23 12:09:56 UTC from one location. How we measure

Readiness by lane

Green: entel.cl. Thin bar: Telecommunications & Internet peer median.

Enable

100/100

Peers 82

Harden

78/100

Peers 61

Accelerate

100/100

Peers 57

Recover

0/100

Peers 16

Priority fixes for entel.cl

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

  1. Priority 1 · Harden

    X-Content-Type-Options: nosniff

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

    Why it matters: It stops browsers from guessing a file's type, which blocks a class of attacks where an uploaded file is run as a script.

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

    On Cloudflare: Add the header with a response header transform rule.

    64% of Telecommunications & Internet peers do this. Limit: Read from the homepage response only; other pages or regions may send different headers.

  2. Priority 2 · Harden

    CAA records limit who can issue certificates

    Observed: No CAA record was found for entel.cl, 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.

    On Cloudflare: Cloudflare documents which CAs its managed certificates need; include them in your CAA records.

    15% of Telecommunications & Internet peers do this.

  3. Priority 3 · Harden

    security.txt published

    Observed: No valid /.well-known/security.txt with a Contact field was returned.

    What to do: Publish /.well-known/security.txt with at least Contact and Expires fields, as RFC 9116 requires, and review it before it expires.

    On Cloudflare: Cloudflare Security Center can serve a security.txt file for the zone.

    13% of Telecommunications & Internet peers do this.

  4. Priority 4 · Harden

    DNSSEC signed

    Observed: No DS record was found for entel.cl at its parent zone, so its DNS answers are not DNSSEC-signed.

    What to do: Enable DNSSEC at your DNS provider, then add the DS record at your registrar. Plan provider moves carefully: a stale DS record can make the domain fail to resolve.

    On Cloudflare: Enable DNSSEC in DNS > Settings and add the DS record at the registrar.

    13% of Telecommunications & Internet peers do this.

What entel.cl already does well

Practices fewer than half of Telecommunications & Internet peers use.

  • HTTP/3 advertisedHTTP/3 advertised.13% of peers
  • Certificate lifetime of 100 days or lessShort-lived 90-day certificate from Google Trust Services, already inside the 2027 limit.28% of peers
  • Reachable over IPv6IPv6 address published.33% of peers

What we saw

Homepage checked
https://www.entel.cl/
Homepage response
HTTP 200
TLS
TLSv1.3, HTTP/2
Certificate
Google Trust Services, 90-day validity, expiring 2026-12-17
CDN or edge
Cloudflare
DNS operators
Amazon Route 53
HSTS
max-age 365 days, includeSubDomains
DMARC policy
p=quarantine
Homepage HTML
796 KB, br
Images on homepage
0

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

Observed 24

  • HTTP requests move to HTTPS
  • HSTS kept for at least a year
  • TLS 1.3 negotiated
  • Certificate has more than 14 days left
  • Certificate lifetime of 100 days or less
  • DMARC policy enforces quarantine or reject
  • Framing restricted
  • Content Security Policy present
  • Referrer-Policy set
  • HTTP/2 negotiated
  • HTTP/3 advertised
  • HTML compressed
  • Static files cached for 30 days or more
  • No render-blocking scripts in <head>
  • robots.txt published
  • XML sitemap discoverable
  • Reachable over IPv6
  • Canonical URL declared
  • Meta description written
  • Mobile viewport configured
  • Structured data present
  • Social preview image set
  • Page language declared
  • At most one redirect to the homepage

Not measured 2

  • Modern image formats in use
  • Offscreen images lazy-loaded

Own entel.cl?

Re-run the checks after a change, keep a private action plan in a free workspace, or report a mistake.

Live status for this site: Status Is Down: entel.cl. This profile covers configuration only.

Compare with other Telecommunications & Internet sites