Skip to main content

Security report for lowicz.eu

Urząd Miejski w Łowiczu · Government · Poland

Medium risk. 9 critical or high findings in GDPR outside view, Security headers and 1 other check.

Security score

60/100

Risk levelMedium

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

The website www.lowicz.eu serves as the official municipal government portal for the city of Łowicz in Poland. It provides basic local government information, contact details, and links to related municipal business and tourism sites. The site targets residents and visitors seeking official information and services. The business model is that of a government service provider with a local authority market position. Technically, the site is simple, built with basic HTML and CSS, with minimal mobile optimization and no detected CMS or advanced frameworks. There is no evidence of analytics or tracking technologies, and no forms for data collection are present. Security posture is limited; no HTTPS status or security headers were detected in the provided data, and no privacy or cookie policies are published. Contact information is clearly provided, enhancing business credibility. WHOIS data is unavailable due to EURid privacy policies, which is common for .eu domains but reduces transparency. Overall, the site is safe, suitable for general audiences, and functions as a basic informational portal.

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

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

    • 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 lowicz.eu

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
67
Security headers
15
Email security
90
DNS health
80
Network security
100
GDPR outside view
10
Average
60

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 lowicz.eu, from OffSeq Breach.

No leaked records found

Breach holds no records for lowicz.eu 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 municipal government of Łowicz operates this website to provide official information and services to its constituents. The site links to partner domains focused on business and tourism, indicating a collaborative ecosystem supporting local economic and cultural activities. The business model is non-commercial, focused on public service. The lack of advanced digital infrastructure suggests limited investment in digital transformation. The site’s market position is stable as a local government authority, with trust derived from official contact details and domain naming. Growth indicators or parent/subsidiary relationships are not evident. The site’s simplicity and limited content suggest a focus on essential communication rather than extensive digital engagement.

Security posture

Security maturity is low to moderate. The absence of visible HTTPS confirmation and security headers indicates potential vulnerabilities to common web threats. No privacy or cookie policies limit GDPR compliance visibility. No incident response or vulnerability disclosure information is provided, which could hinder timely security issue management. The lack of analytics and tracking reduces privacy risks but also limits insight into user behavior. The WHOIS privacy protection reduces transparency but is not unusual for .eu domains. Recommendations include implementing HTTPS, adding security headers, publishing privacy and cookie policies, and establishing incident response contacts to improve security posture and compliance.

Recommendations

  1. Implement HTTPS across the entire website to secure user connections.
  2. Add standard security headers such as Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security.
  3. Publish comprehensive privacy and cookie policies to enhance GDPR compliance and user trust.
  4. Establish and publicize incident response and vulnerability disclosure contacts to improve security readiness.
  5. Enhance mobile optimization and accessibility to improve user experience and reach.

Contact details published on the site

Addresses
Legal name
Urząd Miejski w Łowiczu
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Urząd Miejski w Łowiczu
Description
Official municipal government website for the city of Łowicz, Poland, providing local government information and services.
Key services
Local government information, Business and tourism links, Payment services via Polska bezgotówkowa program
Content quality
basic
Branding
moderate

Technology

Stack
HTML, CSS
Performance
moderate
Mobile
basic
Accessibility
basic
SEO
basic

Security

Observed score
40/100

Analytics and tracking

Tracking level
minimal
Privacy practices
poor

Advertising

Transparency
poor

Site quality

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

Key observations

  1. Website is a basic official municipal government site for Łowicz, Poland.
  2. No WHOIS registrant data available due to EURid privacy policy.
  3. No privacy, cookie, or terms of service policies found on the site.
  4. No security headers or HTTPS status information available from provided data.
  5. Minimal technical sophistication; no CMS or advanced frameworks detected.
  6. Contact information is clearly provided in footer with email and phone.
  7. External links point to related municipal business and tourism sites and official Facebook page.
  8. No forms or data collection mechanisms detected in HTML content.
  9. No analytics or tracking scripts detected.
  10. No advertising or marketing tools detected.
Technical notes

Notes

The website uses basic HTML and CSS without detectable CMS or JavaScript frameworks. Responsive design is minimally addressed via CSS media queries. No analytics or tracking scripts are present, indicating a privacy-conscious or minimalistic approach. Hosting provider and SSL configuration details are not available from the provided data. Performance is likely moderate given the simplicity of the site. Technical debt appears low but modernization opportunities exist, especially in security and user experience enhancements. The lack of structured data (JSON-LD, Open Graph) limits SEO potential. Overall, the technical infrastructure supports basic informational needs but could benefit from modernization and security improvements.
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 lowicz.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 lowicz.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.