Skip to main content

Security report for josefstadt.org

Theater in der Josefstadt Betriebsges.m.b.H. · Hospitality · Austria

High risk. 6 critical or high findings in GDPR outside view, SSL/TLS and 1 other check.

Security score

47/100

Risk levelHigh

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

Theater in der Josefstadt Betriebsges.m.b.H. operates a well-established cultural institution in Austria, providing theatrical performances, ticketing services, subscriptions, and related cultural events. The website serves as a comprehensive portal for current programming, ticket sales, and audience engagement, targeting theatergoers and cultural enthusiasts primarily in Austria. The business enjoys a mature domain with consistent registration details aligning with its public identity. Technically, the website is built on TYPO3 CMS with modern frontend components such as Owl Carousel and YouTube video integration. However, performance metrics are lacking, and the site shows signs of slow loading. Mobile optimization and SEO are adequately addressed, but accessibility is basic. Security posture is weak due to the absence of a valid SSL certificate and lack of HTTPS enforcement, exposing users to potential risks. While some security headers are present, critical TLS protocols and best practices are missing. Privacy compliance is partially met with a privacy policy and terms of service, but no cookie consent mechanism is implemented. Contact information is clearly provided, enhancing business credibility. Overall, the site is functional and professional but requires urgent security improvements to protect user data and trust. Strategic enhancements in SSL/TLS deployment, cookie consent, and performance optimization will significantly improve the site's security and user experience.

Scanned

NIS2 and GDPR posture

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

6 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

      No HTTPS encryption

      GDPR requires appropriate security measures for personal data

      What to do: Implement SSL/TLS certificate for HTTPS

    • High

      No Cookie Policy found

      GDPR requires clear information about cookie usage

      What to do: Add a dedicated cookie policy explaining cookie usage and purposes

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

    • Critical

      No HTTPS Encryption

      Website does not use HTTPS encryption, making all data transmission vulnerable to interception

      What to do: Implement SSL/TLS certificate and redirect all HTTP traffic to HTTPS

  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 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 josefstadt.org

This scan found 18 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
0
Security headers
35
Email security
50
DNS health
80
Network security
100
GDPR outside view
18
Average
47

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 theater holds a strong market position as a cultural landmark with a long history and a loyal audience base. Its business model revolves around live performances, ticket sales through multiple channels (online, app, phone), and supplementary offerings such as publications and merchandise. The target audience includes local residents, cultural tourists, and younger demographics via the U30 program. The organization leverages social media for outreach but does not appear to use extensive analytics or advertising networks, indicating a focus on organic engagement. The domain's longevity and registrant consistency reinforce its legitimacy and market stability.

Security posture

The current security maturity is low due to the lack of a valid SSL certificate and disabled HTTPS protocols, which is a critical vulnerability for any modern website. The absence of DNSSEC and CAA records further weakens domain security. While no active vulnerabilities like Heartbleed or POODLE are detected, the missing encryption exposes users to interception risks. No incident response or security policy information is publicly available, indicating limited transparency in security governance. Compliance with GDPR is partially demonstrated through privacy policies but lacks cookie consent mechanisms. The site should prioritize SSL/TLS implementation and enhance security headers to improve its security posture.

Recommendations

  1. Obtain and deploy a valid SSL/TLS certificate to enable HTTPS across the entire site.
  2. Implement a cookie consent banner/mechanism to comply with GDPR and enhance user privacy.
  3. Enable modern TLS protocols (TLS 1.2 or 1.3) and disable legacy insecure protocols.
  4. Add DNSSEC and CAA records to strengthen domain name system security.
  5. Publish a clear security policy and incident response contact information to improve transparency and trust.
Technical notes

Notes

The website uses TYPO3 CMS, a robust and widely used content management system, indicating a stable technical foundation. Frontend technologies include Owl Carousel for sliders and embedded YouTube videos for multimedia content. The site loads CSS and JS assets from both internal and external sources, including a font service via Fastly CDN. However, performance data is missing, and inferred load times suggest slow performance. Mobile responsiveness is good, but accessibility features are basic. The hosting environment appears to be managed by Kapper.net based on nameservers. The lack of SSL/TLS and modern security configurations represents a significant technical risk that should be addressed promptly.
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

Earlier scans of this domain

  1. 48/100High25 findingsView report
Reviews of this site

Share your experience with josefstadt.org. 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 josefstadt.org.

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.