Skip to main content

Security report for moobly.de

Transportation · Germany

Medium risk. 4 critical or high findings in Security headers and SSL/TLS.

Security score

57/100

Risk levelMedium

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

Moobly is a German-language online platform specializing in ridesharing for mountain trips, enabling users to find and offer carpool rides to various alpine destinations. The website is well-structured with a clear focus on its niche market, leveraging Google Maps API for location-based services and providing a user-friendly interface for ride searches and postings. The platform targets outdoor enthusiasts and environmentally conscious travelers in German-speaking regions, promoting cost and CO2 savings through shared rides. Technically, the website employs modern web technologies including HTTPS, Google Fonts, and the Enhavo CMS framework. It demonstrates good mobile optimization and SEO practices, although some accessibility features are basic. The site integrates Google Analytics and Google Tag Manager for tracking, indicating moderate user tracking levels. From a security perspective, the site benefits from HTTPS and secure form implementations but lacks visible security headers and formal security policies. Privacy compliance is weak due to the absence of privacy and cookie policies and no explicit GDPR compliance indicators. Contact information is limited to a contact form without direct emails or phone numbers, which may affect user trust. Overall, Moobly presents a functional and focused service with good technical foundations but requires improvements in privacy compliance, security transparency, and contact information to enhance trust and regulatory adherence.

Scanned

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

NIS2 and GDPR posture

GDPR outside view
88/ 100 · Low
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

4 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. 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 moobly.de

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
72
Security headers
15
Email security
60
DNS health
65
Network security
40
GDPR outside view
88
Average
57

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 moobly.de, from OffSeq Breach.

No leaked records found

Breach holds no records for moobly.de right now. New leaks arrive continuously, so monitoring on Breach alerts you if that changes.

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

Moobly operates in the transportation sector with a specialized business model centered on ridesharing for mountain travel. Its competitive advantage lies in targeting a niche audience of mountain enthusiasts seeking cost-effective and eco-friendly travel options. The platform's revenue model likely includes user subscriptions or commissions on rides, although explicit monetization details are not visible. The user base is primarily German-speaking individuals interested in outdoor activities. The company appears small in size with no public parent or subsidiary affiliations. The partnership ecosystem is not explicitly detailed, but the use of Google services suggests reliance on established technology providers. Growth potential exists in expanding geographic coverage and enhancing user engagement through improved privacy and security features.

Security posture

The website demonstrates a moderate security maturity level with HTTPS enforced and secure form handling. However, it lacks comprehensive security headers such as Content-Security-Policy and X-Frame-Options, which are recommended to mitigate common web vulnerabilities. No exposed sensitive data or vulnerable libraries were detected in the analyzed content. The absence of a published security policy or incident response contact reduces transparency and preparedness for security incidents. GDPR compliance is not clearly addressed, and cookie consent mechanisms are missing, posing compliance risks. Overall, the security posture is adequate but requires enhancements in policy publication, header implementation, and compliance documentation to meet best practices.

Recommendations

  1. Publish a comprehensive privacy policy page clearly accessible from the homepage.
  2. Implement a cookie consent banner and detailed cookie policy to comply with GDPR.
  3. Add terms of service to clarify user rights and platform responsibilities.
  4. Enhance security headers including Content-Security-Policy, X-Frame-Options, and X-XSS-Protection.
  5. Provide direct contact information including emails and phone numbers for support and incident response.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Description
Nimm Mitfahrer*innen mit in die Berge, suche nach Fahrgemeinschaften zu Gipfelzielen, spare dabei Fahrtkosten und CO2 und finde neue Bergpartner*innen.
Key services
Ride search, Ride posting, Matching riders for mountain trips
Content quality
good
Branding
consistent

Technology

Stack
Google Maps API, Robots meta tag, CSS variables, JavaScript, Google Fonts
Frameworks
Enhavo CMS (detected via meta generator tag)
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • No visible exposed sensitive data
  • Use of secure forms with autocomplete and hidden fields

Analytics and tracking

Services
Google Analytics, Google Tag Manager
Tracking level
moderate
Privacy practices
poor

Advertising

Transparency
basic

Site quality

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

Key observations

  1. Website is a niche ridesharing platform focused on mountain trips.
  2. Content is in German and targets German-speaking users.
  3. No explicit privacy, cookie, or terms of service pages found.
  4. Contact is primarily via contact form; no direct emails or phone numbers found.
  5. Uses Google Maps API extensively for location and ride search features.
  6. No visible security policy or incident response information.
  7. Good use of HTTPS and modern web technologies.
  8. No WAF or blocking mechanisms detected.
  9. No adult or questionable content detected.
Technical notes

Notes

The website uses the Enhavo CMS platform and integrates Google Maps API for geolocation and ride search functionalities. It employs modern CSS with variables and responsive design techniques to ensure good mobile usability. The presence of Google Fonts and Google Tag Manager indicates reliance on third-party services for styling and analytics. Performance appears moderate, with no explicit indicators of slow loading but potential for optimization exists. Accessibility features are basic, with some ARIA labels and keyboard navigation support implied but not fully detailed. SEO is supported by meta tags including Open Graph and canonical links. Technical risks include reliance on external services and lack of advanced security headers.
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. 58/100Medium32 findingsView report
Reviews of this site

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