Skip to main content

Security report for alex.info

Regentalbahn GmbH · Transportation · Germany

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

Security score

63/100

Risk levelMedium

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

The website www.laenderbahn.com/alex/ represents the alex regional train service operated by Regentalbahn GmbH, a subsidiary of the Netinera group. It offers daily direct train connections between Germany and the Czech Republic, targeting commuters and travelers in this region. The site provides comprehensive travel information, ticket sales, real-time updates, and customer service resources. The business model focuses on regional transportation services with a strong emphasis on customer convenience and cross-border connectivity. Technically, the website is built on Craft CMS and employs modern JavaScript libraries and frameworks such as jQuery and Mmenu for mobile navigation. It integrates multiple analytics and tracking tools including Matomo, Google Tag Manager, Facebook Pixel, and Hotjar, all managed with a cookie consent mechanism to comply with privacy regulations. The site is mobile-optimized, accessible, and SEO-friendly, providing a good user experience. From a security perspective, the website enforces HTTPS and uses CSRF tokens to protect forms. While explicit HTTP security headers were not detected in the provided data, the site follows best practices in data protection and privacy compliance, including a comprehensive privacy policy and cookie management. No vulnerabilities or exposed sensitive data were found. However, the absence of WHOIS data for the domain raises concerns about domain registration legitimacy, although the website branding and content strongly indicate a legitimate business. Overall, the site is professional, trustworthy, and well-maintained, serving its target audience effectively. The main risk lies in the missing WHOIS registration data, which should be verified externally. Strategic recommendations include enhancing HTTP security headers, publishing a vulnerability disclosure policy, and providing explicit incident response contacts to further strengthen security posture.

Scanned

NIS2 and GDPR posture

GDPR outside view
68/ 100 · Medium
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. 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';…
  2. GDPR outside view

    These are the privacy signals visitors and data protection authorities look for under GDPR.

    • 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

  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 alex.info

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
47
Security headers
20
Email security
70
DNS health
70
Network security
100
GDPR outside view
68
Average
63

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 alex.info, from OffSeq Breach.

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

1 subdomain 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 alex.info.

Select it in the checkout above.

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

Technical appendix

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

Business context

Business profile

Regentalbahn GmbH operates the alex train service as a regional transportation provider connecting key cities in Germany and the Czech Republic. The company benefits from its parent company Netinera's infrastructure and market presence. The business targets daily commuters, tourists, and regional travelers, offering ticket sales both onboard and online. The website supports customer engagement through travel tips, news updates, and a newsletter. Partnerships with recruitment platforms and social media presence indicate active brand management and growth orientation. The company leverages digital tools for customer service and marketing, positioning itself competitively in the regional rail transport sector.

Security posture

The website demonstrates a mature security posture with HTTPS enforcement, CSRF protection, and cookie consent mechanisms aligned with GDPR requirements. The use of multiple analytics and tracking services is managed transparently with user consent. No critical vulnerabilities or exposed sensitive data were identified. However, the lack of visible HTTP security headers such as Content Security Policy or HSTS suggests room for improvement. The absence of a published incident response or vulnerability disclosure policy limits transparency in security incident handling. Overall, the security measures are adequate for the business type but could be enhanced to meet higher standards.

Recommendations

  1. Implement comprehensive HTTP security headers including CSP, HSTS, X-Frame-Options, and X-XSS-Protection.
  2. Publish a security.txt file or dedicated vulnerability disclosure page to facilitate responsible reporting.
  3. Provide explicit contact information for incident response or security concerns on the website.
  4. Regularly audit and update third-party scripts and analytics tools to mitigate potential vulnerabilities.
  5. Verify and update domain WHOIS registration to ensure transparency and trustworthiness.

Contact details published on the site

Addresses
Legal name
Regentalbahn GmbH
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Regentalbahn GmbH
Description
alex offers daily direct and comfortable train connections between cities in Germany and Czech Republic including Munich, Landshut, Regensburg, Schwandorf, Pilsen and Prague.
Key services
Train transportation, Ticket sales onboard and online, Travel information and real-time updates
Content quality
good
Branding
consistent

Technology

Stack
JavaScript, jQuery, FontAwesome, Matomo Analytics, Google Tag Manager, Facebook Pixel, Hotjar
Frameworks
Mmenu (mobile menu), Craft CMS (implied by CRAFT_CSRF_TOKEN)
Performance
moderate
Mobile
good
Accessibility
good
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • CSRF token implemented
  • Cookie consent mechanism
  • No exposed sensitive data in HTML

Analytics and tracking

Services
Matomo, Google Tag Manager, Facebook Pixel, Hotjar
Tracking level
moderate
Privacy practices
good

Advertising

Tracking pixels
Facebook Pixel, Matomo Analytics, Hotjar
Transparency
good

Site quality

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

Key observations

  1. Website is fully accessible with rich content in German language
  2. Strong focus on regional train services between Germany and Czech Republic
  3. Comprehensive navigation and service information
  4. Use of multiple analytics and tracking tools with cookie consent
  5. No signs of adult or malicious content
  6. WHOIS data missing, which reduces trust score but website branding is consistent with known transportation company
Technical notes

Notes

The website is built on Craft CMS with a modern JavaScript-based front end including jQuery and Mmenu for responsive navigation. It integrates several analytics and marketing tools such as Matomo, Google Tag Manager, Facebook Pixel, and Hotjar, indicating a sophisticated digital marketing strategy. The site is mobile-optimized and accessible, with good SEO practices evident in meta tags and structured navigation. Performance is moderate, with potential for optimization in loading speed. The absence of explicit hosting provider information limits full infrastructure assessment. Overall, the technical implementation supports a professional and user-friendly online presence.
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 alex.info. 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 alex.info.

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.