telekom.hu

Readiness by lane

Green: telekom.hu. Thin bar: Telecommunications & Internet peer median.

Priority fixes for telekom.hu

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

1. Priority 1 · Harden

   HSTS kept for at least a year

   Observed: Strict-Transport-Security was sent with a max-age of 183 days, below the one-year benchmark.

   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 · Harden

   DMARC policy enforces quarantine or reject

   Observed: The DMARC policy for telekom.hu was p=none, which asks receivers to take no action on failing mail.

   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.

   59% of Telecommunications & Internet peers do this.

   Guide: A Practical Website Health Check for Owners

3. Priority 3 · Accelerate

   Modern image formats in use

   Observed: The homepage had 26 images and none used WebP or AVIF.

   What to do: Serve WebP or AVIF with a JPEG or PNG fallback, either through an image CDN or by generating both formats at build time.

   52% of Telecommunications & Internet peers do this.

   Guide: AVIF, WebP, JPEG, and PNG: Choose the Right Image Format

4. Priority 4 · Accelerate

   Static files cached for 30 days or more

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

   41% of Telecommunications & Internet peers do this.

   Guide: Browser Caching Guide for Website Owners

What telekom.hu already does well

Practices fewer than half of Telecommunications & Internet peers use.

• Reachable over IPv6IPv6 address published.33% of peers
• No render-blocking scripts in <head>Head scripts load without blocking.37% of peers

What we saw

Homepage checked

https://www.telekom.hu/

Homepage response

HTTP 200, after 1 redirect

TLS

TLSv1.3, HTTP/2

Certificate

SSL2BUY EMEA LLC, 198-day validity, expiring 2027-05-05

DNS operators

1 self-run or other nameserver domain

HSTS

max-age 183 days, includeSubDomains

DMARC policy

p=none

Homepage HTML

97 KB, gzip

Images on homepage

26 (jpg 48, png 24, svg 13)

Limits: homepage only, one location, one moment. Header checks reflect the homepage response; other pages may differ.

All 31 checks

Select a gap for the method and fix. How each check works

Compare with other Telecommunications & Internet sites

• play.pl62
• pldthome.com62
• telcel.com62
• tracfone.com62
• u.com.my62

Telecommunications & Internet readiness benchmark