Skip to main content

Security report for moedling.at

Stadtgemeinde Mödling · Government · Austria

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

Security score

40/100

Risk levelHigh

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

The Stadtgemeinde Mödling website serves as the official digital portal for the city of Mödling, Austria, providing residents and visitors with comprehensive municipal information, news, events, and public services. The site targets local citizens and stakeholders, offering easy access to administrative contacts, service forms, and cultural activities. The business model is that of a government entity focused on transparency and community engagement. Technically, the website employs a custom RIS CMS platform with common web technologies such as jQuery, Bootstrap, and FontAwesome, and integrates Matomo for analytics. However, the absence of HTTPS is a critical security flaw that undermines user trust and data protection. Security headers are partially implemented, but the lack of SSL/TLS and modern protocols significantly lowers the security posture. Privacy compliance is moderate, with a clear privacy policy but no cookie consent mechanism. Overall, the site is professional and trustworthy but requires urgent security upgrades.

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

This scan found 17 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
50
Network security
100
GDPR outside view
0
Average
40

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

Mödling's municipal website positions itself as a central hub for local governance and community services, leveraging digital tools to enhance citizen engagement. The partnership with GEM2GO for mobile app services indicates a commitment to modern communication channels. The site’s content is well-structured and relevant, supporting a medium-sized government entity. The absence of commercial elements and the focus on public service reflect a non-profit government business model. The website’s moderate size and consistent branding support its role as a trusted local authority. Growth opportunities include enhanced digital services and improved security compliance.

Security posture

The website currently exhibits a low security maturity level due to the lack of HTTPS and modern TLS protocols, exposing users to potential interception and data integrity risks. While some security headers are present, critical best practices such as HSTS, OCSP stapling, and secure session management are missing. No incident response or vulnerability disclosure policies are published, limiting transparency and preparedness. GDPR compliance is partial, with a privacy policy but no cookie consent. The use of Matomo analytics with disabled tracking by default is a positive privacy measure. Immediate remediation of SSL/TLS implementation and enhanced security policies are recommended to mitigate risks.

Recommendations

  1. Implement a valid SSL/TLS certificate and enforce HTTPS site-wide.
  2. Enable HSTS with includeSubDomains and preload to prevent protocol downgrade attacks.
  3. Adopt modern TLS protocols (TLS 1.2 or 1.3) and strong cipher suites.
  4. Introduce a cookie consent banner to comply with GDPR cookie regulations.
  5. Publish a security policy and incident response contact information.
  6. Add a vulnerability disclosure policy and security.txt file.
  7. Regularly audit and update third-party libraries and scripts for vulnerabilities.

Contact details published on the site

Addresses
Legal name
Stadtgemeinde Mödling
Technical notes

Notes

The website uses a custom RIS CMS platform with legacy jQuery 1.7.2 and jQuery UI 1.8.17, alongside modern Bootstrap 5.2.0 and Slick Carousel for UI components. The site loads multiple CSS and JS resources, some asynchronously, but performance metrics indicate zero load time and resource count, suggesting incomplete or missing performance data. Mobile optimization is good with responsive design and mobile app integration. Accessibility features such as skip links and ARIA labels are present. SEO is supported by meta tags and Open Graph data. DNS records are missing A/AAAA/MX/NS entries in the provided data, possibly due to CDN or proxy usage. Hosting provider is not identified. Overall, the technical stack is functional but could benefit from modernization 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 moedling.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 moedling.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.