Skip to main content

Security report for innogy-energo.cz

innogy Energo · Energy · Czech Republic

Medium risk. 5 critical or high findings in GDPR outside view and SSL/TLS.

Security score

75/100

Risk levelMedium

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

innogy Energo is a major energy company operating in the Czech Republic, providing natural gas, electricity, and related services to approximately 1.7 million customers. The company emphasizes its extensive operational footprint with over 4000 employees and multiple service offerings including CNG filling stations, photovoltaics, and electromobility solutions. The website reflects a professional and consistent brand presence with clear navigation and comprehensive service information. Technically, the site leverages modern technologies such as Sitecore CMS, jQuery, Google Tag Manager, and Cookiebot for consent management, indicating a mature digital infrastructure. Security measures include HTTPS enforcement and bot protection via Cloudflare Turnstile, though explicit security headers and policies are not visible. Privacy compliance is well addressed with detailed cookie and privacy policies and a consent banner. Overall, the site demonstrates a solid security posture with room for improvement in publishing explicit security policies and incident response contacts. The absence of WHOIS data slightly impacts trust but is mitigated by the professional presentation and official contact details.

Scanned

NIS2 and GDPR posture

GDPR outside view
40/ 100 · High
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

5 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

      EU business without adequate privacy measures

      EU businesses are subject to strict GDPR requirements

      What to do: Implement comprehensive GDPR compliance including privacy policy, cookie consent, and data protection measures

    • 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

      Third-party services without privacy policy

      Detected services: Google Analytics, Facebook, Twitter, YouTube, Cloudflare

      What to do: Document all third-party data sharing in your privacy policy

  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.

    • High

      Weak Protocols Supported

      Server supports weak protocols: TLSv1.1

      What to do: Disable TLS 1.0, TLS 1.1, and all SSL versions

      • CWE-327
      • OWASP A04:2025
      • ASVS V12.1.1
    • High

      Weak SSL Key Length

      SSL certificate uses 384-bit key, which is considered weak

      What to do: Use at least 2048-bit RSA or 256-bit ECC key

      • CWE-326
      • OWASP A04:2025
      • Mozilla TLS: Mozilla Server Side TLS 6.0 intermediate: rsa_key_size 2048

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

Keep watching innogy-energo.cz

This scan found 16 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
47
Security headers
90
Email security
85
DNS health
90
Network security
100
GDPR outside view
40
Average
75

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

Breach exposure

Leaked credentials and lookalike domains from OffSeq Breach. The counts are free; the detailed lists are paid add-ons.

Dark web exposure

Add-on

Leaked records that mention innogy-energo.cz, from OffSeq Breach.

No leaked records found

Breach holds no records for innogy-energo.cz right now. New leaks arrive continuously, so monitoring on Breach alerts you if that changes.

Monitor on Breach (opens in a new tab)

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 holds a strong market position as one of the largest energy providers in the Czech Republic, targeting both residential and commercial customers. Its diversified service portfolio includes traditional energy supply and innovative solutions like electromobility and photovoltaics, positioning it well for future energy trends. The presence of multiple partner domains and social media channels supports a broad ecosystem and customer engagement strategy. The business model focuses on energy supply, infrastructure management, and value-added services, with a clear emphasis on sustainability and alternative energy sources. The website content and structure suggest a customer-centric approach with accessible information and support channels.

Security posture

The website exhibits a moderate to good security posture with HTTPS usage, cookie consent management, and bot protection mechanisms. However, the lack of visible security headers and absence of a published security policy or incident response information indicate areas for enhancement. No vulnerabilities or exposed sensitive data were detected in the analysis. The company should consider publishing a vulnerability disclosure policy and security.txt file to improve transparency and readiness. Overall, the security culture appears adequate but could benefit from formalized documentation and enhanced header configurations.

Recommendations

  1. Implement and verify HTTP security headers such as Content-Security-Policy, Strict-Transport-Security, X-Frame-Options, and X-Content-Type-Options.
  2. Publish a dedicated security policy and incident response contact information on the website.
  3. Establish and publicize a vulnerability disclosure program or security.txt file to encourage responsible reporting.
  4. Regularly audit third-party scripts and libraries to ensure they are up to date and free from known vulnerabilities.
  5. Enhance transparency by providing detailed data retention policies and GDPR compliance statements.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
innogy Energo
Description
V České republice patříme k největším a nejvýznamnějším společnostem působícím na tuzemském trhu. S více než 4000 zaměstnanci zajišťujeme dodávky zemního plynu, elektřiny a dalších služeb 1,7 milionu zákazníků.
Key services
supply of natural gas, electricity supply, CNG filling stations, photovoltaics, electromobility, energy contracting, energy audits, energy management, micro-cogeneration units
Content quality
good
Branding
consistent

Technology

Stack
jQuery 3.7.1, Google Tag Manager, Cookiebot, Cloudflare Turnstile Captcha, Sitecore Experience Forms
Frameworks
Sitecore
Performance
moderate
Mobile
good
Accessibility
good
SEO
good

Security

Observed score
75/100
Good practices seen
  • HTTPS enforced (implied by canonical URL and external scripts loaded over HTTPS)
  • Cookie consent banner with granular controls
  • Use of Google Tag Manager with consent management
  • Use of Cloudflare Turnstile captcha for bot protection

Analytics and tracking

Services
Google Tag Manager
Tracking level
minimal
Privacy practices
good

Advertising

Tracking pixels
Cookiebot session tracker
Marketing tools
Cookiebot
Transparency
good

Site quality

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

Key observations

  1. Website is fully accessible with rich content and navigation.
  2. No WHOIS data available, indicating possible privacy protection or domain registration issue.
  3. Comprehensive cookie consent mechanism implemented.
  4. No explicit security policy or incident response information found.
  5. Multiple official social media channels linked.
  6. No forms detected that collect personal data directly on the homepage.
  7. Use of modern JavaScript libraries and CMS (Sitecore).
  8. No signs of malware or phishing detected.
  9. Content is in Czech language targeting Czech market.
Technical notes

Notes

The website uses a modern technology stack centered around the Sitecore CMS platform, supported by jQuery and Google Tag Manager for analytics and event tracking. Cookiebot is integrated for comprehensive cookie consent management, reflecting compliance with privacy regulations. The site loads efficiently with preloaded fonts and scripts, and it is optimized for mobile devices with responsive design elements. Accessibility features such as skip links and ARIA roles are present, enhancing usability. Hosting appears to be supported by Cloudflare services, including Turnstile captcha for bot mitigation. Performance is moderate, with opportunities to optimize further by reducing script load and enhancing caching strategies. Overall, the technical infrastructure is robust and aligned with contemporary web standards.
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 innogy-energo.cz. 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 innogy-energo.cz.

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.