Skip to main content

Security report for flensburg.de

Stadt Flensburg · Government · Germany

Medium risk. 5 critical or high findings in GDPR outside view, Security headers and 1 other check.

Security score

64/100

Risk levelMedium

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

The website www.flensburg.de serves as the official digital portal for the city of Flensburg, Germany. It provides a broad range of municipal services and information including citizen services, social programs, cultural and educational resources, political and administrative details, and urban planning information. The site targets residents, local businesses, and visitors, positioning itself as a comprehensive government resource. The business model is that of a government municipal service provider, focusing on public service delivery rather than commercial activities. Technically, the site employs a mix of established JavaScript libraries such as jQuery 1.11.3, FontAwesome 5, jPlayer, and Flowplayer, indicating a moderately mature digital infrastructure. The site appears to be custom-built or uses a proprietary CMS, with good mobile optimization and accessibility features like visual assistance tools. Performance is moderate, with room for modernization of some libraries. From a security perspective, the site uses HTTPS and includes accessibility and privacy-related CSS and scripts, but lacks explicit security headers and published security policies. No vulnerabilities or exposed sensitive data were detected in the provided content. Privacy compliance is partial, with a cookie policy and consent mechanism present but no clear privacy policy or terms of service pages found. Incident response and vulnerability disclosure information are absent. Overall, the website is a trustworthy and professional government portal with good content quality and business credibility. However, it would benefit from enhanced privacy disclosures, security header implementation, and clearer contact information to improve compliance and user trust.

Scanned

NIS2 and GDPR posture

GDPR outside view
28/ 100 · High
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

5 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

    • 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

    • High

      No Cookie Consent Banner found

      GDPR requires explicit consent for non-essential cookies

      What to do: Implement a cookie consent banner that appears on first visit

  2. 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';…

  3. 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.

    • High

      Weak Protocols Supported

      Server supports weak protocols: TLSv1.1

      What to do: Disable TLS 1.0, TLS 1.1, and all SSL versions

      • CWE-327
      • OWASP A04:2025
      • ASVS V12.1.1

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

Keep watching flensburg.de

This scan found 25 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
67
Security headers
65
Email security
55
DNS health
70
Network security
100
GDPR outside view
28
Average
64

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 flensburg.de, from OffSeq Breach.

Total records
69
Employees
0
Customers
69
Third parties
0
Weak passwords
68%

14 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 flensburg.de.

Select it in the checkout above.

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

Open in Breach(opens in a new tab)Monitor on Breach(opens in a new tab)

Technical appendix

Business context, site observations and technical notes gathered during the scan, and the standards behind each reference.

Business context

Business profile

Flensburg.de is positioned as the official municipal website for the city of Flensburg, serving as a central hub for local government services and information. Its competitive advantage lies in its comprehensive coverage of citizen services, social programs, cultural events, and political administration, tailored specifically for the local population and stakeholders. The business model is non-commercial, focusing on public service delivery funded by municipal resources. Revenue streams are not applicable in the traditional sense but may include government funding and grants. The target customer segments include residents needing administrative services, local businesses seeking regulatory information, and visitors interested in cultural and tourism information. Growth indicators include the integration of digital services such as online appointment scheduling and digital agendas. The partnership ecosystem includes local government agencies, cultural institutions, and community organizations, as evidenced by linked partner domains. Strategic observations suggest a focus on digital accessibility and community engagement through extensive content and interactive features.

Security posture

The security posture of the website is moderate. The use of HTTPS ensures encrypted communication, which is fundamental for protecting user data. Accessibility features like eyeAble indicate attention to inclusive design, which indirectly supports security by reducing user errors. However, the absence of explicit security headers such as Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security reduces the defense-in-depth posture. No incident response or vulnerability disclosure information is published, which limits transparency and preparedness for security incidents. No vulnerable or outdated libraries with known critical vulnerabilities were detected, though the use of jQuery 1.11.3 suggests a need for updates to mitigate potential risks. The lack of exposed sensitive data is positive. Compliance gaps exist in privacy policy publication and GDPR explicit statements. Overall, the site demonstrates basic security hygiene but requires improvements in policy transparency and technical security controls.

Recommendations

  1. Publish a comprehensive and clear privacy policy aligned with GDPR requirements.
  2. Implement and configure security headers including Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security.
  3. Establish and publicize an incident response plan and vulnerability disclosure policy, including contact channels.
  4. Update third-party libraries, especially jQuery, to current supported versions to reduce vulnerability risks.
  5. Enhance contact information visibility including official emails and phone numbers for user support and data protection officer.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Stadt Flensburg
Description
Official website of the city of Flensburg providing information and services related to city administration, social services, culture, education, politics, and local economy.
Key services
Citizen services, Social services, Cultural and educational information, Political and administrative information, Job and career opportunities, Urban planning and development
Content quality
good
Branding
consistent

Technology

Stack
jQuery 1.11.3, FontAwesome 5, jPlayer, Flowplayer, Mustache.js, jQuery UI, Highslide JS
Performance
moderate
Mobile
good
Accessibility
good
SEO
good

Security

Observed score
70/100
Good practices seen
  • HTTPS usage assumed (based on URL)
  • No exposed sensitive data in HTML
  • Use of accessibility features (eyeAble visual assistance)

Analytics and tracking

Tracking level
minimal
Privacy practices
basic

Advertising

Transparency
poor

Site quality

Design
good
User experience
good
Content relevance
good
Navigation
good
Professionalism
good
Trustworthiness
high

Key observations

  1. Website is a comprehensive municipal government portal for Flensburg city.
  2. Content is extensive, well-structured, and primarily in German.
  3. No explicit privacy policy or terms of service pages detected in the provided HTML snippet.
  4. Cookie policy is present with consent mechanism.
  5. No direct contact emails or phone numbers found in the provided HTML snippet.
  6. Multiple external partner domains linked, mostly related to local government services and community.
  7. Use of older jQuery version (1.11.3) but modern FontAwesome 5 and other JS libraries.
  8. Accessibility features included (eyeAble visual assistance).
  9. No signs of advertising or tracking services detected.
  10. No security.txt or vulnerability disclosure information found.
Technical notes

Notes

The website uses a combination of legacy and modern JavaScript libraries, including jQuery 1.11.3, FontAwesome 5, jPlayer, and Flowplayer, indicating a mixed technology stack. The HTML structure is well-organized with extensive navigation menus and accessibility features such as the eyeAble visual assistance toolbar. The site includes responsive design elements and print-specific stylesheets, supporting good mobile and print usability. No explicit CMS was detected, suggesting a custom or proprietary content management system. Hosting details are not explicit, but the domain uses name servers from udag.de, a known DNS provider. Performance is moderate, with potential improvements by updating libraries and optimizing assets. SEO is supported by meta tags and structured navigation. Accessibility is enhanced by ARIA labels and keyboard navigation support. Overall, the technical infrastructure is solid but could benefit from modernization and enhanced security configurations.
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 flensburg.de. 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 flensburg.de.

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.