Skip to main content

Security report for bezirk-oberfranken.de

Bezirk Oberfranken · Government · Germany

High risk. 5 critical or high findings in GDPR outside view, Network security and 1 other check.

Security score

49/100

Risk levelHigh

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

Bezirk Oberfranken operates as a regional government authority in Germany, providing a wide range of public services including social assistance, healthcare, cultural programs, agricultural education, and administrative governance. The website serves as a comprehensive portal for residents and stakeholders, offering detailed information and access to various services. The organization maintains a strong market position as a public sector entity with a focus on community support and regional development. Technically, the website is built on TYPO3 CMS with Bootstrap and Font Awesome, hosted by agenturserver, and employs Matomo analytics configured with privacy considerations. The site demonstrates good mobile optimization, accessibility, and SEO practices, reflecting a mature digital infrastructure. Security posture is adequate with HTTPS enabled and privacy-conscious analytics, but lacks some security headers and explicit privacy policies. Overall, the site is professional, trustworthy, and safe for general audiences, though improvements in privacy transparency and security policies are recommended.

Scanned

NIS2 and GDPR posture

GDPR outside view
43/ 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

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

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

Keep watching bezirk-oberfranken.de

This scan found 22 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
85
Security headers
65
Email security
85
DNS health
60
Network security
0
GDPR outside view
43
Average
56
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 bezirk-oberfranken.de, from OffSeq Breach.

Total records
14
Employees
0
Customers
14
Third parties
0
Weak passwords
0%

4 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 bezirk-oberfranken.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

Bezirk Oberfranken is positioned as a large government entity serving the Oberfranken district in Germany. Its competitive advantage lies in its comprehensive service offerings across social, health, cultural, and agricultural sectors, supported by a well-structured digital presence. The business model is public service-oriented, funded by government budgets, focusing on community welfare and regional development. The target customers include residents, social service beneficiaries, cultural participants, and agricultural stakeholders. The website indicates active engagement through social media channels and provides extensive informational resources. Growth indicators include diverse sector coverage and digital modernization via TYPO3 CMS. The partnership ecosystem includes hosting providers and analytics services, with no suspicious affiliations detected.

Security posture

The website maintains a moderate security maturity level with HTTPS enforced and privacy-respecting analytics configurations. However, the absence of key security headers such as Content-Security-Policy and X-Frame-Options reduces defense-in-depth. No exposed sensitive data or vulnerable libraries were detected in the provided content. The lack of published incident response or vulnerability disclosure policies indicates room for improvement in security governance and transparency. Overall, the security posture is adequate for a government portal but could be enhanced by adopting additional best practices and formalizing security policies.

Recommendations

  1. Publish a comprehensive privacy policy page detailing data processing and user rights to improve GDPR compliance and user trust.
  2. Implement and configure essential security headers (Content-Security-Policy, X-Frame-Options, X-Content-Type-Options) to strengthen protection against common web attacks.
  3. Establish and publicize an incident response and vulnerability disclosure policy to enhance transparency and readiness.
  4. Provide clear contact information for the Data Protection Officer to comply with data protection regulations and facilitate user inquiries.
  5. Regularly audit and update third-party scripts and libraries to mitigate potential vulnerabilities and maintain security hygiene.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Bezirk Oberfranken
Description
Übersicht über Einrichtungen und Aufgaben des Bezirks Oberfranken. Dazu zählen Hilfen für Menschen mit Behinderung und die Hilfe zur Pflege.
Key services
Social assistance and care services, Health services including psychiatric and nursing facilities, Cultural programs and heritage preservation, Agricultural education and support, Public administration and governance
Content quality
good
Branding
consistent

Technology

Stack
TYPO3 CMS, Bootstrap, Font Awesome, Matomo Analytics
Frameworks
TYPO3 CMS, Bootstrap
Performance
moderate
Mobile
good
Accessibility
good
SEO
good

Security

Observed score
75/100
Good practices seen
  • HTTPS enabled
  • Matomo analytics configured with DoNotTrack and disableCookies
  • Cookie consent mechanism implemented

Analytics and tracking

Services
Matomo
Tracking level
minimal
Privacy practices
basic

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 comprehensive regional government portal for Bezirk Oberfranken in Germany.
  2. Content is extensive, covering multiple sectors including social services, health, culture, agriculture, and administration.
  3. No privacy policy or terms of service pages explicitly found in the provided content.
  4. Cookie consent mechanism is implemented with a dedicated stylesheet and configuration.
  5. Use of Matomo analytics with privacy-respecting settings (DoNotTrack, disableCookies).
  6. No visible security headers detected in the provided data; HTTPS is enabled.
  7. No contact emails or phone numbers explicitly found in the truncated content; contact forms and social media links are present.
  8. No vulnerability disclosure or incident response information found.
  9. No adult or explicit content detected; content is safe for general audiences.
  10. WHOIS data is limited but does not raise suspicion; domain appears to be professionally managed.
Technical notes

Notes

The website leverages TYPO3 CMS, a robust open-source content management system, combined with Bootstrap for responsive design and Font Awesome for iconography. Hosting is managed by agenturserver, as indicated by the nameservers. Performance is moderate with good mobile optimization and accessibility features. SEO is supported by proper meta tags and structured navigation. The use of Matomo analytics with privacy features demonstrates a commitment to user privacy. However, the absence of visible security headers and incomplete privacy documentation suggest technical debt in security and compliance areas. Modernization opportunities include enhancing security configurations and expanding transparency through published policies.
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 bezirk-oberfranken.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 bezirk-oberfranken.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.