Skip to main content

Security report for pzu.ee

PZU Kindlustus · Finance · Estonia

Medium risk. 3 critical or high findings in Security headers and SSL/TLS.

Security score

74/100

Risk levelMedium

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

PZU Kindlustus operates as an established insurance provider in Estonia, offering a range of personal insurance products including vehicle, travel, home, and accident insurance. The website reflects a professional presence with consistent branding and a focus on serving private individuals. The business is supported by a domain registered since 2012 under ALMIC OÜ, an Estonian registrar, indicating a stable and legitimate operation. Technically, the site is built on WordPress, leveraging modern tools such as Google Tag Manager, Cookiebot for cookie consent, and Cloudflare for DNS and security, demonstrating a mature digital infrastructure. Security measures include HTTPS enforcement and reCAPTCHA integration, though explicit security policies and headers could be enhanced. Privacy compliance is partially addressed via cookie consent, but the absence of a clear privacy policy and terms of service pages represents a compliance gap. Overall, the site is functional and trustworthy but would benefit from improved transparency and security documentation.

Scanned

NIS2 and GDPR posture

GDPR outside view
88/ 100 · Low
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

3 findings rated critical or high. Fix these first.

  1. 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 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';…

  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 SSL Key Length

      SSL certificate uses 256-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 pzu.ee

This scan found 20 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
65
Security headers
55
Email security
70
DNS health
65
Network security
100
GDPR outside view
88
Average
74

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 targets private individuals in Estonia, focusing on essential insurance services. Its business model revolves around providing various insurance products, positioning itself as a key player in the Estonian insurance market. The website content and metadata emphasize core insurance offerings, with no visible affiliate or partner domains. The use of structured data and SEO plugins suggests an intent to maintain good search visibility. The absence of direct contact emails or phone numbers on the homepage may indicate a preference for contact via forms or other channels. The company appears to be part of the larger PZU Group, a known insurance entity, enhancing its market credibility.

Security posture

The website enforces HTTPS and uses Cloudflare for DNS and CDN services, which provides baseline security and performance benefits. Integration of reCAPTCHA v3 on forms helps mitigate automated abuse. Cookie consent is managed via Cookiebot, supporting GDPR compliance. However, the lack of explicit privacy policy, terms of service, security policy, and incident response contacts reduces transparency and may expose the company to compliance risks. Security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options are not explicitly detected, which could be improved to harden the site against common web attacks. No vulnerabilities or exposed sensitive data were detected in the analyzed content.

Recommendations

  1. Publish a comprehensive privacy policy and terms of service pages prominently linked on the website.
  2. Implement and disclose a security policy including incident response procedures and contact channels such as security@ or abuse@ emails.
  3. Add a security.txt file to facilitate responsible vulnerability disclosure.
  4. Enhance HTTP security headers (CSP, X-Frame-Options, X-Content-Type-Options) to improve protection against web attacks.
  5. Provide clear and verified contact information including company phone numbers and emails to improve trust and compliance.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
PZU Kindlustus
Description
PZU Kindlustus pakub eraisikule: kaskokindlustus, liikuskindlustus, reisikindlustus, kodukindlustus, õnnetusjuhtumikindlustus.
Key services
kaskokindlustus, liikuskindlustus, reisikindlustus, kodukindlustus, õnnetusjuhtumikindlustus
Content quality
good
Branding
consistent

Technology

Stack
WordPress, jQuery, Google Tag Manager, Cookiebot, reCAPTCHA v3, Slick Carousel
Frameworks
Yoast SEO
Platforms
WordPress
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
70/100
Good practices seen
  • HTTPS enforced
  • Use of reCAPTCHA v3 for forms
  • Cookie consent mechanism implemented
  • Stop User Enumeration plugin active

Analytics and tracking

Services
Google Tag Manager
Tracking level
moderate
Privacy practices
basic

Advertising

Tracking pixels
Cookiebot, reCAPTCHA
Marketing tools
Cookiebot, SendPulse Push Notifications
Transparency
basic

Site quality

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

Key observations

  1. Website is a professional insurance service provider site for Estonia
  2. Uses modern web technologies and cookie consent mechanisms
  3. Lacks explicit privacy policy and terms of service pages
  4. No direct contact emails or phone numbers found in HTML content
  5. Security posture is good but can be improved with explicit policies and headers
  6. WHOIS data supports legitimacy and long-term operation
Technical notes

Notes

The website is built on WordPress CMS with a modern tech stack including jQuery, Google Tag Manager, Cookiebot, and reCAPTCHA v3. Hosting and DNS are managed via Cloudflare, providing CDN and security benefits. The site uses Yoast SEO plugin for metadata and structured data, improving search engine visibility. Performance is moderate with standard optimizations. Mobile responsiveness and basic accessibility features are present, though accessibility could be further improved. The site uses multiple CSS stylesheets and JavaScript libraries, indicating a feature-rich but potentially complex front-end. No critical technical debt or outdated libraries were detected in the provided content.
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 pzu.ee. 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 pzu.ee.

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.