Skip to main content

Security report for oja.li

Stiftung OJA Liechtenstein · Government · Liechtenstein

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

Security score

68/100

Risk levelMedium

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

Stiftung OJA Liechtenstein is a non-profit foundation operating under the mandate of 10 municipalities in Liechtenstein to provide open youth work and socio-cultural animation. The organization runs multiple youth centers and specialized programs to support youth independence and social engagement. The website reflects a well-structured, professional digital presence with clear navigation and relevant content targeting local youth and community stakeholders. Technically, the site uses modern frameworks such as Vue.js and jQuery, built on the concrete5 CMS, and integrates Matomo for analytics, indicating a moderate level of digital maturity. Security posture is good with HTTPS enforced and no visible vulnerabilities, though improvements can be made by adding security headers and formal security policies. Privacy compliance is partial, with a privacy policy present but lacking a cookie consent mechanism. Overall, the site is trustworthy and aligns well with the organization's mission and regional focus.

Scanned

NIS2 and GDPR posture

GDPR outside view
53/ 100 · Medium
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

5 findings rated critical or high. Fix these first.

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

  2. GDPR outside view

    These are the privacy signals visitors and data protection authorities look for under GDPR.

    • 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

    • High

      No Cookie Consent Banner found

      GDPR requires explicit consent for non-essential cookies

      What to do: Implement a cookie consent banner that appears on first visit

  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
    • High

      Weak SSL Key Length

      SSL certificate uses 256-bit key, which is considered weak

      What to do: Use at least 2048-bit RSA or 256-bit ECC key

      • CWE-326
      • OWASP A04:2025
      • Mozilla TLS: Mozilla Server Side TLS 6.0 intermediate: rsa_key_size 2048

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

Keep watching oja.li

This scan found 23 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
52
Security headers
60
Email security
70
DNS health
75
Network security
100
GDPR outside view
53
Average
68

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 foundation holds a strong regional position as the primary provider of open youth work in Liechtenstein, supported by local government mandates. Its business model is non-profit and community-oriented, focusing on youth engagement and social services. The website supports this with clear service descriptions, multiple contact channels, and active social media links. Partnerships with related organizations such as Sovort and Streetwork Liechtenstein enhance its ecosystem. The use of a professional CMS and modern web technologies suggests a commitment to maintaining an effective digital presence. Revenue streams are likely public funding and community support, with additional services such as venue rentals. Growth indicators include active blog updates and multiple youth centers.

Security posture

The website demonstrates a solid security baseline with HTTPS and obfuscated email addresses to reduce spam. However, the absence of key security headers like Content-Security-Policy and Strict-Transport-Security represents an area for improvement. No incident response or security policy pages are published, which could hinder transparency and preparedness. The use of Matomo analytics respects privacy better than some alternatives but requires proper cookie consent to fully comply with GDPR. No vulnerabilities or exposed sensitive data were detected in the HTML content. Overall, the security posture is good but could be enhanced with formal policies and technical headers.

Recommendations

  1. Implement comprehensive security headers including Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security.
  2. Add a cookie consent banner/mechanism to comply fully with GDPR and ePrivacy regulations.
  3. Publish a security policy and incident response plan accessible on the website to improve transparency and preparedness.
  4. Consider adding a security.txt file to facilitate vulnerability disclosures.
  5. Enhance accessibility features to improve compliance and user experience for all visitors.

Contact details published on the site

Addresses
Legal name
Stiftung OJA Liechtenstein
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Stiftung OJA Liechtenstein
Description
Die Stiftung OJA Liechtenstein setzt im Auftrag von 10 Liechtensteiner Gemeinden die Offene Jugendarbeit im Sinne der Soziokulturellen Animation um. Sie unterstützt Jugendliche auf dem Weg zur Selbständigkeit und betreibt 10 Jugendtreffs und einen Mädchentreff mit verschiedenen thematischen Schwerpunkten.
Key services
Offene Jugendarbeit, Jugendtreffs, Projekte und Veranstaltungen, Vermietung von Räumlichkeiten
Content quality
good
Branding
consistent

Technology

Stack
jQuery, Vue.js, Axios, Swiper.js, Matomo Tag Manager
Frameworks
concrete5 CMS, Foundation CSS
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
80/100
Good practices seen
  • HTTPS enforced
  • No exposed sensitive data in HTML
  • Use of obfuscation for email addresses

Analytics and tracking

Services
Matomo Tag Manager
Tracking level
moderate
Privacy practices
basic

Advertising

Tracking pixels
Matomo Tag Manager
Marketing tools
CleverReach (newsletter)
Transparency
basic

Site quality

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

Key observations

  1. Website is fully accessible with no blocking or WAF challenges.
  2. Content is professionally presented in German targeting Liechtenstein youth.
  3. Uses modern JavaScript frameworks and CMS concrete5.
  4. No explicit privacy cookie consent mechanism detected.
  5. Contact information is clear and includes email, phone, and physical address.
  6. Social media presence on Facebook and Instagram.
  7. No visible security vulnerabilities or exposed sensitive data.
  8. No published security or incident response policies.
  9. WHOIS data supports legitimacy and transparency.
Technical notes

Notes

The website is built on the concrete5 CMS platform, leveraging jQuery, Vue.js, Axios, and Swiper.js for interactive features and responsive design. The use of Matomo Tag Manager indicates a preference for privacy-conscious analytics. The site is mobile-optimized with responsive layouts and good navigation clarity. Performance is moderate, with autoplay sliders and multiple images that could be optimized further. The technical stack is modern but could benefit from additional security hardening and accessibility improvements. Hosting provider details are not explicitly identified from the content. Overall, the technical infrastructure supports the business goals effectively with room for modernization and security enhancements.
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 oja.li. 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 oja.li.

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.