Skip to main content

Security report for uzavirky-city.cz

Transportation · Czech Republic

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

Security score

59/100

Risk levelMedium

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

The website www.uzavirky-city.cz serves as a local informational platform focused on providing real-time and planned road closure and traffic incident data for the city of Benešov, Czech Republic. It targets residents and visitors who need up-to-date traffic information to navigate the city effectively. The site leverages Google Maps API to deliver an interactive map experience, enhancing usability and engagement. The business model appears to be a public or municipal service, offering essential transportation-related updates without commercial intent. From a technical perspective, the site is built on WordPress with custom theming and uses modern web technologies including JavaScript and CSS. The integration of Google Maps API is a key feature, though no advanced frameworks or analytics tools are detected. The site performs moderately well with good mobile optimization and basic accessibility features, but lacks comprehensive SEO and privacy compliance elements. Security posture is adequate with HTTPS enabled, but the absence of security headers and privacy policies indicates room for improvement. No critical vulnerabilities or exposed sensitive data were found, but the lack of WHOIS data and registrant information reduces domain trustworthiness. The site does not display contact information or incident response details, which could impact user trust and compliance with data protection regulations. Overall, the website is a functional and useful local service with a safe content profile. However, it would benefit from enhanced privacy compliance, improved security headers, and clearer business and contact information to strengthen trust and regulatory adherence.

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

10 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 uzavirky-city.cz

This scan found 22 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
77
Security headers
15
Email security
65
DNS health
85
Network security
100
GDPR outside view
10
Average
59

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

Breach exposure

Leaked credentials and lookalike domains from OffSeq Breach. The counts are free; the detailed lists are paid add-ons.

Dark web exposure

Add-on

Leaked records that mention uzavirky-city.cz, from OffSeq Breach.

No leaked records found

Breach holds no records for uzavirky-city.cz right now. New leaks arrive continuously, so monitoring on Breach alerts you if that changes.

Monitor on Breach (opens in a new tab)

Technical appendix

Business context, site observations and technical notes gathered during the scan, and the standards behind each reference.

Business context

Business profile

The platform occupies a niche market segment providing localized traffic and road closure information for Benešov city. Its competitive advantage lies in real-time updates and integration with official municipal sources, positioning it as a trusted resource for local commuters. The business model is informational and likely funded or supported by local government or municipal agencies. Revenue streams are not evident, suggesting a public service orientation. Target customers include local residents, commuters, and visitors requiring traffic updates. Growth potential may be tied to expanding coverage or integrating additional city services. The partnership ecosystem includes official city websites and related local informational portals. Strategic observations highlight the importance of maintaining data accuracy and enhancing user engagement through improved technical and compliance measures.

Security posture

The website demonstrates a basic security maturity level with HTTPS enforced, ensuring encrypted communication. However, the absence of key security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options exposes the site to potential risks like clickjacking and MIME sniffing. No evidence of vulnerable libraries or exposed sensitive data was found, indicating a low immediate risk. Compliance gaps exist due to missing privacy and cookie policies, which are critical under GDPR and similar regulations. Incident response readiness is unclear as no security or abuse contact information is provided. The security culture appears minimal, with no visible certifications or frameworks referenced. Enhancing security headers, publishing privacy policies, and establishing incident response contacts would significantly improve the security posture.

Recommendations

  1. Implement comprehensive security headers including Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options to mitigate common web vulnerabilities.
  2. Publish clear and accessible privacy and cookie policies to comply with GDPR and enhance user trust.
  3. Add explicit contact information including emails and phone numbers for general inquiries and security incidents.
  4. Conduct regular audits of third-party scripts and plugins to identify and remediate potential vulnerabilities.
  5. Enhance accessibility features and SEO optimization to improve user experience and search engine visibility.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Description
Website provides a map and information about road closures, traffic restrictions, and accidents in Benešov city area.
Key services
Interactive map of road closures, Traffic incident updates, Links to official municipal traffic notices
Content quality
good
Branding
consistent

Technology

Stack
Google Maps API, WordPress, JavaScript, CSS, HTML5
Performance
moderate
Mobile
good
Accessibility
basic
SEO
basic

Security

Observed score
70/100
Good practices seen
  • HTTPS enabled

Analytics and tracking

Tracking level
minimal
Privacy practices
poor

Advertising

Transparency
poor

Site quality

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

Key observations

  1. Website is a local municipal or city service providing traffic and road closure information.
  2. No WHOIS data available, which limits domain trust assessment.
  3. No privacy, cookie, or terms of service policies found on the site.
  4. No contact emails or phone numbers explicitly provided on the homepage.
  5. Uses Google Maps API extensively for interactive map features.
  6. No signs of adult or questionable content; content is safe and general audience appropriate.
  7. No visible security headers detected in the HTML content.
  8. Website uses WordPress CMS with custom theme 'mapauzavirek'.
  9. External links mostly to official city domains and Google services.
  10. No analytics or tracking scripts detected beyond Google Maps API.
Technical notes

Notes

The website is built on WordPress CMS with a custom theme named 'mapauzavirek'. It extensively uses Google Maps API for interactive map functionalities, including markers for road closures and traffic incidents. The front-end employs standard HTML5, CSS, and JavaScript, with no advanced frameworks detected. Performance is moderate, with no major blocking issues but potential for optimization. Mobile responsiveness is good, ensuring usability across devices. Accessibility is basic, lacking advanced ARIA roles or semantic enhancements. SEO is basic, with meta tags present but no structured data or Open Graph tags detected. The absence of analytics or tracking scripts suggests minimal data collection. Hosting provider details are not discernible from the content. Overall, the technical infrastructure is functional but could benefit from modernization and enhanced compliance features.
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 uzavirky-city.cz. 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 uzavirky-city.cz.

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.