Skip to main content

Security report for obernburg.de

Stadt Obernburg a.Main · Government · Germany

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

Security score

60/100

Risk levelMedium

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

Stadt Obernburg a.Main operates a comprehensive municipal website providing residents and visitors with information about city administration, public services, events, tourism, and cultural offerings. The site is well-structured, primarily in German, and targets local citizens and tourists. It maintains a consistent brand presence and offers clear contact channels including phone, email, and a contact form. The website leverages modern web technologies such as JavaScript, jQuery, and accessibility tools to enhance user experience. Hosting is managed via UI-DNS, a common provider for German municipal sites. From a security perspective, the website enforces HTTPS and includes a cookie consent mechanism compliant with GDPR. It uses Matomo analytics configured to disable cookies by default, reflecting a privacy-conscious approach. However, no explicit security policy or incident response information is published, and security headers are not explicitly detected. The WHOIS data is limited but consistent with a legitimate municipal domain. No blocking or WAF mechanisms interfere with content access. Overall, the website demonstrates a solid technical and privacy foundation suitable for a government entity, with room for improvement in formal security disclosures and header implementations. The site is safe, free from adult or questionable content, and maintains a trustworthy online presence.

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

6 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 obernburg.de

This scan found 27 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
42
Security headers
60
Email security
70
DNS health
60
Network security
100
GDPR outside view
28
Average
60

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

The website represents a small-sized municipal government entity serving the Obernburg community in Germany. Its market position is that of a local authority providing essential public information and services. The business model is non-commercial, focused on governance, community engagement, and tourism promotion. Key services include event announcements, public facility information, and administrative contacts. The site fosters partnerships with regional and national government bodies and a partner city in Hungary. The digital presence supports community outreach and transparency, with moderate technical sophistication and good privacy practices.

Security posture

The security posture is moderate to good. HTTPS is enforced, and cookie consent is implemented with privacy-respecting analytics (Matomo with disabled cookies). No critical vulnerabilities or exposed sensitive data were found in the HTML content. However, the absence of explicit security policies, incident response contacts, and security headers like Content-Security-Policy or X-Frame-Options indicates areas for enhancement. No vulnerability disclosure or security.txt files are present. The site does not appear to use a WAF or other blocking mechanisms, which simplifies access but may expose it to certain risks. Overall, the site is secure for its purpose but could improve transparency and defense-in-depth measures.

Recommendations

  1. Publish a formal security policy page outlining security practices and commitments.
  2. Add incident response contact information, such as a security@ or abuse@ email address.
  3. Implement and configure security headers including Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security.
  4. Consider publishing a vulnerability disclosure policy or security.txt file to facilitate responsible reporting.
  5. Regularly review and update privacy and cookie policies to maintain GDPR compliance and transparency.

Contact details published on the site

Addresses
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Stadt Obernburg a.Main
Description
Die Stadt Obernburg stellt sich, ihre kommunalen Einrichtungen und die Partnerstädte vor. Ortsansässige Unternehmen und Veranstaltungstipps werden präsentiert.
Key services
Information about city administration, Event announcements, Public services and facilities, Tourism and cultural information
Content quality
good
Branding
consistent

Technology

Stack
JavaScript, jQuery, Slick Slider, Matomo Analytics, eyeAble accessibility tools
Performance
moderate
Mobile
good
Accessibility
good
SEO
good

Security

Observed score
80/100
Good practices seen
  • HTTPS enforced
  • Cookie consent mechanism
  • No exposed sensitive data in HTML

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 municipal government portal for Stadt Obernburg a.Main.
  2. Content is in German and targets local residents and visitors.
  3. Comprehensive cookie consent and privacy policy present.
  4. No terms of service or explicit security policy found.
  5. Contact information is clearly provided including phone, email, address, and contact form.
  6. Use of Matomo analytics with cookie consent disables cookies.
  7. Accessibility features included via eyeAble tools.
  8. No suspicious or malicious content detected.
  9. No WAF or blocking mechanisms detected; site fully accessible.
Technical notes

Notes

The website uses a modern JavaScript stack including jQuery and Slick Slider for UI components, and Matomo for analytics with privacy-focused configuration. Accessibility is enhanced via the eyeAble toolset. The CMS appears to be Umbraco, inferred from internal document references. Hosting is provided by UI-DNS, a reputable German DNS and hosting provider. Performance is moderate with responsive design and good mobile optimization. SEO is supported by proper meta tags and structured navigation. No broken elements or errors were detected in the HTML content. Opportunities exist to improve security headers and formalize security documentation.
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 obernburg.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 obernburg.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.