elisa.fi

Readiness by lane

Green: elisa.fi. Thin bar: Telecommunications & Internet peer median.

Priority fixes for elisa.fi

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

   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 Next.js: Next.js documents nonce-based CSP with middleware.

   48% of Telecommunications & Internet peers do this.

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

3. Priority 3 · Enable

   Social preview image set

   Observed: The homepage had no og:image, so shared links may show without a preview image.

   What to do: Add Open Graph tags, including og:image with a 1200 x 630 image.

   59% of Telecommunications & Internet peers do this.

   Guide: SEO Checklist for a New Website

4. Priority 4 · Harden

   CAA records limit who can issue certificates

   Observed: No CAA record was found for elisa.fi, 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 elisa.fi already does well

Practices fewer than half of Telecommunications & Internet peers use.

• security.txt publishedsecurity.txt with a contact found.13% of peers
• Nameservers spread across providersNameservers spread across more than one operator.16% of peers
• Referrer-Policy setReferrer-Policy present.33% of peers

What we saw

Homepage checked

https://elisa.fi/

Homepage response

HTTP 200

TLS

TLSv1.2, HTTP/2

Certificate

DigiCert, 198-day validity, expiring 2027-03-10

CDN or edge

Amazon CloudFront

Platform or framework

Next.js

DNS operators

2 self-run or other nameserver domains

HSTS

max-age 365 days

DMARC policy

p=quarantine

Homepage HTML

160 KB, gzip

Images on homepage

15 (jpg 128, png 75)

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

• 1und1.de80
• bouyguestelecom.fr79
• datamartgh.shop80
• meo.pt80
• vodafone.ro81

Telecommunications & Internet readiness benchmark