Skip to main content

Security report for merkur.at

Merkur Versicherung AG · Finance · Austria

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

Security score

49/100

Risk levelHigh

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

Merkur Versicherung AG is Austria's oldest insurance company, specializing in private health, accident, life, property, and legal protection insurance. Positioned as the second largest private health insurer in Austria, it serves a broad audience including private customers, employees, and businesses. The website demonstrates a mature digital presence with a professional design, clear navigation, and comprehensive content tailored to its target audience. Technically, the site is built on Liferay DXP with React and Clay UI components, but suffers from critical SSL misconfiguration that undermines its security posture. Security headers are well implemented, but the lack of a valid SSL certificate and disabled TLS protocols present significant risks. Privacy compliance is strong with clear policies and consent mechanisms. Overall, the site is trustworthy and professional but requires urgent remediation of SSL issues 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 merkur.at

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. 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
60
Email security
50
DNS health
85
Network security
100
GDPR outside view
0
Average
49

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 merkur.at, from OffSeq Breach.

Total records
417
Employees
0
Customers
416
Third parties
1
Weak passwords
12%

8 subdomains affected

See the 10 newest leaked credentials

A one-off add-on to this report that lists the most recent identifier and password pairs OffSeq Breach holds for merkur.at.

Select it in the checkout above.

Breach keeps ingesting new leaks, so these numbers can grow between scans.

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 operates in the finance sector with a focus on insurance products. Its business model revolves around providing tailored insurance solutions, supported by a digital customer portal and extensive online resources. The presence of multiple social media channels and app store links indicates active engagement and marketing efforts. The domain registration data aligns with the company's claims, reinforcing legitimacy. The company is part of the Merkur Group and has a long-standing market presence since 1798. The website content and structure reflect a well-established enterprise with a clear brand identity and consistent messaging.

Security posture

While the website employs several security best practices such as HSTS, HttpOnly cookies, and security headers like X-Frame-Options and X-Content-Type-Options, the absence of a valid SSL certificate and disabled TLS protocols severely compromise the security posture. This exposes users to risks such as data interception and undermines trust. No incident response or vulnerability disclosure policies were found. The site lacks OCSP stapling and session resumption, which are important for performance and security. Overall, the security maturity is moderate but requires immediate attention to SSL/TLS configuration.

Recommendations

  1. Obtain and correctly install a valid SSL certificate to enable HTTPS across the site.
  2. Enable modern TLS protocols (TLS 1.2 and TLS 1.3) and disable deprecated versions.
  3. Implement OCSP stapling and session resumption to improve SSL performance and security.
  4. Publish a clear security policy and vulnerability disclosure program to enhance transparency.
  5. Regularly audit and update security headers and privacy compliance to maintain best practices.
Technical notes

Notes

The website is powered by Liferay Digital Experience Platform, leveraging React and Clay UI libraries for frontend components. It uses Apache as the web server and is hosted on infrastructure managed by grazkom.at. The site has good SEO and accessibility features, with proper meta tags and language attributes. However, performance metrics indicate slow loading times, possibly due to large resource bundles and lack of optimization. The SSL configuration is incomplete, impacting secure communications. The site is mobile optimized and accessible, with a clear navigation structure and comprehensive content. Technical debt is moderate, with opportunities for modernization in SSL and performance optimization.
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 merkur.at. 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 merkur.at.

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.