Skip to main content

Security report for interticket.sk

Komáromi Jókai Színház · Hospitality · Slovakia

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

Security score

46/100

Risk levelHigh

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

Komáromi Jókai Színház operates an online ticketing platform focused on theatrical performances and cultural events in Komárno, Slovakia. The website provides event listings, ticket purchasing options, and voucher issuance primarily targeting local Hungarian and Slovak-speaking audiences. The business model centers on direct online sales with integrated payment processing via Barion. Technically, the site uses a custom CMS with jQuery, Foundation framework, and several third-party scripts for UI and payment integration. However, the site suffers from a lack of HTTPS, resulting in a critical security vulnerability. The absence of privacy and terms of service pages indicates compliance gaps. Performance is suboptimal with slow load times and a large page size. Security posture is weak due to missing SSL, no security headers, and no email authentication records. Contact information is available but no company emails are published. Overall, the site is functional but requires urgent security and compliance improvements.

Scanned

NIS2 and GDPR posture

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

9 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

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

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

Keep watching interticket.sk

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
50
Security headers
20
Email security
50
DNS health
55
Network security
100
GDPR outside view
0
Average
46

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

The company holds a mature domain with consistent WHOIS data, indicating a stable regional presence since 2004. It targets a niche market of theater and event attendees in Komárno, leveraging online sales to streamline ticket distribution. The partnership with Barion for payments suggests a focus on secure and convenient transactions, although the lack of HTTPS undermines this. The site’s multilingual support and social media presence on Facebook enhance its reach. However, the absence of privacy policies and terms of service may expose the business to regulatory risks. The slow website performance could impact user experience and conversion rates. Strategic partnerships appear limited to payment processing, with no evident subsidiaries or parent companies.

Security posture

The website’s security posture is poor. The lack of a valid SSL certificate and disabled TLS protocols expose users to data interception and man-in-the-middle attacks. No HTTP security headers are implemented, increasing risks of clickjacking, MIME sniffing, and XSS attacks. Email security is weak with no DMARC record, potentially allowing spoofing. The site uses third-party scripts including Google reCAPTCHA and Barion pixel, which introduce tracking but no evident vulnerabilities. The absence of incident response contacts or security policies further weakens the security maturity. Immediate remediation is required to enable HTTPS, configure security headers, and implement email authentication standards to protect users and maintain trust.

Recommendations

  1. Obtain and install a valid SSL/TLS certificate to enable HTTPS across the entire site.
  2. Implement HTTP security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options.
  3. Publish comprehensive privacy policy and terms of service pages to ensure regulatory compliance.
  4. Configure DMARC, SPF, and DKIM records for email domain to prevent spoofing and phishing.
  5. Optimize website performance by reducing page size and improving load times.
  6. Add visible company contact emails and incident response contacts for security reporting.
  7. Enhance mobile optimization and accessibility features to improve user experience.
  8. Regularly audit third-party scripts and tracking pixels for security and privacy impact.
  9. Establish a formal security policy and incident response plan accessible to users.
  10. Monitor domain expiry closely and renew timely to avoid service disruption.

Contact details published on the site

Addresses
Technical notes

Notes

The website is built on a custom CMS platform using jQuery 2.2.4, jQuery UI, and the Foundation CSS framework. It integrates third-party services such as Barion for payment processing and Google reCAPTCHA for bot protection. The DNS setup uses DNS Made Easy nameservers and Google MX records for email. However, the SSL certificate is invalid or missing, and no TLS protocols are enabled, resulting in HTTP-only access. The site has a large page size (~391 KB) and slow load time (~13 seconds), indicating potential optimization needs. The site is multilingual with Hungarian and Slovak language options. No modern frontend frameworks or CMS platforms like WordPress or Drupal are detected. The hosting provider is not explicitly identified beyond IP and DNS info. Overall, the technical infrastructure is functional but outdated and insecure, requiring modernization and security hardening.
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 interticket.sk. 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 interticket.sk.

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.