Skip to main content

Security report for saarbahn.de

Saarbahn GmbH · Transportation · Germany

Medium risk. 6 critical or high findings in GDPR outside view and Security headers.

Security score

65/100

Risk levelMedium

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

Saarbahn GmbH is a regional public transportation company serving the Saarbrücken area in Germany, providing reliable local transit services including tram and bus operations. It operates as a subsidiary of Stadtwerke Saarbrücken GmbH, a major regional utility and employer. The website offers comprehensive information on timetables, ticketing options including mobile tickets, service updates, and customer support. Technically, the site uses a combination of Apache server, jQuery, Foundation framework, and other modern JavaScript libraries to deliver a responsive and user-friendly experience. However, the SSL/TLS configuration is currently invalid, lacking a proper certificate and modern protocol support, which poses a significant security risk. Security headers are partially implemented, but critical improvements are needed to secure communications and protect user data. Privacy compliance is moderate with a clear privacy policy but no cookie consent mechanism detected. Overall, the site is functional and professional but requires urgent security enhancements to meet modern standards.

Scanned

This is an earlier scan of saarbahn.de. View the latest report

NIS2 and GDPR posture

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

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

  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 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 X-Frame-Options header

      Prevents clickjacking attacks

      What to do: Add "X-Frame-Options: DENY" or "X-Frame-Options: SAMEORIGIN"

    • 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 saarbahn.de

This scan found 16 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
90
Security headers
45
Email security
50
DNS health
85
Network security
100
GDPR outside view
18
Average
65

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

Saarbahn GmbH holds a strong position as a regional transport provider in Saarbrücken, leveraging its affiliation with Stadtwerke Saarbrücken GmbH to maintain operational stability and market presence. Its business model focuses on public transit services with key revenue streams from ticket sales and public funding. The company targets daily commuters, occasional travelers, and regional residents requiring reliable mobility solutions. The website supports this by providing easy access to timetable information, ticket purchasing, and service alerts. Partnerships with regional transport associations and carsharing services enhance its service ecosystem. The company shows growth orientation through investments in new tram-train vehicles and hydrogen buses, signaling commitment to sustainable and modern transport solutions.

Security posture

The current security posture of the Saarbahn website is weak due to the absence of a valid SSL certificate and lack of HTTPS enforcement, exposing users to potential interception and man-in-the-middle attacks. While some security headers like XSS protection and content type options are present, the lack of HSTS, OCSP stapling, and session resumption reduces overall security effectiveness. No explicit incident response or vulnerability disclosure policies are found, indicating limited readiness for security incidents. The site does not implement cookie consent mechanisms, which may affect GDPR compliance. The use of modern JavaScript libraries is positive but requires regular updates to avoid vulnerabilities. Immediate remediation of SSL/TLS issues is critical to protect user data and maintain trust.

Recommendations

  1. Obtain and deploy a valid SSL/TLS certificate to enable secure HTTPS connections.
  2. Enable and enforce modern TLS protocols (TLS 1.2 and TLS 1.3) and disable outdated versions.
  3. Implement HTTP Strict Transport Security (HSTS) with includeSubDomains and preload options.
  4. Add a cookie consent banner to comply with GDPR and inform users about tracking.
  5. Publish explicit security and incident response policies including contact channels for reporting issues.
Technical notes

Notes

The website is built on a solid technical foundation using Apache web server and a mix of popular JavaScript libraries such as jQuery, Owl Carousel, and Foundation framework for responsive design. The CMS appears custom or proprietary, with backend editing URLs visible in metadata. Performance metrics are not provided but inferred to be moderate due to multiple scripts and large SVG graphics. Mobile optimization is good with responsive navigation and UI elements. SEO is supported by proper meta tags and canonical links. However, the invalid SSL certificate and disabled TLS protocols represent significant technical debt and risk. Hosting details are limited but the IP and server headers suggest a dedicated or managed hosting environment. Overall, the technical stack is modern but requires security upgrades and performance tuning.
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

Earlier scans of this domain

  1. 52/100Medium26 findings · partial scanView report
Reviews of this site

Share your experience with saarbahn.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 saarbahn.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.