Skip to main content

Security report for hotelscombined.com

Other · N/a

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

Security score

70/100

Risk levelMedium

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

The website www.hotelscombined.com is currently inaccessible beyond a CAPTCHA verification page, indicating the presence of a web application firewall or bot mitigation system. This prevents direct access to business content, limiting the ability to analyze the company's services, policies, or contact information. The domain WHOIS query returned no registration data, suggesting the domain may be unregistered, privacy protected, or otherwise obscured, which raises concerns about legitimacy and transparency. Technically, the site uses Google reCAPTCHA Enterprise to prevent automated access, but lacks visible security headers or HTTPS confirmation in the provided data. Overall, the site exhibits minimal content and poor user experience due to access restrictions.

Scanned

NIS2 and GDPR posture

GDPR outside view
50/ 100 · Medium
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

7 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. GDPR outside view

    These are the privacy signals visitors and data protection authorities look for under GDPR.

    • 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

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

Keep watching hotelscombined.com

This scan found 19 issues across 5 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
72
Security headers
20
Email security
100
DNS health
80
Network security
100
GDPR outside view
50
Average
70

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

Due to the CAPTCHA challenge and lack of accessible content, no concrete business intelligence can be derived. The domain name suggests affiliation with a hotel price comparison or travel meta-search service, but no direct evidence or business details are available. No contact information, privacy policies, or terms of service are present to validate business operations or compliance. The absence of WHOIS data further limits trust and raises questions about domain ownership and operational legitimacy.

Security posture

The security posture shows some strengths in bot mitigation via Google reCAPTCHA Enterprise, which helps prevent automated abuse. However, the lack of visible HTTPS confirmation, security headers, and privacy compliance documentation are notable weaknesses. The CAPTCHA challenge itself acts as a barrier to access, which while improving security against bots, also reduces transparency and user trust. No incident response or vulnerability disclosure information is available, indicating immature security governance or limited public security communication.

Recommendations

  1. Ensure the domain WHOIS information is properly registered and publicly available to improve trust and legitimacy.
  2. Publish clear privacy, cookie, and terms of service policies accessible without CAPTCHA barriers.
  3. Implement and verify HTTPS with strong TLS configuration and add essential security headers.
  4. Provide accessible contact information and business details to enhance credibility and compliance.
  5. Consider balancing bot mitigation with user experience to avoid blocking legitimate users and enabling better analysis.
Site observations

Automated reading of the public site. Ratings are indicative.

Generic detected. Page is a CAPTCHA challenge page requiring user verification before access, indicating WAF or bot mitigation in place. These observations may be incomplete. For a fuller analysis, contact guard@offseq.com.

Business

Content quality
poor
Branding
moderate

Technology

Stack
Google reCAPTCHA Enterprise, Fetch API, JavaScript, HTML5, CSS3
SEO
poor

Security

Observed score
30/100
Good practices seen
  • Use of Google reCAPTCHA Enterprise for bot mitigation

Analytics and tracking

Tracking level
minimal
Privacy practices
poor

Advertising

Transparency
poor

Site quality

Design
basic
User experience
poor
Content relevance
poor
Navigation
poor
Professionalism
poor
Trustworthiness
low

Key observations

  1. Website content is blocked behind a CAPTCHA challenge page.
  2. No business or contact information is available on the page.
  3. No privacy, cookie, or terms of service policies are present.
  4. No WHOIS data available for domain, indicating possible non-registration or privacy protection.
  5. Use of Google reCAPTCHA Enterprise indicates bot mitigation measures.
  6. No visible security headers or HTTPS information provided.
  7. Page is minimal and does not provide actual business content.
Technical notes

Notes

The website relies on Google reCAPTCHA Enterprise for bot mitigation, indicating a modern approach to security challenges. The HTML content is minimal and focused solely on CAPTCHA verification, with no visible CMS or backend technology disclosed. External resources are loaded from Google domains and an Amazon S3 bucket hosting logos and background images. No SEO or accessibility features are evident due to the blocked content. Performance and mobile optimization cannot be assessed given the limited page content. The lack of security headers and HTTPS confirmation in the provided data suggests technical improvements are needed to meet modern web security standards.
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. 71/100Medium24 findingsView report
Reviews of this site

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