Skip to main content

Security report for orot.pl

Opolska Regionalna Organizacja Turystyczna · Government · Poland

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

Security score

60/100

Risk levelMedium

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

Opolska Regionalna Organizacja Turystyczna (OROT) is a well-established regional tourism organization based in Opole, Poland, founded in 2004. The organization focuses on promoting tourism within the Opole Voivodeship through event organization, publishing, certification of tourist products, and fostering partnerships with local and national tourism entities. The website serves as a central hub for information, news, and resources related to regional tourism. Technically, the website employs a modern tech stack including jQuery, Bootstrap, and Google Analytics, and is built on the SkyCMS platform. It is mobile-optimized and provides a good user experience with clear navigation and relevant content. Security-wise, the site uses HTTPS with DNSSEC enabled and includes CSRF tokens and cookie consent mechanisms, though it lacks some advanced security headers and a vulnerability disclosure policy. Overall, the domain registration data is consistent and trustworthy, supporting the legitimacy of the organization. The website is safe for general audiences and does not contain any adult or questionable content.

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

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 orot.pl

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
67
Security headers
20
Email security
70
DNS health
90
Network security
100
GDPR outside view
10
Average
60

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

OROT holds a key position as the official regional tourism organization for Opole Voivodeship, operating as a non-profit entity within the government and non-profit sectors. Its business model revolves around tourism promotion, event management, and certification services, targeting tourists, local businesses, and cultural organizations. The organization maintains partnerships with national tourism bodies and regional stakeholders, enhancing its market presence. The website reflects a professional and consistent brand image, supporting its credibility and trustworthiness. Growth indicators include active news updates, event participation, and cross-border cooperation projects. The partnership ecosystem includes national tourism portals and regional cultural institutions, reinforcing its strategic role in regional tourism development.

Security posture

The website demonstrates a moderate to good security posture with HTTPS enforced and DNSSEC enabled, which protects domain integrity. The presence of CSRF tokens and cookie consent modals indicates attention to security and privacy. However, the absence of advanced HTTP security headers such as Content-Security-Policy and X-Frame-Options suggests room for improvement. No vulnerability disclosure or incident response contacts are provided, which could hinder timely security issue reporting. The use of third-party scripts like Google Analytics and Facebook SDK introduces some tracking but is common practice. Overall, the security posture is adequate for the organization's scope but could be enhanced with additional controls and transparency.

Recommendations

  1. Implement a security.txt file to provide clear vulnerability disclosure and incident response contacts.
  2. Add advanced HTTP security headers such as Content-Security-Policy, X-Frame-Options, and X-XSS-Protection to strengthen browser security.
  3. Regularly review and update third-party libraries and scripts to mitigate vulnerabilities.
  4. Enhance privacy compliance by detailing data retention policies and user rights more explicitly.
  5. Consider publishing terms of service to clarify user and organizational responsibilities.

Contact details published on the site

Addresses
Legal name
Opolska Regionalna Organizacja Turystyczna
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Opolska Regionalna Organizacja Turystyczna
Description
Opolska Regionalna Organizacja Turystyczna is a regional tourism organization based in Opole, Poland, focused on promoting tourism, organizing events, publishing tourist materials, and supporting local tourism initiatives.
Key services
Tourism promotion, Event organization, Publishing tourist guides and materials, Certification of tourist products, Supporting local tourism initiatives and partnerships
Content quality
good
Branding
consistent

Technology

Stack
jQuery, Bootstrap, Google Analytics, Facebook SDK, Owl Carousel, Blueimp Gallery
Frameworks
Bootstrap
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
75/100
Good practices seen
  • HTTPS enforced
  • CSRF token present in meta tag
  • Cookie consent modal implemented

Analytics and tracking

Services
Google Analytics
Tracking level
moderate
Privacy practices
basic

Advertising

Tracking pixels
Facebook Pixel (via Facebook SDK)
Marketing tools
Facebook SDK
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 challenge.
  2. Content is professionally presented and relevant to regional tourism.
  3. Privacy and cookie policies are implemented with consent mechanisms.
  4. No terms of service or explicit security policies found.
  5. WHOIS data supports legitimacy and long-term operation.
  6. Use of common web technologies and analytics tools.
  7. No critical security issues detected but some security headers could be improved.
Technical notes

Notes

The website is built on the SkyCMS content management system and uses a combination of jQuery, Bootstrap, Owl Carousel, and Blueimp Gallery for UI and interactivity. Google Analytics and Facebook SDK are integrated for analytics and social media engagement. The site is mobile-optimized and includes accessibility features such as ARIA attributes and language selection via Google Translate. Performance is moderate, with minified CSS and JS assets loaded asynchronously. The site uses DNSSEC for domain security and HTTPS for encrypted communication. There is no explicit hosting provider identified from the data. Technical debt appears low, but the lack of some modern security headers and vulnerability disclosure mechanisms indicates areas for modernization and risk reduction.
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 orot.pl. 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 orot.pl.

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.