Skip to main content

Security report for villach.at

Stadt Villach · Government · Austria

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

Security score

52/100

Risk levelMedium

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

The website villach.at serves as the official digital presence of the city government of Villach, Austria. It provides comprehensive information and services to residents, visitors, and businesses, including news, event updates, municipal services, and contact information. The site is well-structured, professionally designed, and targets a broad audience interested in city services and local governance. The business model is focused on public administration and citizen engagement, positioning the site as a central hub for municipal information in the region. Technically, the site is built on a Microsoft IIS server using ASP.NET WebForms and Kentico CMS, integrating modern JavaScript libraries such as jQuery and AI-powered concierge tools. It employs Piwik Pro for analytics and Google reCAPTCHA for bot protection. Hosting is provided by a reputable Austrian hosting provider, hosttech.at. While the site is mobile-optimized and accessible, performance metrics indicate slow loading times, suggesting room for optimization. From a security perspective, the site lacks a valid SSL certificate and does not support HTTPS, which is a critical vulnerability exposing users to data interception risks. Security headers are partially implemented, and DNS records show proper SPF and DMARC configurations, enhancing email security. However, the absence of TLS protocols, HSTS, and OCSP stapling reduces the overall security posture. No explicit security or incident response policies are published, and no vulnerability disclosure mechanisms are evident. Overall, villach.at is a credible and authoritative government website with strong business credibility and good content quality. However, the lack of HTTPS and modern SSL/TLS configurations significantly undermines user trust and security. Strategic improvements in SSL deployment, security header enhancements, and privacy compliance mechanisms are recommended to elevate the site's security and compliance standards.

Scanned

This is an earlier scan of villach.at. View the latest report

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 villach.at

This scan found 19 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
35
Email security
85
DNS health
90
Network security
100
GDPR outside view
0
Average
52

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

Villach.at operates as the official municipal website for the city of Villach, Austria, serving as a digital gateway for public services, news, and community engagement. The site leverages partnerships with local tourism and marketing entities, such as visitvillach.at and kaerstin.at, to enhance visitor information. The business model is non-commercial, focusing on government service delivery and citizen communication. The platform supports multiple languages, reflecting a diverse target audience including residents, tourists, and businesses. The integration of AI concierge services and online appointment booking indicates a push towards digital transformation and improved user experience. The site’s market position is strong within the regional government sector, acting as a trusted source of official information. Revenue streams are not applicable, but the site supports public sector objectives including transparency, accessibility, and community support.

Security posture

The security posture of villach.at is currently weak due to the absence of a valid SSL certificate and lack of HTTPS support, exposing users to potential man-in-the-middle attacks and data privacy violations. While some security best practices are observed, such as HttpOnly and Secure cookie flags, CSRF token usage, and SPF/DMARC DNS records, the overall encryption and transport security are inadequate. The server uses Microsoft IIS 10.0 and ASP.NET 4.0, which are mature technologies but require proper configuration to ensure security. The site lacks modern TLS protocols, HSTS, OCSP stapling, and session resumption, which are standard for secure web services. No published security policies or incident response contacts were found, indicating limited transparency in security governance. The site should prioritize SSL certificate installation and enable HTTPS to protect user data and comply with regulatory requirements.

Recommendations

  1. Install and maintain 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 HTTP Strict Transport Security (HSTS) with includeSubDomains and preload directives.
  4. Enable OCSP stapling to improve certificate validation performance and security.
  5. Publish a security policy and incident response contact information, including abuse and security email addresses.
  6. Implement a cookie consent mechanism to comply with GDPR and privacy regulations.
  7. Regularly audit and update security headers and ensure secure configuration of all web components.

Contact details published on the site

Addresses
Technical notes

Notes

The website is hosted on Microsoft IIS 10.0 with ASP.NET 4.0 WebForms and Kentico CMS, indicating a traditional but stable technology stack. It uses jQuery 3.5.1 and integrates third-party services such as Piwik Pro analytics, Google reCAPTCHA, and an AI concierge tool from GoodGuys. The site is mobile-optimized and includes accessibility features, supported by the presence of WAI compliance logos. However, performance is poor with zero load time and resource count reported, suggesting incomplete or delayed performance data. The DNS setup is robust with multiple authoritative name servers and valid SPF and DMARC records. Hosting is provided by hosttech.at, a known Austrian hosting provider. The site uses no modern SSL/TLS protocols, which is a critical technical debt. SEO is well addressed with meta tags and structured navigation. Overall, the infrastructure is functional but requires modernization in security 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

Earlier scans of this domain

  1. 70/100Medium28 findingsView report
Reviews of this site

Share your experience with villach.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 villach.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.