Skip to main content

Security report for hotelcms.hu

Hospitality · Hungary

Medium risk. 8 critical or high findings in GDPR outside view, Security headers and 1 other check.

Security score

65/100

Risk levelMedium

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

The website hotelcms.hu serves as an administrative login portal for RoomSome, a hospitality management system likely targeting hotels or accommodation providers in Hungary. The platform provides secure access to administrative functions, including user authentication with two-factor authentication support. The site is designed primarily for internal users rather than public visitors, which explains the minimal public-facing content and absence of marketing materials. The business appears to be a small-sized entity founded in 2015, focusing on providing software solutions for the hospitality sector. Technically, the website uses a modern but basic technology stack including jQuery, Bootstrap 4, and Noty for notifications. The design is functional but basic, with some mobile responsiveness and accessibility features. External dependencies are minimal, limited to Google Fonts and common JavaScript libraries. SEO and public content optimization are minimal due to the nature of the site as an admin portal. From a security perspective, the site implements two-factor authentication, which is a positive security control for user access. However, there is no visible evidence of security headers such as Content Security Policy or HSTS, and no privacy or cookie policies are present. The absence of contact information and security incident response details limits transparency and trust. No WAF or blocking mechanisms were detected, and the domain WHOIS data is consistent and appropriate for the business age and type. Overall, the site is functional for its intended purpose but lacks comprehensive privacy, security, and compliance disclosures. Strategic improvements in security headers, privacy policies, and contact transparency would enhance trust and compliance posture.

Scanned

NIS2 and GDPR posture

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

    • 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. 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 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 hotelcms.hu

This scan found 21 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
82
Security headers
45
Email security
70
DNS health
85
Network security
100
GDPR outside view
10
Average
65

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

RoomSome operates in the hospitality sector, providing a hotel management system accessible via an admin portal. The business model is B2B SaaS, targeting hotel administrators and staff. The company appears to be small-sized and established since 2015, indicating some market presence and operational maturity. The lack of public marketing content suggests a focus on direct client relationships or private deployments. No partnerships or subsidiaries are evident from the site. The platform's competitive advantage includes integrated two-factor authentication and a streamlined admin interface. Revenue streams likely derive from software licensing or subscription fees. Growth indicators and strategic partnerships are not publicly visible.

Security posture

The security posture shows moderate maturity with the implementation of two-factor authentication for login security. However, the absence of security headers such as Content-Security-Policy, X-Frame-Options, and HSTS reduces protection against common web attacks. No privacy or cookie policies are present, indicating compliance gaps with GDPR and related regulations. Incident response and vulnerability disclosure mechanisms are not publicly documented, limiting readiness and transparency. The site uses AJAX for login processes with error handling, which is positive. Overall, the security controls are functional but could be significantly improved to meet best practices and regulatory requirements.

Recommendations

  1. Implement HTTPS with strict transport security (HSTS) and ensure all resources load securely.
  2. Add comprehensive security headers including Content-Security-Policy, X-Frame-Options, and X-XSS-Protection.
  3. Publish clear privacy and cookie policies to comply with GDPR and enhance user trust.
  4. Provide visible contact information and incident response channels for security issues.
  5. Conduct regular security audits and vulnerability assessments to identify and remediate risks.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Description
Admin interface for RoomSome, a hospitality-related service platform, likely a hotel or accommodation management system.
Key services
Hotel management system, User authentication with two-factor authentication, Admin dashboard access
Content quality
basic
Branding
consistent

Technology

Stack
jQuery, jQuery UI, Bootstrap 4, Noty (notifications), FontAwesome 5, Google Fonts (Roboto)
Frameworks
Bootstrap
Performance
moderate
Mobile
basic
Accessibility
basic
SEO
poor

Security

Observed score
50/100
Good practices seen
  • Two-factor authentication (TFA) support
  • AJAX-based login with error handling
  • Password and TFA code input fields with placeholders

Analytics and tracking

Tracking level
minimal
Privacy practices
poor

Advertising

Transparency
poor

Site quality

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

Key observations

  1. Website is an admin login portal for RoomSome, a hospitality management system.
  2. No public-facing marketing or informational content detected.
  3. No privacy, cookie, or terms of service policies found on the login page.
  4. Two-factor authentication is implemented, indicating a focus on security for user access.
  5. No contact information or business details are publicly displayed on this page.
  6. External resources are limited to Google Fonts and common JS libraries.
  7. No analytics or advertising scripts detected.
  8. No social media or external business links present.
Technical notes

Notes

The website uses a standard technology stack with jQuery, Bootstrap 4, and Noty for UI and notifications. The HTML is well-structured with responsive design elements, though mobile optimization is basic. External dependencies are minimal, reducing attack surface. No CMS or hosting provider details are evident. Performance is moderate with no explicit optimization indicators. SEO is minimal due to the admin nature of the site. Accessibility features are basic but present. Technical debt appears low but modernization opportunities exist, especially in security and compliance implementations.
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 hotelcms.hu. 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 hotelcms.hu.

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.