Janáčkova filharmonie Ostrava · Media · Czech Republic
Medium risk. 5 critical or high findings in GDPR outside view, SSL/TLS and 1 other check.
Janáčkova filharmonie Ostrava is a well-established symphony orchestra based in Ostrava, Czech Republic, providing a rich program of classical music concerts, educational activities, and cultural events. The organization targets classical music enthusiasts and the cultural community, operating primarily as a non-profit entity. The website reflects a professional and consistent brand image with comprehensive event listings and ticketing integration. Technically, the website is built on WordPress using common plugins such as Contact Form 7, Cookie Law Info, and Google Analytics. It employs modern JavaScript libraries like jQuery and jCarousel for interactive elements and uses Google reCAPTCHA v3 to protect forms. The site is mobile-optimized and SEO-friendly, though performance is moderate. From a security perspective, the site uses HTTPS and has implemented cookie consent mechanisms aligned with GDPR. However, it lacks visible security headers and published security policies or incident response contacts. No vulnerabilities or exposed sensitive data were detected in the content. The absence of WHOIS data reduces trust assessment confidence but does not detract from the professional presentation. Overall, the website presents a low-risk profile with good privacy compliance and a strong cultural mission. Strategic improvements in security headers, incident response transparency, and WHOIS data availability would enhance trust and security posture.
Scanned
NIS2 Art. 21(2)
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.
5 findings rated critical or high. Fix these first.
These are the privacy signals visitors and data protection authorities look for under GDPR.
EU businesses are subject to strict GDPR requirements
What to do: Implement comprehensive GDPR compliance including privacy policy, cookie consent, and data protection measures
GDPR requires a clear and accessible privacy policy
What to do: Add a comprehensive privacy policy page and link to it prominently
Detected services: Google Analytics, Facebook, Twitter, YouTube
What to do: Document all third-party data sharing in your privacy policy
TLS encrypts the connection and proves the site is really yours. Weak or expiring certificates trigger browser warnings and put traffic at risk.
Server supports weak protocols: TLSv1.1
What to do: Disable TLS 1.0, TLS 1.1, and all SSL versions
Services reachable from the internet are the first thing attackers probe. Anything open that does not need to be should be closed.
Port 21 (FTP) is publicly accessible - FTP - Often unencrypted file transfer
What to do: Consider restricting access to FTP or implementing strong authentication
Need hands-on remediation? Email guard@offseq.com
This scan found 22 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.
€25per month
Email alerts on material changes and an exportable JSON history of every change.
Billed monthly to your card. Cancel anytime. See sample alerts.
€39.90one-time
Prices incl. 21% VAT. Secure checkout by Mollie; sold by SEQ SIA, Latvia.
Each check with its score, findings and the evidence it collected.
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
Not counted
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.
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
Leaked credentials and lookalike domains from OffSeq Breach. The counts are free; the detailed lists are paid add-ons.
Leaked records that mention jfo.cz, from OffSeq Breach.
3 subdomains 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 jfo.cz.
Select it in the checkout above.
Breach keeps ingesting new leaks, so these numbers can grow between scans.
Business context, site observations and technical notes gathered during the scan, and the standards behind each reference.
Automated reading of the public site. Ratings are indicative.
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
Rate this report, add an optional comment, and tell us if you want a security specialist to follow up.
Reviews of this site
Share your experience with jfo.cz. Every review is verified by email and published after moderation.
Community rating
No published reviews yet. Be the first to review jfo.cz.