Skip to main content

Security report for mujdelirest.cz

Hospitality · Czech Republic

Medium risk. 11 critical or high findings in GDPR outside view, Email security and 2 other checks.

Security score

52/100

Risk levelMedium

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

The website mujdelirest.cz serves as a multilingual dining portal login page, primarily targeting users who require access to dining services, likely employees or customers within the hospitality sector in the Czech Republic. The business appears to be relatively new, with domain registration dating back to early 2022. The portal provides a straightforward login interface with support for multiple languages, indicating an intent to serve a diverse user base. However, the site lacks visible business contact information, privacy policies, and terms of service on the login page, which limits transparency and user trust. Technically, the website employs common and reliable web technologies including jQuery, Bootstrap, Chart.js, and TinyMCE, suggesting a moderate level of digital maturity. The site is mobile-optimized and includes a cookie consent banner compliant with basic GDPR requirements, though no detailed privacy or security policies are presented. Performance appears moderate with no evident blocking or WAF interference. From a security perspective, the site uses secure form submission methods and password input types but lacks explicit security headers such as Content-Security-Policy or HSTS, which are recommended for enhanced protection. The absence of privacy and security policies, as well as contact information for incident response, indicates gaps in compliance and user assurance. The WHOIS data is transparent and consistent with the website's regional focus, supporting legitimacy. Overall, the website is functional and moderately secure but would benefit from improved transparency, enhanced security headers, and published privacy and security policies to strengthen user 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

11 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

  2. Email security

    SPF, DKIM and DMARC stop others sending email that looks like it comes from your domain, a common route to phishing and invoice fraud.

    • Critical

      No email authentication configured

      Domain is vulnerable to email spoofing

      What to do: Implement SPF, DKIM, and DMARC immediately

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

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

Keep watching mujdelirest.cz

This scan found 28 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. 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
15
Email security
40
DNS health
75
Network security
100
GDPR outside view
10
Average
52

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

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 mujdelirest.cz, from OffSeq Breach.

Total records
52
Employees
0
Customers
52
Third parties
0
Weak passwords
21%

1 subdomain affected

See the 10 newest leaked credentials

A one-off add-on to this report that lists the most recent identifier and password pairs OffSeq Breach holds for mujdelirest.cz.

Select it in the checkout above.

Breach keeps ingesting new leaks, so these numbers can grow between scans.

Open in Breach(opens in a new tab)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 business operates within the hospitality sector, providing a digital portal for dining services. Its market positioning appears to be niche, serving a defined user group requiring login access, possibly employees or clients of a food service provider. The business model likely revolves around providing access to dining-related services or benefits. The lack of detailed company information and external partnerships on the login page limits insight into revenue streams or growth indicators. The multilingual support suggests an intent to serve a broader regional audience. No evident partnerships or subsidiaries are disclosed on the page.

Security posture

The current security posture is moderate but incomplete. The use of HTTPS is assumed but not explicitly confirmed in the HTML content. The login form uses secure POST methods and password masking, which are basic security practices. However, the absence of security headers such as Content-Security-Policy, X-Frame-Options, and HSTS reduces protection against common web attacks. No incident response contacts or vulnerability disclosure policies are present, limiting readiness for security incidents. Cookie consent is implemented but limited to essential cookies, with no detailed privacy policy. Overall, the site should enhance security controls and transparency to meet higher compliance standards.

Recommendations

  1. Implement and enforce HTTPS with strong SSL/TLS configuration and verify it site-wide.
  2. Add essential security headers including Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options.
  3. Publish comprehensive privacy and cookie policies accessible from all pages.
  4. Provide clear contact information including security incident response channels.
  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
Dining Portal providing login access to users, likely related to food service or hospitality sector.
Key services
User login portal for dining services
Content quality
basic
Branding
moderate

Technology

Stack
jQuery 3.5.1, jQuery UI, Chart.js, TinyMCE, Bootstrap
Performance
moderate
Mobile
good
Accessibility
basic
SEO
basic

Security

Observed score
55/100
Good practices seen
  • Login form uses POST method
  • Password input field type is password
  • Cookie consent banner present

Analytics and tracking

Tracking level
minimal
Privacy practices
poor

Advertising

Transparency
poor

Site quality

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

Key observations

  1. Website is a multilingual dining portal login page.
  2. No privacy policy or terms of service found on the login page.
  3. Cookie consent banner is present and informs about essential cookies only.
  4. No contact information or company details are provided on this page.
  5. No social media or external business contact links found.
  6. Uses common web technologies and libraries for UI and charts.
  7. No explicit security headers or advanced security policies detected in HTML.
  8. WHOIS data is transparent and consistent with the website's regional focus.
Technical notes

Notes

The website uses a standard technology stack with jQuery, Bootstrap, Chart.js, and TinyMCE, indicating a conventional web application architecture. The site is mobile-optimized and includes responsive design elements. Performance is moderate with no evident blocking or errors. However, the absence of CMS identification and hosting provider details limits deeper infrastructure insights. The site lacks advanced SEO metadata and accessibility features beyond basic viewport settings. There is opportunity to modernize with enhanced SEO, accessibility, and security features to improve overall technical robustness.
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 mujdelirest.cz. 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 mujdelirest.cz.

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.