Skip to main content

Security report for dpmz.sk

Dopravný podnik mesta Žiliny s.r.o. · Transportation · Slovakia

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

Security score

41/100

Risk levelHigh

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

Dopravný podnik mesta Žiliny s.r.o. operates as the official public transportation provider for the city of Žilina, Slovakia. The website serves as a comprehensive portal offering schedules, ticketing information, news updates, and additional services such as charter transport and a tourist hostel. The company targets local residents and visitors, positioning itself as a key municipal service provider with a medium-sized operational footprint. The business model focuses on public transit services supported by digital tools like electronic ticketing and journey planning subdomains. Technically, the website employs a traditional web stack with jQuery and Nivo Slider for UI elements, alongside CookieYes for cookie consent management. While the site is functional and moderately optimized for mobile, it lacks advanced CMS indicators and modern frameworks. SEO and accessibility are basic but adequate for the target audience. Analytics integration includes Google Analytics and smartemailing.cz for newsletter management, reflecting a moderate level of digital maturity. From a security perspective, the site uses HTTPS and implements a detailed cookie consent mechanism, supporting GDPR compliance. However, it lacks visible HTTP security headers and published security policies or incident response contacts. No critical vulnerabilities or exposed sensitive data were detected. The absence of a terms of service page and limited mobile optimization are minor gaps. Overall, the security posture is moderate but could benefit from enhancements in header policies and formal security disclosures. The overall risk assessment is low, with the website demonstrating legitimacy, consistent business information, and a trustworthy digital presence. Strategic recommendations include implementing security headers, publishing security and incident response policies, improving mobile and accessibility features, and maintaining regular audits of third-party scripts to ensure ongoing security and compliance.

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

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

  3. 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 dpmz.sk

This scan found 29 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
42
Security headers
35
Email security
65
DNS health
65
Network security
0
GDPR outside view
40
Average
41

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

The company holds a strong local market position as the primary public transport operator in Žilina, Slovakia. Its competitive advantage lies in its official status and integration with municipal services, supported by digital tools such as electronic ticketing and journey planners. Revenue streams likely include ticket sales, charter services, and possibly advertising on vehicles. The target customer segment is broad, encompassing daily commuters, tourists, and local residents. Growth indicators include ongoing updates to services and digital offerings. The partnership ecosystem includes the website developer MaM multimedia and digital service subdomains. Strategic observations suggest a stable operation focused on service reliability and gradual digital enhancement.

Security posture

The current security maturity level is moderate. The website enforces HTTPS and provides a comprehensive cookie consent mechanism aligned with GDPR. However, it lacks advanced security headers such as Content Security Policy, HSTS, and X-Frame-Options, which are recommended to mitigate common web threats. No incident response or vulnerability disclosure policies are published, limiting transparency in security management. Data protection practices appear adequate for the scope of data collected, primarily through cookies and newsletter signups. The absence of phone contact details and security-specific emails reduces incident reporting readiness. Overall, the security culture is functional but could be improved with formal policies and enhanced technical controls.

Recommendations

  1. Implement HTTP security headers including CSP, HSTS, and X-Frame-Options to strengthen web security.
  2. Publish a formal security policy and incident response contact information to improve transparency and readiness.
  3. Add a vulnerability disclosure program or security.txt file to encourage responsible reporting.
  4. Enhance mobile optimization and accessibility to improve user experience and compliance.
  5. Conduct regular security audits of third-party scripts and dependencies to mitigate risks.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Dopravný podnik mesta Žiliny s.r.o.
Description
Oficiálna stránka dopravného podniku v meste Žilina. Vyhľadávanie spojenia, aktuálne informácie, zájazdová preprava a turistický hostel.
Key services
Public transport schedules, Charter transport, Tourist hostel, Ticketing services including SMS ticket, Customer support and information
Content quality
good
Branding
consistent

Technology

Stack
jQuery, Nivo Slider, CookieYes cookie consent
Performance
moderate
Mobile
basic
Accessibility
basic
SEO
basic

Security

Observed score
65/100
Good practices seen
  • Cookie consent banner with granular controls
  • No exposed sensitive data in HTML

Analytics and tracking

Services
Google Analytics, smartemailing.cz
Tracking level
moderate
Privacy practices
good

Advertising

Marketing tools
CookieYes
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 in Slovak language targeting local users in Žilina.
  3. Cookie consent is implemented with detailed categories and user controls.
  4. No explicit terms of service page found.
  5. Contact information includes webmaster email and contact forms but no phone numbers explicitly labeled.
  6. Social media presence on Facebook, YouTube, Instagram.
  7. Uses Google Analytics and smartemailing.cz for analytics and newsletter signup.
  8. No visible security headers or advanced security policies published.
  9. Website design is functional with moderate mobile optimization.
  10. No adult or questionable content detected.
Technical notes

Notes

The website uses a legacy but stable technology stack centered on jQuery and Nivo Slider for UI interactions. CookieYes is integrated for cookie consent management, reflecting compliance with privacy regulations. The CMS is custom or proprietary, with no popular CMS detected. Performance is moderate with room for improvement in mobile responsiveness and accessibility. SEO is basic with meta tags present but no advanced structured data like JSON-LD or Open Graph tags detected. Hosting provider and SSL configuration details are not available, limiting deeper infrastructure analysis. Technical debt is moderate due to older libraries and lack of modern frameworks, suggesting opportunities for modernization to improve performance and security.
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 dpmz.sk. 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 dpmz.sk.

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.