Skip to main content

Security report for kuldigasautoskola.lv

Other

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

Security score

60/100

Risk levelMedium

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

The website www.kuldigasautoskola.lv appears to be a business site likely related to a driving school or educational service, hosted on the Wix platform. However, due to access restrictions and rate limiting, the full content and business details are not accessible for analysis. The technical infrastructure is based on Wix's standard technology stack, including core-js polyfills and Wix's proprietary scripts. Security posture cannot be fully assessed due to lack of accessible data, but no explicit security headers or SSL details were found in the accessible content. The absence of privacy policies, cookie consent mechanisms, and contact information further limits the ability to evaluate compliance and business credibility. Overall, the site is likely safe for general audiences but lacks transparency and visible trust indicators. Strategic recommendations include improving WHOIS transparency, adding privacy and cookie policies, and enhancing contact and security information to build trust.

Scanned

NIS2 and GDPR posture

GDPR outside view
25/ 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

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

This scan found 26 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
35
Email security
60
DNS health
75
Network security
100
GDPR outside view
25
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

Technical appendix

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

Business context

Business profile

Due to limited accessible content, detailed business intelligence is unavailable. The site is built on Wix, indicating a small to medium-sized business model likely focused on local or regional driving education services. No partner or subsidiary domains were identified. The lack of visible business information and contact details suggests a need for improved digital presence and transparency to enhance market positioning and customer trust.

Security posture

The current security posture is weak due to lack of visible HTTPS enforcement confirmation, absence of security headers, and no incident response or security policy information. The site does not display GDPR compliance indicators or data protection officer contacts. The use of Wix platform provides some baseline security, but the lack of explicit security best practices and policies is a concern. No vulnerabilities were detected in the accessible content, but the inability to fully analyze the site due to WAF or rate limiting is a limitation.

Recommendations

  1. Implement and publicly display a comprehensive privacy policy and cookie consent mechanism to comply with GDPR and enhance user trust.
  2. Ensure WHOIS data is accessible and transparent to improve domain legitimacy and trustworthiness.
  3. Add clear contact information including business address, phone numbers, and email addresses to improve business credibility.
  4. Configure and verify HTTPS with strong SSL/TLS settings and implement security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options.
  5. Develop and publish a security policy and incident response plan with contact channels to demonstrate security maturity and readiness.
Site observations

Automated reading of the public site. Ratings are indicative.

Generic detected. WHOIS query limit exceeded error and minimal HTML content with heavy Wix platform scripts indicate possible rate limiting or WAF protection blocking full content access. These observations may be incomplete. For a fuller analysis, contact guard@offseq.com.

Business

Technology

Stack
Wix, core-js, focus-within-polyfill
Platforms
Wix.com

Analytics and tracking

Site quality

Trustworthiness
low

Key observations

  1. Website content is heavily restricted or blocked from full analysis.
  2. WHOIS data unavailable due to query limit error.
  3. Website built on Wix platform with standard Wix scripts and assets.
  4. No privacy, cookie, or terms of service policies detected.
  5. No contact information or business details found in accessible content.
  6. No security headers or SSL configuration details available.
  7. No analytics or advertising scripts detected in accessible content.
  8. No adult or explicit content detected; site appears safe for general audience.
  9. WAF or rate limiting likely preventing full content retrieval.
Technical notes

Notes

The website is built on the Wix platform, utilizing Wix's proprietary scripts and standard polyfills such as core-js and focus-within-polyfill for browser compatibility. The site uses static media hosted on Wix's CDN domains. Performance and accessibility cannot be fully assessed due to content access restrictions. The site appears to be mobile-optimized as per Wix standards, but no explicit accessibility or SEO optimizations were detected in the accessible content. The technical stack is modern but limited by the platform's constraints and lack of custom security or analytics integrations.
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 kuldigasautoskola.lv. 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 kuldigasautoskola.lv.

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.