Skip to main content

Security report for queenscourt.hu

Queen’s Court Hotel & Residence · Hospitality · Hungary

High risk. 6 critical or high findings in Network security, Security headers and 1 other check.

Security score

49/100

Risk levelHigh

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

Queen’s Court Hotel & Residence is a luxury five-star wellness apartment hotel located in Budapest, Hungary. The website presents a professional and well-structured digital presence, highlighting the hotel’s tailored luxury offerings, customer ratings, and awards from reputable platforms such as Hotels.com and Tripadvisor. The business targets discerning travelers seeking high-end accommodation and wellness services. Technically, the site is built on WordPress using Elementor, with modern libraries like GSAP and jQuery, and includes cookie consent mechanisms compliant with GDPR principles. Security posture is adequate with HTTPS enabled and no exposed sensitive data, though security headers and formal policies are absent. Overall, the website reflects a credible and mature hospitality business with room for improvement in privacy and security transparency.

Scanned

NIS2 and GDPR posture

GDPR outside view
88/ 100 · Low
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

6 findings rated critical or high. Fix these first.

  1. Network security

    Services reachable from the internet are the first thing attackers probe. Anything open that does not need to be should be closed.

    • Critical

      Critical Service Exposed: MySQL

      Port 3306 (MySQL) is publicly accessible - MySQL - Database server

      What to do: Immediately restrict access to MySQL using firewall or VPN

      • NIS2 21(2)(e)
      • IR 2024/2690 6.7.2(f): Implementing Regulation (EU) 2024/2690, Annex point 6.7.2(f): Network security
      • NIST CM-7: NIST SP 800-53 Rev. 5 CM-7: Least Functionality
      • NIST SC-7: NIST SP 800-53 Rev. 5 SC-7: Boundary Protection

  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';…

  3. 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.

    • High

      Weak Protocols Supported

      Server supports weak protocols: TLSv1.1

      What to do: Disable TLS 1.0, TLS 1.1, and all SSL versions

      • CWE-327
      • OWASP A04:2025
      • ASVS V12.1.1

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

Keep watching queenscourt.hu

This scan found 23 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
72
Security headers
15
Email security
85
DNS health
80
Network security
0
GDPR outside view
88
Average
57
After the cap
49

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 · found on this site
  • 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

Breach exposure

Leaked credentials and lookalike domains from OffSeq Breach. The counts are free; the detailed lists are paid add-ons.

Dark web exposure

Add-on

Leaked records that mention queenscourt.hu, from OffSeq Breach.

No leaked records found

Breach holds no records for queenscourt.hu right now. New leaks arrive continuously, so monitoring on Breach alerts you if that changes.

Monitor on Breach (opens in a new tab)

Technical appendix

Business context, site observations and technical notes gathered during the scan, and the standards behind each reference.

Business context

Business profile

The hotel operates in the hospitality sector with a focus on luxury and wellness. It leverages direct online booking and maintains presence on major booking platforms, indicating a hybrid business model combining direct sales and third-party distribution. The domain age (since 2012) supports a stable market presence. Customer reviews and awards serve as strong trust signals. The website’s multilingual support (English and Hungarian) suggests targeting both local and international clientele. No parent or subsidiary companies are identified. The business appears small but well-positioned in the luxury segment with growth potential.

Security posture

The website demonstrates a basic to moderate security maturity level. HTTPS is properly configured, and cookie consent is implemented with granular user controls, supporting GDPR compliance. However, the absence of security headers such as Content-Security-Policy, X-Frame-Options, and others is a gap. No incident response or vulnerability disclosure information is published, which limits transparency and readiness perception. No known vulnerabilities or exposed sensitive data were detected in the HTML content. The site would benefit from formalizing security policies and improving header configurations to enhance protection against common web threats.

Recommendations

  1. Publish a comprehensive privacy policy and terms of service pages to improve compliance and user trust.
  2. Implement and display a security policy and incident response contact information to enhance transparency.
  3. Add security headers (CSP, X-Content-Type-Options, X-Frame-Options) to strengthen defense against attacks.
  4. Enhance accessibility features to improve usability for all users.
  5. Regularly audit and update third-party libraries and plugins to mitigate vulnerabilities.

Contact details published on the site

Registration number
SZ19000558
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Queen’s Court Hotel & Residence
Description
A luxurious five-star wellness apartment hotel located in Budapest, offering tailored luxury and classic eclectic heritage. The site promotes booking services and highlights awards and customer ratings.
Key services
Luxury accommodation, Wellness services, Online booking
Content quality
good
Branding
consistent

Technology

Stack
WordPress, Elementor, jQuery, GSAP, CookieYes (cookie consent), WP TripAdvisor Review Slider, TranslatePress
Frameworks
Elementor
Platforms
WordPress
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
80/100
Good practices seen
  • HTTPS enabled
  • Cookie consent banner with detailed preferences
  • No exposed sensitive data in HTML

Analytics and tracking

Services
Google Analytics
Tracking level
moderate
Privacy practices
basic

Advertising

Marketing tools
CookieYes, WP TripAdvisor Review Slider
Transparency
basic

Site quality

Design
good
User experience
good
Content relevance
good
Navigation
good
Professionalism
good
Trustworthiness
high

Key observations

  1. Website uses WordPress with Elementor builder and several plugins.
  2. Cookie consent is implemented with detailed categories and user controls.
  3. No explicit privacy policy or terms of service pages found in the provided content.
  4. No contact emails or phone numbers explicitly found in the HTML content provided.
  5. Website shows good customer ratings and awards, enhancing trust.
  6. No security headers detected in the provided data; potential improvement area.
  7. No incident response or vulnerability disclosure information found.
  8. No data protection officer contact information found.
  9. Website content is professional and targeted at luxury hospitality customers.
  10. No adult or questionable content detected.
Technical notes

Notes

The website uses a modern WordPress CMS with Elementor page builder, supported by jQuery and GSAP for animations. CookieYes manages cookie consent, and WP TripAdvisor Review Slider integrates customer reviews. Fonts are loaded from Google Fonts. The site is hosted under a domain registered with PDR Ltd. and uses DNS servers from rackforest.com. Performance is moderate with some optimization opportunities. Mobile responsiveness is good, but accessibility is basic. SEO is supported by proper meta tags and structured data. No critical technical debt or outdated technologies were detected, but security header implementation is lacking.
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 queenscourt.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 queenscourt.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.