Skip to main content

Security report for opravujeme.to

Technická správa komunikací hl. m. Prahy, a.s. · Transportation · Czech Republic

Medium risk. 6 critical or high findings in Security headers, GDPR outside view and 2 other checks.

Security score

72/100

Risk levelMedium

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

The website opravujeme.to is an official municipal platform operated by Technická správa komunikací hl. m. Prahy, a.s., providing centralized and up-to-date information on temporary traffic restrictions and roadworks in Prague. It serves residents and commuters by consolidating traffic disruption data in one accessible location, enhancing public awareness and planning. The site is well-branded with official logos and links to authoritative city and transportation websites, reinforcing its credibility. Technically, the website employs modern frontend technologies including Bootstrap, FontAwesome, Quill Editor, and Vue.js components for cookie consent management. Google Tag Manager is used for analytics, with a clear cookie consent mechanism in place, reflecting good privacy compliance. The site is mobile-optimized and presents a clean, navigable user interface with relevant content. From a security perspective, HTTPS is implied and cookie consent is implemented, but no explicit security headers or published security policies were detected. There is no visible incident response or vulnerability disclosure information, which could be improved. No vulnerabilities or sensitive data exposures were found in the content analyzed. Overall, the website demonstrates a solid business credibility and privacy compliance posture with room for enhancement in security policy transparency and technical security headers. The domain registration data aligns well with the business entity, supporting legitimacy and trustworthiness.

Scanned

NIS2 and GDPR posture

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

6 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 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

    • High

      Third-party services without privacy policy

      Detected services: Google Analytics, Cloudflare

      What to do: Document all third-party data sharing in your privacy policy

  3. Email security

    SPF, DKIM and DMARC stop others sending email that looks like it comes from your domain, a common route to phishing and invoice fraud.

    • High

      No DMARC record found

      DMARC provides email authentication and reporting

      What to do: Add DMARC record: "v=DMARC1; p=none; rua=mailto:dmarc@yourdomain.com"

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

Keep watching opravujeme.to

This scan found 17 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
72
Security headers
45
Email security
65
DNS health
85
Network security
100
GDPR outside view
65
Average
72

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 business operates as a public service entity under the municipal technical road management company of Prague, focusing on transportation sector information dissemination. Its market position is that of an official city-level traffic information provider, targeting local residents and commuters. The business model is service-oriented, providing free access to traffic restriction data to improve urban mobility and public safety. Partnerships with city authorities and transportation agencies are evident through linked domains and branding. The platform's growth potential lies in expanding data coverage and enhancing user engagement through improved technical features and security assurances.

Security posture

The current security maturity level is moderate. The website uses HTTPS and has implemented a cookie consent mechanism aligned with GDPR requirements. However, the absence of explicit security headers such as Content Security Policy, HSTS, and X-Frame-Options reduces the overall security posture. There is no published security policy or incident response contact, which limits transparency and preparedness. No vulnerabilities or exposed sensitive data were detected, indicating a low immediate risk. To improve, the organization should adopt comprehensive security headers, publish security policies, and establish clear incident response channels to enhance trust and compliance.

Recommendations

  1. Implement and enforce security headers including CSP, HSTS, X-Frame-Options, and X-Content-Type-Options.
  2. Publish a clear security policy and incident response contact information on the website.
  3. Introduce a vulnerability disclosure program or security.txt file to encourage responsible reporting.
  4. Enhance accessibility features to improve compliance and user experience for all visitors.
  5. Regularly audit third-party scripts and analytics tools to ensure privacy compliance and minimize tracking.

Contact details published on the site

Addresses
Legal name
Technická správa komunikací hl. m. Prahy, a.s.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Technická správa komunikací hl. m. Prahy, a.s.
Description
Provides centralized information on temporary traffic restrictions on major roads in Prague.
Key services
Traffic restriction updates, Overview of roadworks and closures
Content quality
good
Branding
consistent

Technology

Stack
Bootstrap CSS, FontAwesome, Quill Editor, Vue.js (vue-gtm-cookie-consent component), Google Tag Manager
Frameworks
Bootstrap
Performance
moderate
Mobile
good
Accessibility
basic
SEO
basic

Security

Observed score
70/100
Good practices seen
  • HTTPS usage implied by URL
  • Cookie consent mechanism implemented

Analytics and tracking

Services
Google Analytics (via GTM)
Tracking level
minimal
Privacy practices
good

Advertising

Transparency
basic

Site quality

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

Key observations

  1. Website is an official municipal service platform for Prague traffic information.
  2. Content is in Czech language with clear navigation and up-to-date information.
  3. Cookie consent is implemented with detailed descriptions in Czech.
  4. No contact emails or phone numbers explicitly shown on the main page or footer; contact page likely contains more details.
  5. No visible security policy or incident response information.
  6. No terms of service found.
  7. No exposed sensitive data or vulnerabilities detected in the HTML content.
  8. Use of modern frontend technologies and frameworks.
  9. External links point to official city and transportation authority domains.
Technical notes

Notes

The website is built on a modern frontend stack using Bootstrap for responsive design, FontAwesome for icons, and Quill Editor for rich text editing capabilities. Vue.js components are used for cookie consent management, indicating a modular and maintainable codebase. Google Tag Manager integration supports analytics and marketing efforts. Performance is moderate with no critical issues detected, and mobile optimization is good. SEO is basic with proper meta tags and Open Graph tags present. There is no detected CMS or hosting provider information. Opportunities exist to improve technical SEO, accessibility, and security configurations to reduce technical debt and enhance operational resilience.
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 opravujeme.to. 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 opravujeme.to.

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.