Skip to main content

Security report for parkingplzen.cz

Plzeňské městské dopravní podniky, a.s. · Transportation · Czech Republic

High risk. 9 critical or high findings in GDPR outside view, Email security and 3 other checks.

Security score

47/100

Risk levelHigh

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

Parking Plzeň is a municipal parking management service operated by Plzeňské městské dopravní podniky, a.s., responsible for organizing parking in the city center of Plzeň. The website provides information about parking houses, paid parking zones, and parking cards, targeting residents and visitors seeking convenient parking solutions. The business model focuses on public service and urban traffic management, positioning itself as the official parking authority in Plzeň. The site offers downloadable official documents and integrates with public transport services for combined mobility solutions. Technically, the website uses a modern technology stack including jQuery, Bootstrap 4, Video.js, and Google Analytics, managed via niCMS. It is mobile-optimized with good SEO practices and uses HTTPS with a cookie consent mechanism, reflecting a moderate to good level of digital maturity. However, the absence of a privacy policy and terms of service pages indicates areas for compliance improvement. From a security perspective, the site enforces HTTPS and uses consent-based tracking scripts but lacks advanced security headers and published security policies. No vulnerabilities or exposed sensitive data were detected in the HTML content. The missing WHOIS data reduces domain trustworthiness, though the website content and contact details suggest a legitimate municipal service. Overall, the website is professional, trustworthy, and functional but would benefit from enhanced privacy compliance and transparency regarding domain registration and security policies.

Scanned

NIS2 and GDPR posture

GDPR outside view
40/ 100 · High
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

  2. 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.

    • Critical

      No email authentication configured

      Domain is vulnerable to email spoofing

      What to do: Implement SPF, DKIM, and DMARC immediately

  3. Network security

    Services reachable from the internet are the first thing attackers probe. Anything open that does not need to be should be closed.

    • Critical

      Critical Service Exposed: MySQL

      Port 3306 (MySQL) is publicly accessible - MySQL - Database server

      What to do: Immediately restrict access to MySQL using firewall or VPN

      • NIS2 21(2)(e)
      • IR 2024/2690 6.7.2(f): Implementing Regulation (EU) 2024/2690, Annex point 6.7.2(f): Network security
      • NIST CM-7: NIST SP 800-53 Rev. 5 CM-7: Least Functionality
      • NIST SC-7: NIST SP 800-53 Rev. 5 SC-7: Boundary Protection
  4. 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 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 parkingplzen.cz

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. 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
85
Security headers
35
Email security
60
DNS health
60
Network security
0
GDPR outside view
40
Average
47

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 · found on this site
  • 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

Parking Plzeň operates within the transportation sector as a municipal service managing static traffic and parking infrastructure in Plzeň. Its competitive advantage lies in its official status under the city’s public transport company, enabling integrated parking and public transport solutions. Revenue streams likely include parking fees, parking card sales, and possibly municipal funding. The target customers are local residents, commuters, and visitors to Plzeň. The presence of downloadable forms and detailed parking information indicates a customer-centric approach. Partnerships with public transport and city information portals enhance its ecosystem. Growth indicators include digital presence and mobile app promotion. Strategic observations suggest focusing on compliance and security transparency to strengthen public trust.

Security posture

The website demonstrates a moderate security maturity level with HTTPS enforcement and cookie consent mechanisms. No critical vulnerabilities or exposed sensitive data were found. However, the absence of security headers such as Content-Security-Policy and lack of published security or incident response policies indicate gaps. GDPR compliance is partial due to missing privacy policy documentation. Incident response readiness and data protection officer contact information are not provided, limiting transparency. The use of Google Tag Manager and Analytics is managed with consent but could be further enhanced with detailed data retention policies. Overall, the security posture is adequate for a municipal service website but requires improvements in policy publication and header implementation.

Recommendations

  1. Publish a comprehensive privacy policy page to improve GDPR compliance and user trust.
  2. Add a terms of service page detailing user rights and obligations.
  3. Implement security headers such as Content-Security-Policy, X-Content-Type-Options, and Strict-Transport-Security.
  4. Provide clear incident response contact information and consider publishing a security policy.
  5. Verify and publish accurate WHOIS domain registration data to enhance domain trustworthiness.

Contact details published on the site

Addresses
Legal name
Plzeňské městské dopravní podniky, a.s.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Plzeňské městské dopravní podniky, a.s.
Description
Organizuje parkování v centru města Plzně, spravuje parkovací domy, placená parkoviště a parkovací zóny. Poskytuje služby veřejnosti a městu v oblasti statické dopravy.
Key services
Správa parkovacích domů, Provoz placených parkovišť, Organizace parkovacích zón, Prodej parkovacích karet
Content quality
good
Branding
consistent

Technology

Stack
jQuery, Bootstrap 4, Video.js, Magnific Popup, Fancybox 2.1.5, Google Fonts, Google Tag Manager, Google Analytics, Revolution Slider, Easy Pie Chart, LazySizes
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • Cookie consent banner with consent mechanism
  • No exposed sensitive data in HTML
  • Use of Google Tag Manager with consent control

Analytics and tracking

Services
Google Analytics, Google Tag Manager
Tracking level
moderate
Privacy practices
basic

Advertising

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 and relevant to municipal parking services.
  3. No privacy policy or terms of service pages found, which is a compliance gap.
  4. Cookie consent banner is implemented with express consent mechanism.
  5. WHOIS data is missing, which is unusual and reduces domain trust.
  6. Use of modern web technologies and analytics tools is evident.
  7. Contact information is clearly provided with official company email and phone.
  8. No security.txt or vulnerability disclosure information found.
Technical notes

Notes

The website is built on niCMS with a modern front-end stack including Bootstrap 4 and jQuery. It uses several third-party libraries for UI components, video playback, and image galleries. Google Fonts and Google Tag Manager are integrated for typography and analytics. The site is mobile responsive and uses lazy loading for images, improving performance. However, some accessibility features could be enhanced. The site loads multiple minified CSS and JS files, indicating optimization efforts. Hosting provider details are not explicit. Overall, the technical infrastructure is solid but could benefit from improved accessibility and security header implementation.
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 parkingplzen.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 parkingplzen.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.