Skip to main content

Security report for marinexchange.com

MarineXchange Software GmbH · Technology · Austria

High risk. 8 critical or high findings in GDPR outside view, SSL/TLS and 2 other checks.

Security score

31/100

Risk levelHigh

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

MarineXchange Software GmbH operates a comprehensive enterprise software platform, MXP365, tailored for the cruise industry. The company provides a wide range of modules and digital solutions designed to enhance operational efficiency and guest experience onboard cruise ships. Positioned as a leading technology provider in this niche, MarineXchange leverages partnerships and acquisitions, such as Bytepoets, to expand its capabilities and market reach. The website reflects a mature digital presence with professional design and rich content targeting cruise lines and hospitality stakeholders. Technically, the website is built on WordPress using Elementor and Yoast SEO, indicating a modern CMS infrastructure with SEO and user experience considerations. However, performance metrics are lacking, and the site shows slow loading characteristics. Mobile optimization is good, but accessibility features are basic. The site integrates analytics and cookie consent tools, demonstrating awareness of privacy compliance. Security posture is a significant concern due to the absence of HTTPS and SSL certificates, lack of HSTS, and missing DNSSEC and CAA records. While no active vulnerabilities or malware are detected, the lack of encryption exposes users to risks and undermines trust. Privacy policies and cookie consent mechanisms are well implemented, supporting GDPR compliance. Overall, MarineXchange presents a credible and professional business with strong market positioning but must urgently address critical security gaps to protect its users and maintain trust. Strategic improvements in security infrastructure and performance optimization are recommended to align with industry best practices.

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

8 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

      No HTTPS encryption

      GDPR requires appropriate security measures for personal data

      What to do: Implement SSL/TLS certificate for HTTPS

  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.

    • Critical

      No HTTPS Encryption

      Website does not use HTTPS encryption, making all data transmission vulnerable to interception

      What to do: Implement SSL/TLS certificate and redirect all HTTP traffic to HTTPS

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

This scan found 20 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
0
Security headers
15
Email security
50
DNS health
85
Network security
20
GDPR outside view
18
Average
31

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

MarineXchange targets the cruise industry with an enterprise software platform that covers operational management and guest experience enhancement. Its business model focuses on providing modular, cloud-based solutions that integrate seamlessly across devices and shipboard systems. The company has established partnerships with technology and research organizations and has expanded through acquisitions like Bytepoets, indicating growth and innovation focus. Revenue streams likely include software licensing, subscriptions, and professional services. The target customers are cruise lines and hospitality operators seeking digital transformation. The company’s presence at industry events and expert sessions highlights active market engagement and thought leadership.

Security posture

The current security maturity level is low due to the lack of HTTPS and SSL, which is a critical vulnerability. The absence of key security headers and DNS security measures further weakens the security posture. No evidence of incident response or vulnerability disclosure policies is found, indicating potential gaps in security governance. Privacy compliance is supported by cookie consent and privacy policies, but the overall security framework is insufficient for enterprise standards. The business impact of these vulnerabilities includes potential data interception, loss of customer trust, and regulatory non-compliance risks.

Recommendations

  1. Implement a valid SSL/TLS certificate and enforce HTTPS across the entire website.
  2. Enable HTTP Strict Transport Security (HSTS) with includeSubDomains and preload options.
  3. Configure DNSSEC and CAA records to enhance domain security and prevent certificate mis-issuance.
  4. Add comprehensive security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options.
  5. Develop and publish a formal incident response and vulnerability disclosure policy to improve security governance.

Contact details published on the site

Addresses
Legal name
MarineXchange Software GmbH
Technical notes

Notes

The website uses a modern CMS (WordPress) with Elementor page builder and Yoast SEO plugin, indicating a well-supported and extensible platform. The tech stack includes jQuery, Swiper carousel, and Borlabs Cookie for consent management. However, the site lacks HTTPS, which is a major technical deficiency. Performance data is missing, but indications suggest slow loading times. Mobile responsiveness is good, but accessibility features are minimal. SEO is enhanced by meta tags and structured data (JSON-LD). Hosting appears to be on an Apache server with a single IPv4 address, but no CDN or advanced hosting details are evident. Technical debt includes missing security configurations and potential performance optimization opportunities.
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 marinexchange.com. 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 marinexchange.com.

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.