Skip to main content

Security report for olomouc.eu

Magistrát města Olomouce · Government · Czech Republic

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

Security score

71/100

Risk levelMedium

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

The website www.olomouc.eu serves as the official information portal for the statutory city of Olomouc in the Czech Republic. It provides residents and visitors with news, updates, and public information related to city governance and events. The site is clearly positioned as a government entity, with branding and content consistent with an official municipal portal. The target audience includes local citizens, tourists, and stakeholders interested in city affairs. Technically, the website employs a custom CMS named CMSOl, built with PHP, SQL, and VanillaJS, supplemented by older versions of jQuery and jQuery UI. It integrates modern tools such as Google Tag Manager and CookieHub for analytics and cookie consent management. The site uses FontAwesome 6 Pro for iconography and includes scripts for calendar event handling. While the technology stack is functional, the use of outdated jQuery versions suggests potential security risks and modernization opportunities. From a security perspective, the site enforces HTTPS and uses cookie consent mechanisms, indicating awareness of privacy compliance. However, no explicit privacy policy or terms of service pages were detected in the provided content, and security headers were not identified. The absence of a security.txt file or vulnerability disclosure information limits transparency in incident response. The WHOIS data for the domain is unavailable, which restricts full legitimacy verification, but the website's official nature and consistent branding mitigate concerns. Overall, the website presents a professional and trustworthy front for the city government, with good content quality and user experience. Strategic improvements in security headers, updated libraries, and explicit privacy documentation would enhance its security posture and compliance standing.

Scanned

NIS2 and GDPR posture

GDPR outside view
85/ 100 · Low
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

4 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 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 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 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 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 olomouc.eu

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
65
Security headers
30
Email security
60
DNS health
85
Network security
100
GDPR outside view
85
Average
71

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 portal operates as an essential government service platform, delivering official communications and city-related information. Its market position is that of a primary municipal information source, with no direct commercial activities. The business model is non-commercial, focusing on public service and transparency. The site targets local residents, tourists, and businesses seeking city updates. The presence of social media links to official city accounts supports community engagement. Growth indicators include regular content updates and integration of digital tools for user interaction. Partnerships appear limited to public service and technology providers, with no commercial subsidiaries or related domains identified.

Security posture

The security maturity level is moderate, with HTTPS enforced and cookie consent implemented. However, the use of outdated JavaScript libraries like jQuery 1.7.2 introduces potential vulnerabilities. The lack of visible security headers such as Content Security Policy (CSP), X-Frame-Options, and HSTS reduces defense-in-depth. No exposed sensitive data or obvious vulnerabilities were detected in the analyzed content. Compliance gaps include missing explicit privacy policy and terms of service documentation, which are critical for GDPR and NIS2 adherence. Incident response readiness is unclear due to absence of security contact information or security.txt. The security culture appears basic but can be improved with updated practices and transparency.

Recommendations

  1. Implement and enforce modern security headers including CSP, HSTS, X-Frame-Options, and X-Content-Type-Options.
  2. Upgrade JavaScript libraries, especially jQuery, to current supported versions to mitigate known vulnerabilities.
  3. Publish comprehensive privacy policy and terms of service pages clearly accessible from the homepage.
  4. Create and maintain a security.txt file to facilitate vulnerability disclosure and incident reporting.
  5. Enhance accessibility features and conduct regular security audits to maintain compliance and user trust.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Magistrát města Olomouce
Description
Oficiální informační portál statutárního města Olomouce.
Key services
city news and updates, public information, event calendar
Content quality
good
Branding
consistent

Technology

Stack
jQuery 1.7.2, jQuery UI 1.8.20, VanillaJS, PHP, SQL, FontAwesome 6 Pro, Google Tag Manager, CookieHub, ics-browser-gen, FileSaver.js
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
70/100
Good practices seen
  • HTTPS enforced (implied by https URL)
  • Use of Google Tag Manager and CookieHub for consent management

Analytics and tracking

Services
Google Analytics (via Google Tag Manager)
Tracking level
moderate
Privacy practices
basic

Advertising

Ad networks
Google Adsense
Tracking pixels
CookieHub
Marketing tools
Google Custom Search Engine
Transparency
basic

Site quality

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

Key observations

  1. Website is official city government portal for Olomouc, Czech Republic
  2. Content is in Czech language with localized metadata
  3. No privacy policy or terms of service pages explicitly found in provided content
  4. Cookie consent mechanism present via CookieHub
  5. Contact phone number provided in structured data with multilingual support
  6. No forms detected in provided HTML snippet
  7. Use of older jQuery version may pose security risks
  8. No visible security.txt or vulnerability disclosure information
  9. No WHOIS data available from EURid WHOIS raw output
  10. Social media links to Facebook and Instagram official city pages present
Technical notes

Notes

The website is built on a custom CMS (CMSOl) using PHP, SQL, and VanillaJS, with legacy jQuery and jQuery UI libraries. It integrates third-party services such as Google Tag Manager for analytics and CookieHub for cookie consent management. The site uses FontAwesome 6 Pro for icons and includes scripts for calendar event handling and file saving. Performance is moderate, with room for improvement in mobile optimization and accessibility. The technical debt is evident in outdated libraries and missing security headers. Modernization opportunities include updating the tech stack, improving SEO metadata completeness, and enhancing user experience with responsive design and accessibility compliance.
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. 71/100Medium29 findingsView report
Reviews of this site

Share your experience with olomouc.eu. 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 olomouc.eu.

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.