Skip to main content

Security report for gaia-x4futuremobility.de

Gaia-X 4 Future Mobility · Transportation · Germany

Medium risk. 7 critical or high findings in GDPR outside view, Email security and 1 other check.

Security score

59/100

Risk levelMedium

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

Gaia-X 4 Future Mobility is a collaborative project family focused on developing and implementing future mobility applications based on the Gaia-X initiative. It is funded by the German Federal Ministry for Economic Affairs and Climate Action and coordinated by the DLR Institute for AI Security. The initiative involves about 80 participants from industry and research, aiming to build an open, decentralized data and service ecosystem for mobility. The website provides detailed information about the six constituent projects, their goals, participants, and related initiatives. Technically, the site is built on the Webflow platform, uses Google Fonts and jQuery, and is hosted on a CDN. However, the site lacks a valid SSL certificate and does not enforce HTTPS, which is a critical security concern. Privacy and terms of service pages are present, but no cookie consent mechanism is detected. Overall, the site is professionally designed with good content relevance and navigation but requires urgent security improvements.

Scanned

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

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

  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 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 gaia-x4futuremobility.de

This scan found 24 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
30
Email security
40
DNS health
75
Network security
100
GDPR outside view
18
Average
59

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 project family holds a strong market position as an official Gaia-X Lighthouse project within the German Gaia-X Hub Mobility domain. It benefits from government funding and collaboration with prominent research institutions and industry players. The business model revolves around publicly funded R&D to create interoperable, secure data ecosystems for mobility applications, targeting IT providers, developers, municipalities, and industry stakeholders. The partnership ecosystem includes major German research centers, automotive companies, and technology providers. Growth indicators include active project development, multiple use cases, and integration with broader Gaia-X initiatives. The website reflects a mature collaborative effort with clear strategic alignment to European digital sovereignty and mobility transformation goals.

Security posture

The website's security posture is weak due to the absence of a valid SSL certificate and lack of HTTPS enforcement, exposing users to potential data interception risks. No security headers are present, and critical DNS security features like DNSSEC and DMARC are missing. The site does not implement cookie consent mechanisms, which may impact GDPR compliance. No incident response or vulnerability disclosure policies are found. While the project itself focuses on secure data ecosystems, the website infrastructure does not reflect strong security practices, representing a risk to user trust and data protection. Immediate remediation of SSL/TLS and security headers is recommended to improve the security maturity.

Recommendations

  1. Obtain and deploy a valid SSL/TLS certificate to enable HTTPS across the entire website.
  2. Implement HTTP Strict Transport Security (HSTS) with includeSubDomains and preload options.
  3. Add essential security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options.
  4. Configure DNSSEC and add DMARC records to enhance DNS and email security.
  5. Introduce a cookie consent banner/mechanism to comply with GDPR requirements.
  6. Publish a security policy and vulnerability disclosure page to improve transparency and incident response readiness.
  7. Regularly audit and update third-party libraries and dependencies to avoid vulnerabilities.
Technical notes

Notes

The website is built using the Webflow CMS platform, leveraging Google Fonts and jQuery 3.5.1. It is hosted on a CDN infrastructure, likely Cloudflare, based on DNS and IP data. Performance is moderate with a page load time of approximately 3.4 seconds and 33 resources loaded. The site is mobile optimized with responsive design and clear navigation. SEO is basic with meta viewport and title tags but lacks advanced SEO features. Accessibility is basic with some ARIA roles and language attributes but no explicit accessibility enhancements detected. The absence of HTTPS and security headers is a significant technical risk. The site uses external links extensively to official Gaia-X and government domains, reflecting a well-integrated ecosystem. Overall, the technical infrastructure is modern but requires security hardening and privacy compliance improvements.
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 gaia-x4futuremobility.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 gaia-x4futuremobility.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.