Skip to main content

Security report for ice.net

Lyse Tele AS · Telecommunications · Norway

Medium risk. 6 critical or high findings in GDPR outside view, SSL/TLS and 2 other checks.

Security score

55/100

Risk levelMedium

0–100, higher is better. How it is calculated

ice.no is the official website of Lyse Tele AS, a Norwegian telecommunications company celebrating 10 years in business. The company offers mobile subscriptions, mobile broadband, and mobile phones, targeting Norwegian consumers and businesses. The website demonstrates a mature digital presence with comprehensive content, clear navigation, and strong branding consistency. It integrates multiple analytics and marketing tools, including Google Analytics, Hotjar, Optimizely, and Freshchat, indicating a data-driven approach to customer engagement and service optimization. Security practices are robust, with HTTPS enforced, cookie consent managed via Cookiebot, and no visible vulnerabilities or exposed sensitive data. Privacy and terms of service pages are accessible and comprehensive, supporting GDPR compliance. Overall, the site reflects a professional, secure, and user-friendly platform aligned with the company's market position as a leading Norwegian telecom provider.

Scanned

NIS2 and GDPR posture

GDPR outside view
63/ 100 · Medium
Checks completed
7of 7

NIS2 Art. 21(2)

  1. (a) Risk analysis and security policies: Not visible from outside
  2. (b) Incident handling: One indicator
  3. (c) Business continuity, backups and crisis management: Not visible from outside
  4. (d) Supply chain security: Not visible from outside
  5. (e) Secure acquisition, development and maintenance, including vulnerability handling: Partly checked
  6. (f) Assessing the effectiveness of security measures: Not visible from outside
  7. (g) Cyber hygiene and security training: Not visible from outside
  8. (h) Cryptography and encryption: Partly checked
  9. (i) HR security, access control and asset management: One indicator
  10. (j) Multi-factor authentication and secured communications: Not visible from outside

This scan rated NIS2 with an earlier keyword method that is no longer shown; rescan for the per-article view. Risk management, continuity, supply chain, training, MFA, management oversight (Art. 20) and incident reporting (Art. 23) need internal evidence, and Guard cannot tell whether NIS2 applies to this organisation.

GDPR is indicative only, based on publicly visible signals: Articles 7, 12, 13 and 32 of Regulation (EU) 2016/679 and Article 5(3) of the ePrivacy Directive. Not a certification or legal assessment.

Priority findings

6 findings rated critical or high. Fix these first.

  1. GDPR outside view

    These are the privacy signals visitors and data protection authorities look for under GDPR.

    • Critical

      No HTTPS encryption

      GDPR requires appropriate security measures for personal data

      What to do: Implement SSL/TLS certificate for HTTPS

  2. SSL/TLS

    TLS encrypts the connection and proves the site is really yours. Weak or expiring certificates trigger browser warnings and put traffic at risk.

    • Critical

      No HTTPS Encryption

      Website does not use HTTPS encryption, making all data transmission vulnerable to interception

      What to do: Implement SSL/TLS certificate and redirect all HTTP traffic to HTTPS

  3. Security headers

    Security headers are instructions your web server sends to every visitor’s browser. Missing ones leave visitors more exposed to attacks such as clickjacking and injected scripts.

    • High

      Missing Strict-Transport-Security header

      Forces HTTPS connections

      What to do: Add "Strict-Transport-Security: max-age=31536000; includeSubDomains; preload"

      • CWE-319
      • OWASP A04:2025
      • ASVS V3.4.1
    • High

      Missing X-Frame-Options header

      Prevents clickjacking attacks

      What to do: Add "X-Frame-Options: DENY" or "X-Frame-Options: SAMEORIGIN"

    • High

      Missing Content-Security-Policy header

      Controls resources the browser is allowed to load

      What to do: Implement a Content-Security-Policy appropriate for your application

      • ASVS V3.4.3
      • OWASP Secure Headers: OWASP Secure Headers Project recommends Content-Security-Policy: default-src 'self'; form-action 'self'; base-uri 'self'; object-src 'none';…

Need hands-on remediation? Email guard@offseq.com

Keep watching ice.net

This scan found 18 issues across 6 checks. Monitoring re-runs those checks daily, emails you when something material changes and records each fix, so you can show progress.

Daily monitoring

Recommended

€25per month

  • TLS certificates and expiry
  • DNS records
  • SPF, DKIM and DMARC
  • Security headers
  • GDPR and NIS2 posture
  • Exposed services
  • Third-party trackers
  • Security score drift

Email alerts on material changes and an exportable JSON history of every change.

Billed monthly to your card. Cancel anytime. See sample alerts.

Full report

€39.90one-time

  • The complete analysis as a PDF you can cite
  • Email delivery with an unlock code
  • Lifetime access to this report

Prices incl. 21% VAT. Secure checkout by Mollie; sold by SEQ SIA, Latvia.

Results by check

Each check with its score, findings and the evidence it collected.

How this score is calculated

The security score runs 0–100, higher is better. It is the plain average of the security checks that completed in this scan, each counted equally. A check that could not run is left out: it counts neither as a pass nor as a fail.

Counted in this score

SSL/TLS
0
Security headers
15
Email security
65
DNS health
85
Network security
100
GDPR outside view
63
Average
55

Not counted

  • NIS2 outside view: Re-weights evidence from the TLS, email, DNS, network and hygiene checks, so counting it would count that evidence twice. Shown on its own.
  • OffSeq Observations: An AI reading of the site, useful context but not reproducible evidence. Shown on its own.

Findings that cap the score at 49

Each of these is serious on its own, so while any is present the site cannot rate better than high risk, however good the other checks are.

  • The certificate is not trusted by browsers
  • The website is not served over HTTPS
  • A database, remote desktop, file-sharing or Telnet service is reachable from the internet
  • The page loads a script from a compromised source
  • The domain registration has expired
  • SPF authorises every server to send mail as the domain

Partial scans

When the site blocks Guard or most checks cannot run, the score covers only the checks that ran (usually DNS and email), is capped at 75 and is shown as partial, without a risk level.

Risk levels

  • Critical0–25
  • High26–49
  • Medium50–75
  • Low76–100

Technical appendix

Business context, site observations and technical notes gathered during the scan, and the standards behind each reference.

Business context

Business profile

The company positions itself as a competitive telecom operator in Norway, offering a range of mobile and broadband services with value-added features such as family plans and device insurance. The business model includes retail and online sales channels, supported by a strong customer service infrastructure evidenced by awards and chat integration. The domain age and WHOIS data align with the company's claimed history, enhancing legitimacy. Partnerships and service subdomains indicate a well-structured ecosystem supporting identity management, ordering, and customer self-service. The marketing strategy leverages multiple ad networks and retargeting services, ensuring broad reach and personalized advertising. The company maintains transparency through detailed cookie and privacy disclosures, reflecting a mature compliance posture.

Security posture

The website exhibits a strong security posture with enforced HTTPS, presence of security headers, and use of anti-forgery tokens. Cookie consent is actively managed, and no sensitive data is exposed in the HTML content. The use of reputable third-party services is evident, with no detected vulnerable libraries or insecure scripts. However, explicit security policy and incident response information are not found, representing an area for improvement. The overall security score is high, reflecting good practices but with room for enhanced transparency and formal documentation.

Recommendations

  1. Publish a dedicated security policy page outlining security practices and commitments.
  2. Implement and publish a vulnerability disclosure policy or security.txt file to facilitate responsible reporting.
  3. Provide clear incident response contact channels such as security@ or abuse@ email addresses.
  4. Regularly audit and update third-party scripts and libraries to mitigate emerging vulnerabilities.
  5. Enhance Content-Security-Policy headers with strict rules to further reduce attack surface.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Lyse Tele AS
Description
Telecommunications provider offering mobile subscriptions, mobile broadband, and mobile phones primarily in Norway.
Key services
Mobile subscriptions, Mobile broadband, Mobile phones and accessories, Value-added services like insurance, device trade-in, and family plans
Content quality
excellent
Branding
consistent

Technology

Stack
JavaScript, Optimizely, Google Tag Manager, Hotjar, Freshchat, Cookiebot, Microsoft Application Insights, Siteimprove
Performance
fast
Mobile
excellent
Accessibility
good
SEO
good

Security

Observed score
90/100
Good practices seen
  • HTTPS enforced
  • Cookie consent management
  • No exposed sensitive data in HTML
  • Use of security tokens and anti-forgery cookies

Analytics and tracking

Services
Google Analytics, Hotjar, Microsoft Application Insights, Siteimprove, Dynatrace
Tracking level
extensive
Privacy practices
good

Advertising

Ad networks
Facebook, Google Marketing Platform (DV360 & Google Ads), Snapchat, LinkedIn, Adtraction, Adform
Tracking pixels
Hotjar, Siteimprove, Cookiebot, Optimizely
Marketing tools
Optimizely, Freshchat, Cookiebot
Transparency
excellent

Site quality

Design
excellent
User experience
excellent
Content relevance
excellent
Navigation
excellent
Professionalism
excellent
Trustworthiness
high

Key observations

  1. Comprehensive cookie consent management with Cookiebot.
  2. Use of multiple analytics and marketing tools with clear privacy disclosures.
  3. Strong branding and professional website design.
  4. Clear navigation and mobile optimization.
  5. No signs of WAF or content blocking.
  6. No exposed sensitive data or security vulnerabilities detected in HTML content.
  7. Use of modern JavaScript libraries and frameworks.
  8. Presence of customer service chat integration (Freshchat).
  9. Multiple social media presence links in footer.
  10. Clear contact phone number with business hours.
Technical notes

Notes

The website is built on Episerver CMS and leverages modern JavaScript libraries and analytics tools, including Optimizely for A/B testing and Microsoft Application Insights for telemetry. Performance is optimized with preloading, responsive images, and lazy loading techniques. Mobile optimization is excellent, with adaptive layouts and accessible navigation. The site uses advanced cookie consent management via Cookiebot, ensuring compliance and user control. Hosting appears to be on Microsoft Azure, supported by telemetry and CDN usage. The technical infrastructure is robust, supporting a fast, secure, and user-friendly experience with minimal technical debt evident.
Standards and sources

Reference chips under each finding point to the standard, regulation or specification the finding relates to. They are taken from the official datasets below and mapped conservatively: a finding with no defensible link shows none. NIS2 and GDPR references mark where a finding is relevant evidence, not a compliance verdict. Implementing Regulation (EU) 2024/2690 binds digital infrastructure and digital service providers; for other entities it is the most detailed public reading of the Article 21 measures. WCAG, EN 301 549, European Accessibility Act and Web Accessibility Directive references name the requirement an automated accessibility rule relates to; they are not a conformance verdict.

Retrieved 2026-10-25

Reviews of this site

Share your experience with ice.net. Every review is verified by email and published after moderation.

Overall rating
Select a rating
4000 characters remaining

We’ll email you to confirm your review and keep your details private.

Community rating

No published reviews yet. Be the first to review ice.net.

Feedback on this report

Rate this report, add an optional comment, and tell us if you want a security specialist to follow up.

Overall report quality
Select a rating
2000 characters remaining

We only use your feedback to improve Guard reports. Contact details are never shared.