Skip to main content

Security report for protel.net

Protel (now Planet) · Hospitality · N/a

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

Security score

64/100

Risk levelMedium

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

Protel, now integrated into Planet, operates as a leading provider of hospitality software and payment solutions, targeting hotels, retail, and travel sectors. Their product suite includes property management systems, booking engines, and payment acceptance solutions designed to enhance guest experiences and streamline operations. The website reflects a mature digital presence with comprehensive content, multilingual support, and integration with Planet's broader ecosystem. Technically, the site is built on Drupal 10 with modern JavaScript libraries and analytics tools, but critically lacks a valid SSL/TLS certificate, exposing it to security risks and undermining user trust. Security headers and content security policies are implemented, but the absence of HTTPS significantly lowers the security posture. Privacy compliance is well addressed with a comprehensive GDPR-compliant privacy policy, though no cookie consent mechanism was detected. Overall, the site demonstrates strong business credibility and user experience but requires urgent security improvements to meet modern standards.

Scanned

NIS2 and GDPR posture

GDPR outside view
43/ 100 · High
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

3 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

  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

    • High

      No Cookie Consent Banner found

      GDPR requires explicit consent for non-essential cookies

      What to do: Implement a cookie consent banner that appears on first visit

Need hands-on remediation? Email guard@offseq.com

Keep watching protel.net

This scan found 15 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
55
Email security
50
DNS health
85
Network security
100
GDPR outside view
43
Average
64

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

Protel's market positioning as part of Planet leverages a strong portfolio in hospitality and retail payment solutions, supported by a partner ecosystem including Planet Payment and Planet ecampus. Their business model focuses on B2B SaaS and integrated payment services, targeting medium to large enterprises in hospitality and retail. The website content and case studies indicate a focus on customer success and operational efficiency. The multilingual approach and extensive product offerings suggest a global reach. The lack of explicit terms of service or security policy pages may indicate areas for improvement in transparency. The integration with multiple marketing and analytics platforms shows a data-driven approach to customer engagement and growth.

Security posture

The website exhibits a moderate security maturity level with implementation of key security headers and a strict content security policy. The use of Google reCAPTCHA v3 on forms helps mitigate automated abuse. However, the absence of a valid SSL/TLS certificate and lack of HTTPS support is a critical vulnerability that exposes user data and undermines trust. No HSTS or OCSP stapling is enabled, and TLS protocols are not supported, indicating outdated or incomplete security configurations. No explicit incident response or vulnerability disclosure information is available, which may impact incident handling readiness. Overall, the security posture is compromised by missing fundamental HTTPS protections despite other good practices.

Recommendations

  1. Install and enforce a valid SSL/TLS certificate to enable HTTPS across the entire site immediately.
  2. Enable modern TLS protocols (TLS 1.2 or higher) and configure HSTS with includeSubDomains and preload flags.
  3. Implement OCSP stapling and session resumption to improve security and performance.
  4. Add a cookie consent banner/mechanism to comply with privacy regulations and improve transparency.
  5. Publish explicit terms of service, security policy, and incident response information to enhance trust and compliance.
  6. Regularly audit third-party scripts and tracking tools to minimize privacy risks and optimize performance.
  7. Enhance contact information visibility by adding verified company emails and phone numbers for support and security contacts.
Technical notes

Notes

The website runs on a Debian-based Apache 2.4.62 server with PHP 8.2.28 and Drupal 10 CMS, indicating a modern and stable technology stack. The front-end uses multiple JavaScript libraries for analytics, tracking, and UI enhancements, including Google Tag Manager, reCAPTCHA, Hotjar, New Relic, and others. The site is multilingual with language detection and alternate hreflang tags, improving SEO and user experience. Performance metrics are not provided but inferred as slow due to zero load time/resource count data. Accessibility and SEO optimizations appear good based on meta tags and structured data. The lack of SSL/TLS is a major technical risk. DNS is managed via GoDaddy nameservers with no DNSSEC or CAA records, which could be improved for DNS security. Overall, the infrastructure is solid but requires security hardening and performance tuning.
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 protel.net. 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 protel.net.

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.