Skip to main content

Security report for helvetia.de

Helvetia Versicherungen · Finance · Germany

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

Security score

51/100

Risk levelMedium

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

Helvetia Versicherungen is a well-established insurance provider in Germany offering a broad range of insurance and pension products for private and corporate customers. The company emphasizes customer service, sustainability, and innovative insurance solutions, supported by over 160 years of experience. The website is professionally designed, content-rich, and targets German-speaking customers with clear navigation and comprehensive service information. Technically, the site uses Adobe Experience Manager CMS and Cloudflare for DNS and CDN services, with Adobe DTM for marketing analytics. However, a critical security issue is the absence of a valid SSL certificate and HTTPS support, which significantly impacts the security posture. Security headers are properly configured, but the lack of HTTPS and modern TLS protocols is a major vulnerability. Privacy compliance is well addressed with clear privacy and cookie policies, and GDPR compliance is evident. Business credibility is high, supported by awards and customer reviews. Overall, the site is trustworthy but urgently needs to address its SSL/TLS configuration to ensure secure user interactions.

Scanned

NIS2 and GDPR posture

GDPR outside view
0/ 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

      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

    • Critical

      No HTTPS encryption

      GDPR requires appropriate security measures for personal data

      What to do: Implement SSL/TLS certificate for HTTPS

    • High

      No Cookie Policy found

      GDPR requires clear information about cookie usage

      What to do: Add a dedicated cookie policy explaining cookie usage and purposes

  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 helvetia.de

This scan found 15 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
65
Email security
50
DNS health
90
Network security
100
GDPR outside view
0
Average
51

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

Helvetia holds a strong market position in the German insurance sector, leveraging its long history and customer satisfaction awards. The business model focuses on providing tailored insurance products including pet, vehicle, home, liability, and pension insurances. The company maintains a multi-channel approach with online calculators, agent locators, and digital claim reporting. Partnerships with mail providers and review platforms enhance operational efficiency and customer trust. The website content and structure reflect a mature digital presence aimed at both private and corporate clients, supporting growth and customer engagement.

Security posture

The current security posture shows a mix of good practices and critical gaps. Security headers like X-Frame-Options, X-XSS-Protection, and HSTS are implemented, indicating awareness of web security best practices. However, the complete lack of a valid SSL certificate and disabled TLS protocols expose users to significant risks including data interception and man-in-the-middle attacks. No OCSP stapling or session resumption is configured, which could affect performance and security. The absence of a security.txt file or explicit incident response contact reduces transparency for vulnerability reporting. Immediate remediation of SSL/TLS issues is essential to protect user data and maintain trust.

Recommendations

  1. Obtain and deploy a valid SSL/TLS certificate to enable HTTPS across the entire site.
  2. Enable modern TLS protocols (TLS 1.2 and TLS 1.3) and disable deprecated protocols.
  3. Implement OCSP stapling and session resumption to improve security and performance.
  4. Publish a security.txt file to facilitate vulnerability disclosure and improve transparency.
  5. Regularly review and update security headers and conduct security audits to identify and mitigate risks.

Contact details published on the site

Addresses
Technical notes

Notes

The website is built on Adobe Experience Manager, a robust enterprise CMS, and uses Cloudflare for DNS and CDN services, indicating a modern and scalable infrastructure. Adobe DTM is used for tag management and analytics, supporting marketing and data collection needs. The site is mobile optimized with responsive design and accessibility features. Performance data is missing, but the use of CDN and lazy loading images suggests good performance optimization. The malformed CAA DNS records are a minor technical issue that should be corrected. Overall, the technical stack is mature but requires urgent SSL/TLS improvements to meet security 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 helvetia.de. 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 helvetia.de.

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.