Skip to main content

Security report for morgens.hu

MORGENS · 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

MORGENS is a Hungarian company specializing in integrated hotel guest acquisition solutions, offering a comprehensive suite of services including booking engines, loyalty programs, digital marketing, revenue management, and hotel content management systems. The company holds a strong market position with over 150 partners and notable certifications such as Google Premier Partner and a product innovation award. Their website reflects a mature digital infrastructure utilizing modern technologies like Google Analytics, Tag Manager, Recaptcha, and advanced animation libraries, providing a professional and engaging user experience. Security measures include HTTPS enforcement and bot protection, complemented by a detailed cookie consent mechanism ensuring GDPR compliance. However, there is room for improvement in security headers and incident response transparency. Overall, MORGENS demonstrates a solid security posture and business credibility, making it a trustworthy entity in the hospitality technology sector.

Scanned

NIS2 and GDPR posture

GDPR outside view
83/ 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 morgens.hu

This scan found 24 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
20
Email security
70
DNS health
85
Network security
0
GDPR outside view
83
Average
55
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

Technical appendix

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

Business context

Business profile

MORGENS operates primarily in the hospitality and technology sectors, targeting hotels and tourism service providers in Hungary. Their business model focuses on B2B SaaS and service offerings that enhance direct booking conversions and guest loyalty. The company leverages strategic partnerships and certifications to maintain competitive advantages. Their revenue streams likely include software licensing, marketing services, and consulting. The presence of a comprehensive partner ecosystem and a strong digital marketing approach indicates a growth-oriented strategy. The company emphasizes long-term partnerships and data-driven marketing, positioning itself as a key player in the Hungarian hospitality technology market.

Security posture

The website employs HTTPS with no visible SSL issues and integrates Google Recaptcha to mitigate spam and bot attacks. Cookie consent is managed via CookieYes, providing granular user control and GDPR compliance. No critical vulnerabilities or exposed sensitive data were detected in the HTML content. However, the absence of explicit security headers such as Content-Security-Policy and X-Frame-Options suggests potential areas for enhancement. There is no published security policy or incident response contact, which could improve transparency and readiness. Overall, the security posture is solid but could benefit from additional hardening and formalized disclosure mechanisms.

Recommendations

  1. Implement HTTP security headers including Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options to enhance protection against common web attacks.
  2. Publish a dedicated security policy page and provide clear incident response contact information to improve transparency and trust.
  3. Introduce a security.txt file to facilitate responsible vulnerability disclosure.
  4. Regularly audit and update third-party scripts and libraries to mitigate risks from vulnerabilities.
  5. Enhance monitoring and alerting mechanisms to detect and respond to potential security incidents promptly.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
MORGENS
Description
Integrált megoldások a hatékony és jövedelmező szállodai vendégszerzés szolgálatában. Teljes körű szolgáltatást nyújtanak szállodai vendégszerzéshez, foglalási rendszerekhez, digitális marketinghez, revenue managementhez és webfejlesztéshez.
Key services
RoomSome Booking Engine, RoomSome Loyalty, RoomSome Voucher, Zadír Hotel CMS, Zadír Ticket, Digital Marketing, Yield & Revenue Management
Content quality
excellent
Branding
consistent

Technology

Stack
Google Analytics, Google Tag Manager, Google Recaptcha, CookieYes Consent Management, Optimonk, GSAP, Lottie animations, DotLottie player
Performance
moderate
Mobile
good
Accessibility
good
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • Google Recaptcha for bot protection
  • Cookie consent banner with granular controls
  • No exposed sensitive data in HTML

Analytics and tracking

Services
Google Analytics, Google Tag Manager
Tracking level
moderate
Privacy practices
good

Advertising

Ad networks
Google Ads, Facebook Ads
Tracking pixels
Facebook Pixel
Marketing tools
Optimonk, Facebook Pixel
Transparency
good

Site quality

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

Key observations

  1. Website is fully accessible with no blocking or WAF challenges.
  2. Comprehensive cookie consent mechanism implemented with detailed categories.
  3. No explicit terms of service found on the site.
  4. Contact information is primarily via contact forms and social media; no direct emails or phone numbers explicitly found in the HTML.
  5. Strong branding and consistent professional design.
  6. Use of modern web technologies and animation libraries enhances user experience.
  7. Security best practices are partially implemented; room for improvement in HTTP security headers.
  8. No visible vulnerabilities or exposed sensitive data.
  9. Privacy and cookie policies are well presented and GDPR compliant.
  10. Business is focused on hospitality technology solutions in Hungary.
Technical notes

Notes

The website uses a modern tech stack including Google Analytics, Tag Manager, Recaptcha, CookieYes for consent management, Optimonk for marketing pop-ups, and advanced animation libraries like GSAP and Lottie. The CMS appears proprietary (Zadír Hotel CMS) tailored for hospitality clients. Hosting is likely provided by zcms.hu, inferred from resource URLs. Performance is moderate with good mobile optimization and accessibility features. SEO is well addressed with proper meta tags and Open Graph images. The site is well-structured with clear navigation and professional design, supporting a positive user experience. Opportunities exist to improve security headers and formalize security policies to reduce technical risks.
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 morgens.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 morgens.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.