Skip to main content

Security report for bad-segeberg.de

Stadt Bad Segeberg · Government · Germany

High risk. 5 critical or high findings in Email security, Network security and 2 other checks.

Security score

49/100

Risk levelHigh

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

The website www.bad-segeberg.de serves as the official municipal portal for the city of Bad Segeberg in Germany. It provides comprehensive information about local government, city services, tourism, culture, social programs, and community engagement. The site targets residents, visitors, and local businesses, offering a broad range of resources including digital city maps, event calendars, and administrative contacts. The business model is that of a government entity focused on public service and community support. Technically, the website is built on TYPO3 CMS, a robust open-source content management system widely used in government and enterprise environments. It employs modern web technologies such as Bootstrap for responsive design, OpenLayers for mapping, and FontAwesome for icons. The site is hosted via INWX, a reputable domain and hosting provider. Performance is moderate with good mobile optimization and accessibility features, ensuring a positive user experience across devices. From a security perspective, the site enforces HTTPS and implements cookie consent mechanisms compliant with GDPR. It uses Matomo analytics with user consent to track usage while respecting privacy. No critical vulnerabilities or exposed sensitive data were detected in the analyzed content. However, security headers could be improved, and a formal security policy or incident response contact is not evident. The domain registration data is consistent and transparent, reinforcing the legitimacy of the site. Overall, the website demonstrates a solid security posture and good privacy compliance for a government portal. It offers trustworthy and professional content with clear navigation and user-friendly design. Strategic recommendations include enhancing security headers, publishing a security policy, and adding a security.txt file to facilitate vulnerability disclosures. These steps would further strengthen the site's security maturity and trustworthiness.

Scanned

NIS2 and GDPR posture

GDPR outside view
83/ 100 · Low
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. Email security

    SPF, DKIM and DMARC stop others sending email that looks like it comes from your domain, a common route to phishing and invoice fraud.

    • Critical

      No email authentication configured

      Domain is vulnerable to email spoofing

      What to do: Implement SPF, DKIM, and DMARC immediately

  2. Network security

    Services reachable from the internet are the first thing attackers probe. Anything open that does not need to be should be closed.

    • Critical

      Critical Service Exposed: MySQL

      Port 3306 (MySQL) is publicly accessible - MySQL - Database server

      What to do: Immediately restrict access to MySQL using firewall or VPN

      • NIS2 21(2)(e)
      • IR 2024/2690 6.7.2(f): Implementing Regulation (EU) 2024/2690, Annex point 6.7.2(f): Network security
      • NIST CM-7: NIST SP 800-53 Rev. 5 CM-7: Least Functionality
      • NIST SC-7: NIST SP 800-53 Rev. 5 SC-7: Boundary Protection
    • High

      High-Risk Service Exposed: FTP

      Port 21 (FTP) is publicly accessible - FTP - Often unencrypted file transfer

      What to do: Consider restricting access to FTP or implementing strong authentication

      • NIS2 21(2)(e)
      • IR 2024/2690 6.7.2(f): Implementing Regulation (EU) 2024/2690, Annex point 6.7.2(f): Network security
      • NIST CM-7: NIST SP 800-53 Rev. 5 CM-7: Least Functionality
      • NIST SC-7: NIST SP 800-53 Rev. 5 SC-7: Boundary Protection

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

  4. 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 bad-segeberg.de

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. 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
62
Security headers
85
Email security
60
DNS health
65
Network security
0
GDPR outside view
83
Average
59
After the cap
49

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 · found on this site
  • 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 bad-segeberg.de, from OffSeq Breach.

No leaked records found

Breach holds no records for bad-segeberg.de right now. New leaks arrive continuously, so monitoring on Breach alerts you if that changes.

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

Bad Segeberg's official website positions itself as a central hub for municipal information and services, catering to a diverse audience including residents, tourists, and local businesses. The site leverages partnerships with regional service providers and integrates external resources such as tourism boards and public service portals. Its competitive advantage lies in comprehensive local content, digital tools like interactive maps, and community engagement features. Revenue streams are typical of government entities, primarily funded by public budgets. The site reflects a medium-sized municipal operation with a focus on transparency, accessibility, and digital service delivery. Growth indicators include ongoing updates to city planning, social programs, and cultural events. The partnership ecosystem includes regional tourism and public service organizations, enhancing the city's outreach and service quality.

Security posture

The website exhibits a mature security posture appropriate for a government portal. HTTPS is enforced, and privacy compliance is evident through detailed cookie and privacy policies with consent mechanisms. The use of Matomo analytics is privacy-conscious, relying on user consent. No critical security flaws or vulnerabilities were identified in the content. However, the absence of explicit security headers such as Content-Security-Policy and X-Frame-Options suggests room for improvement. There is no visible incident response or security contact information, which is a gap in transparency and readiness. The site does not publish a security.txt file or vulnerability disclosure policy. Overall, the security culture appears cautious but could benefit from formalizing incident response and enhancing technical controls.

Recommendations

  1. Implement comprehensive security headers including Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options to mitigate common web attacks.
  2. Publish a clear security policy and provide dedicated contact channels for incident reporting and vulnerability disclosures.
  3. Add a security.txt file at the root domain to facilitate responsible vulnerability reporting.
  4. Regularly audit third-party scripts and libraries to ensure no known vulnerabilities are present.
  5. Enhance user trust by including visible trust seals or certifications related to security and privacy compliance.

Contact details published on the site

Addresses
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Stadt Bad Segeberg
Description
Official municipal website providing information about the city of Bad Segeberg, including local government, services, tourism, culture, social services, and community engagement.
Key services
City administration information, Tourism and cultural event information, Social services and community programs, Digital city planning and maps, Job and career opportunities in city administration
Content quality
good
Branding
consistent

Technology

Stack
TYPO3 CMS, Bootstrap CSS, OpenLayers (JavaScript mapping library), FontAwesome icons, Matomo Analytics
Frameworks
TYPO3 CMS
Performance
moderate
Mobile
good
Accessibility
good
SEO
good

Security

Observed score
80/100
Good practices seen
  • HTTPS enforced
  • Cookie consent mechanism implemented
  • No exposed sensitive data in HTML
  • Use of async loading for analytics scripts

Analytics and tracking

Services
Matomo
Tracking level
moderate
Privacy practices
good

Advertising

Tracking pixels
Matomo
Marketing tools
Matomo Analytics
Transparency
basic

Site quality

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

Key observations

  1. Website is a well-structured official municipal portal for Bad Segeberg, Germany.
  2. Content is comprehensive and covers multiple city services and information.
  3. Good implementation of privacy and cookie policies with user consent.
  4. Use of TYPO3 CMS and modern web technologies.
  5. No critical security issues or vulnerabilities detected in the provided content.
  6. No contact emails or phone numbers explicitly found in the HTML content provided.
  7. No terms of service page detected.
  8. External links mostly to official or related government and community service domains.
  9. Matomo analytics used with consent mechanism.
  10. No WAF or blocking mechanisms detected.
Technical notes

Notes

The website is built on TYPO3 CMS, leveraging Bootstrap for responsive design and OpenLayers for interactive mapping. The technology stack is modern and well-suited for government portals. Performance is moderate, with asynchronous loading of analytics scripts to optimize speed. The site demonstrates good mobile optimization and accessibility features, including keyboard navigation and ARIA labels. SEO is supported by proper meta tags and structured navigation. Hosting is managed by INWX, a reputable provider. Technical risks are minimal but include the lack of advanced security headers and formal vulnerability disclosure mechanisms. Opportunities exist to modernize security practices and improve performance monitoring.
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 bad-segeberg.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 bad-segeberg.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.