Skip to main content

Security report for try.be

Five Nines Digital Ltd · Hospitality · United Kingdom

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

Security score

54/100

Risk levelMedium

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

Trybe is a specialized SaaS provider offering next-generation bookings and business management software tailored for the spa and leisure industry. The platform targets spa businesses seeking to streamline their booking processes, inventory management, team scheduling, and payment processing. Positioned as a cloud-based, open-API solution, Trybe emphasizes ease of use, integration capabilities, and operational efficiency. The company is UK-based, operating under Five Nines Digital Ltd, and holds ISO27001 certification, reinforcing its commitment to security standards. Technically, the website is built using modern web technologies including React and Gatsby, with Tailwind CSS for styling. Hosting appears to be on AWS infrastructure. While the site is well-designed, mobile-optimized, and rich in content, performance is hindered by slow load times and a high number of resources. SEO and accessibility features are well implemented, contributing to a positive user experience. From a security perspective, the site lacks a valid SSL certificate and does not support modern TLS protocols, which is a critical vulnerability impacting user trust and data protection. No major vulnerabilities or exposed sensitive data were detected, and the presence of ISO27001 certification and GDPR-compliant privacy policies indicate a mature security posture. However, improvements in SSL/TLS configuration and security headers are urgently recommended. Overall, Trybe presents a professional and credible business offering with strong market positioning in the hospitality sector. The main risk lies in its current SSL/TLS configuration, which should be addressed promptly to ensure secure communications and maintain customer trust.

Scanned

NIS2 and GDPR posture

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

      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 Privacy Policy found

      GDPR requires a clear and accessible privacy policy

      What to do: Add a comprehensive privacy policy page and link to it prominently

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

This scan found 22 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
50
Security headers
15
Email security
75
DNS health
85
Network security
100
GDPR outside view
0
Average
54

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

Trybe operates in the hospitality sector, focusing on spa and leisure businesses. Its SaaS model provides a comprehensive suite of services including online bookings, inventory management, team rota integration, payment processing, membership management, and digital intake forms. The company leverages partnerships with scheduling (Calendly) and payment (Stripe) providers to enhance its offerings. Client testimonials and industry features demonstrate market acceptance and growth potential. The business targets small to medium-sized spa operators seeking digital transformation and operational efficiency. Its cloud-based platform and open API facilitate integration with other business tools, supporting scalability and customization. The presence of ISO27001 certification and membership in the UK Spa Association further strengthen its market credibility.

Security posture

The security posture of Trybe is mixed. The company demonstrates good security practices through ISO27001 certification, GDPR-compliant privacy policies, and secure handling of payment data via PCI-compliant checkout processes. No critical vulnerabilities such as Heartbleed or POODLE were found, and DNS records include SPF for email protection. However, the absence of a valid SSL certificate and disabled TLS protocols represent significant security gaps, exposing users to potential interception and undermining trust. The lack of security headers and session resumption mechanisms further weakens the security posture. Incident response information and vulnerability disclosure policies are not evident, indicating areas for improvement in security governance and transparency.

Recommendations

  1. Obtain and deploy a valid SSL/TLS certificate to enable HTTPS and secure user communications.
  2. Enable and enforce modern TLS protocols (TLS 1.2 and 1.3) and disable deprecated versions.
  3. Implement HTTP security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options.
  4. Enable OCSP stapling and session resumption to improve security and performance.
  5. Develop and publish a vulnerability disclosure policy and incident response contact information.
  6. Optimize website performance to reduce load times and resource counts.
  7. Maintain and regularly update privacy and cookie policies to ensure ongoing GDPR compliance.

Contact details published on the site

Addresses
Legal name
Five Nines Digital Ltd
Technical notes

Notes

The website is built on a modern React/Gatsby stack with Tailwind CSS for styling, hosted on AWS infrastructure. It uses third-party services such as HubSpot for marketing and analytics, Stripe for payment processing, and Calendly for scheduling demos. The site is mobile-optimized and accessible, with good SEO practices including meta tags and Open Graph data. However, performance is slow with a load time exceeding 25 seconds and a high number of resources (211). The SSL/TLS configuration is inadequate, lacking a valid certificate and disabling all TLS versions, which is a critical technical risk. The site uses HubSpot scripts and Google verification TXT records, indicating integration with marketing and email services. Overall, the technical infrastructure is modern but requires urgent security and performance 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 try.be. 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 try.be.

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.