Skip to main content

Security report for wellcon.at

WELLCON · Healthcare · Austria

High risk. 9 critical or high findings in GDPR outside view, SSL/TLS and 2 other checks.

Security score

27/100

Risk levelHigh

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

Wellcon is an established Austrian company specializing in occupational health, safety, and workplace wellness services. With 25 years of experience and multiple locations, it serves companies seeking comprehensive occupational medicine, psychology, and safety technology solutions. The website is professionally designed using WordPress and Elementor, featuring good content quality and SEO optimization. However, the technical infrastructure lacks a valid SSL certificate, resulting in no HTTPS support, which is a critical security vulnerability. Privacy compliance is basic, with a privacy policy present but no cookie consent mechanism despite the use of Matomo analytics. Contact information is not explicitly provided on the homepage or footer, limiting direct communication channels. Overall, the business credibility is strong, but the security posture requires urgent improvement to protect user data and enhance trust.

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

9 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

  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 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 X-Frame-Options header

      Prevents clickjacking attacks

      What to do: Add "X-Frame-Options: DENY" or "X-Frame-Options: SAMEORIGIN"

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

Keep watching wellcon.at

This scan found 21 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
15
Email security
50
DNS health
75
Network security
20
GDPR outside view
0
Average
27

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

Wellcon operates in the healthcare and occupational safety sector, targeting businesses that require employee health and safety consulting. Its business model focuses on providing interdisciplinary and tailored services including occupational medicine, workplace examinations, and health promotion. The company has a solid market position in Austria with a history dating back to 1998 and five physical locations. The website reflects a professional brand with consistent messaging and trust indicators such as years in business and multiple sites. The use of Matomo analytics suggests a preference for privacy-conscious tracking. However, the absence of explicit contact details and terms of service pages may limit customer engagement and transparency. There is no evidence of partnerships or subsidiaries from the website content.

Security posture

The website currently lacks a valid SSL certificate, resulting in no HTTPS support, which is a critical security flaw exposing users to potential data interception. No advanced security headers are present, and no DMARC or vulnerability disclosure mechanisms are implemented. The SPF record is valid, reducing email spoofing risk. The absence of HSTS and OCSP stapling further weakens TLS security. No incident response or security policy information is available, indicating limited transparency and preparedness for security events. The use of Matomo analytics with disabled cookies is a positive privacy measure, but the lack of cookie consent is a compliance gap. Overall, the security posture is weak and requires immediate remediation to meet modern standards and regulatory requirements.

Recommendations

  1. Obtain and deploy a valid SSL/TLS certificate to enable HTTPS across the entire website.
  2. Implement a cookie consent mechanism to comply with GDPR and inform users about tracking.
  3. Add and publish a comprehensive privacy policy with explicit GDPR compliance statements.
  4. Publish contact information including emails and phone numbers to improve user trust and communication.
  5. Introduce security headers such as Content-Security-Policy, X-Frame-Options, and Referrer-Policy.
  6. Establish a vulnerability disclosure policy or security.txt file to enhance transparency.
  7. Enable DMARC and improve email security posture.
  8. Enable HSTS with includeSubDomains and preload directives.
  9. Regularly update and audit all plugins and server software to mitigate vulnerabilities.
  10. Consider publishing incident response and security policy documentation.
Technical notes

Notes

The website is built on WordPress CMS using the Elementor and Elementor Pro page builders, with Yoast SEO for search engine optimization. It uses Apache as the web server and is hosted on infrastructure associated with Telekom Austria. The site loads multiple CSS and JS assets including jQuery, Swiper.js, and Font Awesome. Matomo analytics is used for tracking with cookies disabled, indicating privacy awareness. Performance metrics are not available, but the page size and resource count are zero in the provided data, suggesting incomplete performance data or measurement issues. Accessibility is enhanced by the Pojo Accessibility plugin. The site is mobile optimized and SEO friendly with proper meta tags and structured data in JSON-LD format. However, the lack of HTTPS and modern TLS protocols is a significant technical deficiency. The site does not implement caching or session resumption for TLS, and no advanced security protocols are enabled.
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 wellcon.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 wellcon.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.