Skip to main content

Security report for hk-schweiz.at

Handelskammer Schweiz-Österreich-Liechtenstein · Other · Austria

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

Security score

46/100

Risk levelHigh

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

The Handelskammer Schweiz-Österreich-Liechtenstein operates as a well-established chamber of commerce serving companies and economic actors in Switzerland, Austria, Liechtenstein, and the CEE region. Founded in 1921, it provides networking opportunities, market support services, economic data, and events to its members, positioning itself as a key business hub in the region. The website reflects a professional and consistent brand with clear business information and relevant content for its target audience. Technically, the site is built on Drupal 7 with jQuery and uses Matomo for analytics, but it suffers from slow performance and lacks modern security features. Critically, the absence of HTTPS and modern TLS protocols exposes the site to significant security risks. Security headers are partially implemented, but no incident response or security policies are published. Privacy compliance is basic, with no cookie consent mechanism detected despite GDPR applicability. Overall, the site demonstrates good business credibility but requires urgent security improvements to protect user data and maintain 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

7 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 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 hk-schweiz.at

This scan found 18 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
40
Email security
50
DNS health
85
Network security
100
GDPR outside view
0
Average
46

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 organization leverages a membership-based business model offering services and events with member discounts, targeting companies operating in the DACH and CEE economic zones. Its competitive advantage lies in its extensive network and long history since 1921. Revenue streams likely include membership fees, paid services, and advertising in its hub magazine. The website content and testimonials reinforce its strong market position and trusted reputation. The absence of social media links suggests a focus on direct member engagement rather than broad digital marketing. The partnership ecosystem includes Microsoft Outlook mail protection and hosting by world4you.at. Growth indicators include recent blog posts and active event promotion.

Security posture

The current security posture is weak due to the lack of HTTPS, no HSTS, and no modern TLS support, exposing users to interception and man-in-the-middle attacks. While some security headers like X-Frame-Options and X-Content-Type-Options are present, they are insufficient without encryption. No vulnerability disclosure or incident response contacts are published, limiting transparency and readiness. The use of Drupal 7, an outdated CMS, may introduce additional risks if not properly patched. Privacy compliance is partial, with a privacy policy present but no cookie consent mechanism. Matomo analytics is configured with Do Not Track enabled, reflecting some privacy awareness. Immediate remediation is required to implement HTTPS and improve security controls.

Recommendations

  1. Implement a valid SSL/TLS certificate and enable HTTPS site-wide immediately.
  2. Configure HSTS with includeSubDomains and preload flags to enforce secure connections.
  3. Upgrade the CMS from Drupal 7 to a supported version or alternative platform to reduce security risks.
  4. Introduce a cookie consent banner and enhance privacy compliance to meet GDPR requirements.
  5. Publish a security policy and incident response contact information to improve transparency and trust.

Contact details published on the site

Addresses
Technical notes

Notes

The website runs on Drupal 7 CMS with jQuery 1.12 and bxSlider for slideshows, hosted on servers managed by world4you.at. The site uses Matomo analytics with Do Not Track enabled, indicating privacy-conscious tracking. Performance metrics are missing, but the DNS resolution time is moderate (535ms). The site lacks HTTPS, which is a critical technical deficiency. The HTML content is well-structured with canonical and shortlink tags, meta viewport for mobile optimization, and basic accessibility features. SEO is basic with canonical links and meta tags but no Open Graph or JSON-LD structured data detected. The site uses multiple CSS imports and JavaScript libraries, some of which are outdated. Overall, the technical infrastructure is functional but outdated and insecure, requiring modernization and security upgrades.
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 hk-schweiz.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 hk-schweiz.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.