Skip to main content

Security report for pkmoto.lv

P.K.Moto · Retail · Latvia

High risk. 7 critical or high findings in GDPR outside view, SSL/TLS and 2 other checks.

Security score

42/100

Risk levelHigh

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

P.K.Moto is a Latvian retail business specializing in motorcycle equipment, tools, garden and home equipment, and related technical products. The company operates an e-commerce website complemented by a physical store located in Ogre, Latvia. Their product range includes moto equipment, instruments, service equipment, spare parts, and auto and moto products, targeting consumers and businesses within Latvia. The website is built on the DIRcms.lv platform and employs a variety of JavaScript libraries to enhance user experience and functionality. Tracking tools such as Google Analytics and Facebook Pixel are used for marketing and analytics purposes. Security posture is moderate with HTTPS enabled but lacks advanced security headers and cookie consent mechanisms. WHOIS data could not be retrieved, limiting domain trust verification. Overall, the website presents a professional retail platform with clear contact information and a safe content environment.

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

7 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

    • High

      No Cookie Consent Banner found

      GDPR requires explicit consent for non-essential cookies

      What to do: Implement a cookie consent banner that appears on first visit

  2. SSL/TLS

    TLS encrypts the connection and proves the site is really yours. Weak or expiring certificates trigger browser warnings and put traffic at risk.

    • Critical

      Unable to retrieve SSL certificate

      Could not establish secure connection to retrieve certificate information

      What to do: Check if the server is accessible and SSL/TLS is properly configured

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

This scan found 18 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
0
Security headers
60
Email security
70
DNS health
75
Network security
20
GDPR outside view
25
Average
42

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 company positions itself as a local Latvian retailer with a broad product offering in the motorcycle and technical equipment sector. Their business model is primarily e-commerce with physical store support, serving a niche market of moto enthusiasts and technical equipment consumers. The presence of multiple product categories and brands indicates a diverse inventory. The website's moderate technical implementation and use of common marketing tools suggest a business with some digital maturity but room for improvement in privacy compliance and security. No partnerships or subsidiaries were identified from the data. The company appears to maintain a direct-to-consumer sales approach with delivery services across Latvia.

Security posture

The website uses HTTPS, ensuring encrypted communication, which is a fundamental security requirement. However, the absence of key security headers such as Content-Security-Policy, X-Frame-Options, and HSTS reduces the overall security posture. No explicit security policies or incident response contacts are published, which may impact customer trust and compliance with regulations like GDPR. The use of third-party JavaScript libraries and tracking pixels introduces potential privacy concerns, especially without visible cookie consent mechanisms. No vulnerabilities or exposed sensitive data were detected in the HTML content. Overall, the security maturity is moderate but could be significantly improved by implementing recommended headers and privacy controls.

Recommendations

  1. Implement comprehensive security headers including Content-Security-Policy, X-Frame-Options, and HSTS to enhance protection against common web attacks.
  2. Add a visible cookie consent banner and cookie policy to comply with GDPR and improve user privacy transparency.
  3. Regularly update and audit third-party libraries to mitigate risks from vulnerable components.
  4. Publish a clear security policy and incident response contact information to build trust and demonstrate compliance.
  5. Obtain and maintain accessible WHOIS data or domain registration transparency to improve legitimacy and trustworthiness.

Contact details published on the site

Addresses
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
P.K.Moto
Description
Online and physical store selling motorcycle equipment, tools, garden and home equipment, service equipment, spare parts, and auto and moto products.
Key services
Online product sales, Physical store sales, Delivery across Latvia, Customer support
Content quality
good
Branding
moderate

Technology

Stack
jQuery, jQuery UI, bxSlider, Fancybox, Owl Carousel, PhotoSwipe, Semantic UI, Rater, SweetAlert, Range Slider, Superfish, EasyAutocomplete, Google Analytics, Facebook Pixel
Frameworks
Semantic UI
Performance
moderate
Mobile
basic
Accessibility
basic
SEO
basic

Security

Observed score
60/100
Good practices seen
  • HTTPS enabled
  • No exposed sensitive data in HTML

Analytics and tracking

Services
Google Analytics, Facebook Pixel
Tracking level
moderate
Privacy practices
basic

Advertising

Tracking pixels
Facebook Pixel
Marketing tools
Facebook Pixel
Transparency
basic

Site quality

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

Key observations

  1. Website is an e-commerce platform for moto and technical equipment in Latvia.
  2. WHOIS data unavailable due to query limit error.
  3. No privacy or cookie consent banner detected despite GDPR relevance.
  4. Contact information is clearly presented including phone numbers, email, and physical address.
  5. Uses multiple JavaScript libraries and tracking pixels (Google Analytics, Facebook Pixel).
  6. No advanced security headers detected; HTTPS is enabled.
  7. No explicit security or incident response policies found on site.
  8. Content is safe and appropriate for general audiences.
  9. Website uses DIRcms.lv CMS platform.
Technical notes

Notes

The website is built on DIRcms.lv CMS and uses a variety of JavaScript libraries such as jQuery, bxSlider, Fancybox, Owl Carousel, Semantic UI, and others to provide interactive features and a rich user interface. Google Fonts are used for typography. The site loads tracking scripts for Google Analytics and Facebook Pixel, indicating marketing and user behavior tracking. The site is moderately optimized for performance and mobile devices but could improve accessibility and SEO optimization. The lack of advanced security headers and cookie consent mechanisms indicates technical debt in security and privacy compliance areas. Hosting provider details were not identified from the content.
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 pkmoto.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 pkmoto.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.