Skip to main content

Security report for tele2.com

Tele2 · Telecommunications · Sweden

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

Security score

53/100

Risk levelMedium

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

Tele2 is a well-established telecommunications company focused on delivering smart connectivity solutions across multiple countries, primarily in the Nordic and Baltic regions. Their business model includes wholesale services, consumer mobile offerings, and business telecommunications solutions, with a strong emphasis on 5G technology and sustainability. The website reflects a mature enterprise with clear branding, comprehensive investor relations, and sustainability commitments. Technically, the website uses modern web technologies and is hosted on a cloud platform with video streaming capabilities. However, the security posture is currently weak due to an invalid SSL certificate and lack of modern TLS protocol support, which poses significant risks to user trust and data security. Privacy compliance is strong, with clear cookie and privacy policies and consent mechanisms in place. Overall, the site is professional and trustworthy but requires urgent security improvements to align with best practices.

Scanned

This is an earlier scan of tele2.com. View the latest report

NIS2 and GDPR posture

GDPR outside view
15/ 100 · Critical
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

    • High

      No Privacy Policy found

      GDPR requires a clear and accessible privacy policy

      What to do: Add a comprehensive privacy policy page and link to it prominently

    • High

      No Cookie Consent Banner found

      GDPR requires explicit consent for non-essential cookies

      What to do: Implement a cookie consent banner that appears on first visit

  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 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 tele2.com

This scan found 13 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. The full timeline opens with your unlock code.

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
65
Email security
50
DNS health
90
Network security
100
GDPR outside view
15
Average
53

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

Tele2 holds a strong market position in telecommunications with a diversified portfolio of brands and subsidiaries across Sweden, Lithuania, Latvia, and Estonia. Their business model leverages wholesale and retail segments, targeting consumers and enterprises. The company emphasizes sustainability and corporate governance, which enhances its reputation and investor confidence. The presence of multiple market-specific domains and brands indicates a broad geographic footprint and localized market strategies. The company maintains active social media channels to engage with customers and stakeholders. Financial transparency is supported by detailed investor reports and calendars. The lack of direct contact information on the main site suggests a structured approach to customer and partner communications, likely routed through dedicated channels.

Security posture

The website demonstrates several security best practices such as the use of security headers (X-Content-Type-Options, X-Frame-Options, Referrer-Policy) and a strict transport security header. However, the SSL certificate is invalid or missing, and no TLS protocols are enabled, which critically undermines the security of data in transit. The absence of OCSP stapling and session resumption further degrades security and performance. No explicit incident response or vulnerability disclosure information is found, indicating potential gaps in transparency and readiness. Privacy policies and cookie consent mechanisms are well implemented, supporting GDPR compliance. The overall security maturity is low, and immediate remediation of SSL/TLS issues is essential to protect users and maintain trust.

Recommendations

  1. Immediately renew and correctly configure the SSL certificate to enable HTTPS with valid encryption.
  2. Enable and enforce modern TLS protocols (TLS 1.2 and TLS 1.3) to secure communications.
  3. Implement OCSP stapling and session resumption to improve security and performance.
  4. Publish clear incident response and vulnerability disclosure policies with dedicated contact channels.
  5. Enhance accessibility features and provide direct, clearly labeled contact information for users.
  6. Regularly audit and update security headers and privacy compliance measures.
  7. Optimize website performance metrics and provide transparency on data retention policies.
Technical notes

Notes

The website is built using modern web standards including CSS Grid and JavaScript, with video content delivered via Cloudflare Stream. Google Tag Manager is used for analytics and tracking, and OneTrust manages cookie consent. Hosting appears to be on a cloud platform with CDN capabilities. Despite modern frontend technologies, performance data is missing, suggesting potential for optimization. Mobile responsiveness is good, and SEO meta tags are properly configured. However, the invalid SSL certificate and lack of TLS support represent significant technical debt and risk. The site lacks explicit CMS identification but is likely custom or SaaS-based. Overall, the technical infrastructure supports a professional web presence but requires urgent security upgrades and performance tuning.
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

Earlier scans of this domain

  1. 80/100Low24 findingsView report
Reviews of this site

Share your experience with tele2.com. 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 tele2.com.

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.