Skip to main content

Security report for holice.eu

Město Holice · Government · Czech Republic

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

Security score

61/100

Risk levelMedium

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

Město Holice operates an official municipal government website providing comprehensive information about the city, local government services, events, and public notices. The site targets residents and visitors, offering easy access to official contacts, news, and e-services. The website is well-branded with consistent city imagery and maintains active social media presence on Facebook, Instagram, and YouTube. Technically, the site uses modern frameworks such as Bootstrap and jQuery, integrates Google Analytics for visitor tracking, and implements GDPR-compliant cookie consent mechanisms. The site is mobile-optimized and provides a good user experience with clear navigation and relevant content. Security posture is solid with HTTPS enforced and no visible vulnerabilities, though security headers and explicit security policies are absent. WHOIS data is unavailable due to EURid privacy restrictions, but the domain usage and content strongly indicate legitimacy as a municipal government site. Overall, the site is trustworthy, professional, and serves its intended audience effectively.

Scanned

This is an earlier scan of holice.eu. View the latest report

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

8 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 holice.eu

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. 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
62
Security headers
15
Email security
65
DNS health
85
Network security
100
GDPR outside view
40
Average
61

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 website positions Město Holice as a local government entity providing essential municipal services and information. Its business model is informational and service-oriented, focusing on transparency and community engagement. The site leverages partnerships with local cultural and technical organizations, enhancing its service ecosystem. Revenue streams are not applicable as it is a government site. The target audience includes local residents, tourists, and stakeholders interested in city governance and events. Growth indicators include active content updates and integration of digital tools like chatbots. The partnership ecosystem includes cultural museums and technical services, reflecting a collaborative municipal approach. Strategic observations highlight the importance of maintaining digital maturity and enhancing security policies to build further trust.

Security posture

The website demonstrates a moderate to good security maturity level. HTTPS is properly configured, and cookie consent is implemented in line with GDPR requirements. However, the absence of security headers such as Content-Security-Policy and X-Frame-Options represents a gap that could be exploited. No exposed sensitive data or vulnerable libraries were detected. There is no published incident response or vulnerability disclosure policy, which limits transparency and preparedness. Data protection officer contact information is not provided, which may be a compliance gap under GDPR. Overall, the security posture is adequate for a municipal informational site but could be improved by adopting additional security best practices and formal policies.

Recommendations

  1. Implement HTTP security headers including Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options to enhance protection against common web attacks.
  2. Publish a clear security policy and incident response contact information to improve transparency and readiness.
  3. Develop and publish a vulnerability disclosure policy or security.txt file to encourage responsible reporting of security issues.
  4. Provide contact details for a Data Protection Officer or privacy contact to strengthen GDPR compliance.
  5. Regularly review and update third-party scripts and libraries to mitigate potential vulnerabilities.

Contact details published on the site

Addresses
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Město Holice
Description
Webové stránky města Holic. Přehledné informace o městě, úřadu, pořádaných akcích atd. Informační centrum, turistické informace. Vše na jednom místě.
Key services
city news and updates, official notices, event calendar, contact information, tourist information, e-services portal
Content quality
good
Branding
consistent

Technology

Stack
Bootstrap 4.5.3, jQuery 3.7.1, Google Analytics (gtag.js), weatherwidget.io, FreePrivacyPolicy.com cookie consent, maica-bot chatbot
Frameworks
Bootstrap
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
80/100
Good practices seen
  • HTTPS enforced
  • Cookie consent implemented
  • No exposed sensitive data in HTML

Analytics and tracking

Services
Google Analytics
Tracking level
moderate
Privacy practices
good

Advertising

Marketing tools
maica-bot chatbot
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. WHOIS data is unavailable due to EURid privacy policies and query failure.
  3. Site uses HTTPS with valid SSL and modern JavaScript libraries.
  4. Cookie consent is implemented in compliance with GDPR.
  5. No contact email addresses explicitly found in HTML source.
  6. Phone number and physical address clearly provided in footer.
  7. Social media links to official city accounts are present.
  8. No terms of service or explicit security policies found.
  9. No vulnerability disclosure or security.txt file detected.
  10. Content is focused on municipal information and events.
Technical notes

Notes

The website uses a modern and stable technology stack including Bootstrap 4.5.3 and jQuery 3.7.1, ensuring responsive design and interactive features. Google Analytics is integrated for visitor tracking, and a chatbot service (maica-bot) is deployed for user engagement. The site loads scripts asynchronously where appropriate, improving performance. The HTML structure is valid and SEO-friendly with comprehensive meta tags and Open Graph data. Mobile optimization is good, and accessibility features are basic but present. Hosting provider details are not explicitly identified. Performance is moderate, with potential for improvement by optimizing image sizes and script loading. No CMS is explicitly detected, suggesting a custom or static site 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

Earlier scans of this domain

  1. 61/100Medium31 findingsView report
Reviews of this site

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