yettel.hu

Readiness by lane

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

Priority fixes for yettel.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 · Accelerate

   Modern image formats in use

   Observed: The homepage had 35 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

3. Priority 3 · Enable

   Canonical URL declared

   Observed: The homepage did not declare a canonical URL.

   What to do: Add a self-referencing canonical link to every indexable page, using the final https:// URL.

   76% of Telecommunications & Internet peers do this.

   Guide: Canonical Tags: A Decision Guide for Duplicate URLs

4. Priority 4 · Harden

   Framing restricted

   Observed: The homepage did not send frame-ancestors or X-Frame-Options, so other sites may frame it.

   What to do: Send Content-Security-Policy: frame-ancestors 'self' (or a list of trusted origins). X-Frame-Options: SAMEORIGIN covers older browsers.

   68% of Telecommunications & Internet peers do this.

   Guide: A Practical Website Health Check for Owners

What yettel.hu already does well

Practices fewer than half of Telecommunications & Internet peers use.

• CAA records limit who can issue certificatesCAA limits issuance to amazon.com, e-szigno.hu, letsencrypt.org and others.15% of peers
• Referrer-Policy setReferrer-Policy present.33% 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.yettel.hu/

Homepage response

HTTP 200

TLS

TLSv1.3, HTTP/2

Certificate

Microsec Ltd., 198-day validity, expiring 2026-12-12

DNS operators

1 self-run or other nameserver domain

HSTS

max-age 183 days, includeSubDomains

DMARC policy

p=quarantine

Homepage HTML

166 KB, gzip

Images on homepage

35 (jpg 32, png 16, svg 12, gif 2)

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

• astrasms.com65
• o2online.es65
• plus.pl66
• povo.jp66
• visible.com66

Telecommunications & Internet readiness benchmark