telkomsel.com

Readiness by lane

Green: telkomsel.com. Thin bar: Telecommunications & Internet peer median.

Priority fixes for telkomsel.com

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.

   81% of Telecommunications & Internet 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 186 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.

   54% of Telecommunications & Internet peers do this.

   Guide: HTTPS and TLS Guide for Website Owners

3. Priority 3 · Harden

   Content Security Policy present

   Observed: The homepage response did not include a Content-Security-Policy header.

   What to do: Start with Content-Security-Policy-Report-Only to see what would break, tighten the policy over a few weeks, then enforce it.

   On Drupal: The Security Kit module includes CSP settings.

   48% of Telecommunications & Internet peers do this.

   Guide: Payment Security and PCI DSS: What Website Owners Need to Know

4. Priority 4 · Enable

   Structured data present

   Observed: The homepage had no JSON-LD structured data.

   What to do: Add JSON-LD for your organization and main content types, then test it with Google's Rich Results Test.

   51% of Telecommunications & Internet peers do this.

   Guide: Structured Data Basics for Website Owners

What telkomsel.com already does well

Practices fewer than half of Telecommunications & Internet peers use.

• No render-blocking scripts in <head>Head scripts load without blocking.37% of peers
• Static files cached for 30 days or moreLong-lived caching on static files.41% of peers

What we saw

Homepage checked

https://www.telkomsel.com/

Homepage response

HTTP 200

TLS

TLSv1.2, HTTP/2

Certificate

DigiCert, 364-day validity, expiring 2026-11-16

Platform or framework

Drupal

DNS operators

1 self-run or other nameserver domain

HSTS

max-age 186 days, includeSubDomains

DMARC policy

p=quarantine

Homepage HTML

506 KB, gzip

Images on homepage

257 (png 138, svg 102, webp 39, gif 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 Telecommunications & Internet sites

• att.com69
• simyo.es70
• singtel.com70
• so-net.ne.jp70
• vodafone.pt70

Telecommunications & Internet readiness benchmark