telenor.no

Readiness by lane

Green: telenor.no. Thin bar: Telecommunications & Internet peer median.

Priority fixes for telenor.no

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

1. Priority 1 · Enable

   Structured data present

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

   Why it matters: Structured data helps search engines understand your organization, products or articles, and is needed for some rich results.

   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. Limit: Based on the homepage HTML delivered to an automated client; scripts that run later were not executed.

   Guide: Structured Data Basics for Website Owners

2. Priority 2 · Accelerate

   HTTP/3 advertised

   Observed: The homepage did not advertise HTTP/3 through an Alt-Svc header.

   What to do: Turn on HTTP/3 at your CDN. Browsers fall back to HTTP/2 automatically, so the risk is low.

   13% of Telecommunications & Internet peers do this.

   Guide: CDN Guide for Website Owners

3. Priority 3 · Harden

   DNSSEC signed

   Observed: No DS record was found for telenor.no 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.

   13% of Telecommunications & Internet peers do this.

   Guide: Website Uptime Readiness: Prepare Before Traffic Arrives

4. Priority 4 · Recover

   Nameservers spread across providers

   Observed: All nameservers for telenor.no belong to a single operator.

   What to do: Treat this as an advanced step. Add a secondary DNS provider through zone transfers or a multi-provider setup, then test changes carefully, since both providers must stay in sync.

   16% of Telecommunications & Internet peers do this.

   Guide: Website Uptime Readiness: Prepare Before Traffic Arrives

What telenor.no already does well

Practices fewer than half of Telecommunications & Internet peers use.

• security.txt publishedsecurity.txt with a contact found.13% of peers
• CAA records limit who can issue certificatesCAA limits issuance to amazon.com, amazonaws.com, amazontrust.com and others.15% of peers
• Certificate lifetime of 100 days or lessShort-lived 89-day certificate from Let's Encrypt, already inside the 2027 limit.28% of peers

What we saw

Homepage checked

https://www.telenor.no/

Homepage response

HTTP 200, after 1 redirect

TLS

TLSv1.3, HTTP/2

Certificate

Let's Encrypt, 89-day validity, expiring 2027-01-12

CDN or edge

Azure Front Door/CDN

Platform or framework

Nuxt

DNS operators

1 self-run or other nameserver domain

HSTS

max-age 365 days, includeSubDomains

DMARC policy

p=reject

Homepage HTML

182 KB, br

Images on homepage

13 (jpg 21, png 6, svg 3)

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

• entel.cl88
• globfone.com88
• telkom.co.za90
• true.th86
• ziggo.nl86

Telecommunications & Internet readiness benchmark