Skip to main content

Security report for pkltugs.com

PKL Latvia, SIA · Transportation · Latvia

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

Security score

61/100

Risk levelMedium

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

PKL Latvia, a member of the Alfons Hakans group, is a specialized tugboat company operating primarily in the Latvian port of Ventspils. Established in 2008, it offers a comprehensive range of maritime services including harbor towage, sea towage, icebreaking, salvage, and escorting. The company positions itself as a market leader in Latvia with a modern fleet of powerful ASD tugboats. The website reflects a professional business presence targeting maritime industry stakeholders and port operators. Technically, the website is built on WordPress using Elementor, leveraging modern web technologies such as jQuery, Slick Slider, and Google reCAPTCHA v3 for form security. The site is hosted behind Cloudflare DNS and CDN services, ensuring good performance and availability. Mobile optimization and user experience are good, though accessibility features are basic. SEO practices are present but could be enhanced. From a security perspective, the site uses HTTPS with a good SSL configuration and employs Google reCAPTCHA to protect forms. However, it lacks DNSSEC, security headers, and published security or incident response policies, which are areas for improvement. No privacy or cookie policies were found, indicating potential compliance gaps with GDPR or other privacy regulations. Overall, the website is trustworthy and professional with a solid business foundation. The main risks relate to privacy compliance and security hardening. Strategic improvements in these areas would enhance trust and regulatory adherence.

Scanned

NIS2 and GDPR posture

GDPR outside view
35/ 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. 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';…

  2. GDPR outside view

    These are the privacy signals visitors and data protection authorities look for under GDPR.

    • 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 Policy found

      GDPR requires clear information about cookie usage

      What to do: Add a dedicated cookie policy explaining cookie usage and purposes

Need hands-on remediation? Email guard@offseq.com

Keep watching pkltugs.com

This scan found 25 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
75
Security headers
15
Email security
75
DNS health
65
Network security
100
GDPR outside view
35
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

PKL Latvia operates in the transportation sector, specifically maritime tugboat services. Its competitive advantage lies in being part of the larger Alfons Hakans group and maintaining a modern, powerful fleet. The business model focuses on providing specialized towage and escort services to shipping and port clients. The company targets port operators and maritime logistics providers in Latvia and possibly the Baltic region. The website content and structure indicate a stable, small-sized company with a clear market leadership claim in Latvia. There is no evidence of extensive partnerships or subsidiaries beyond the parent group. The company appears focused on operational excellence and regional dominance in tugboat services.

Security posture

The current security posture is moderate. HTTPS is properly implemented, and Google reCAPTCHA v3 is used to protect forms from automated abuse. However, the absence of DNSSEC and security headers such as Content-Security-Policy and HSTS reduces the overall security robustness. No explicit security policies or incident response contacts are published, which may hinder rapid response to security incidents. The site does not expose sensitive data or show signs of vulnerable libraries, but the lack of visible security best practices and compliance documentation suggests room for improvement. GDPR compliance is not clearly demonstrated, increasing regulatory risk.

Recommendations

  1. Enable DNSSEC on the domain to enhance DNS security and prevent spoofing.
  2. Implement HTTP security headers including Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security.
  3. Publish a comprehensive privacy policy and cookie policy with GDPR compliance details.
  4. Develop and publish incident response and security policies including dedicated contact channels.
  5. Conduct regular security audits of plugins and third-party scripts to mitigate vulnerabilities.

Contact details published on the site

Addresses
Legal name
PKL Latvia, SIA
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
PKL Latvia, SIA
Description
PKL Latvia is a Latvian tugboat company specializing in harbour and sea towage in the Latvian port of Ventspils. It is a member of the Alfons Hakans group and operates a modern fleet of tugboats, offering services such as harbor towage, sea towage, icebreaking, salvage, and escorting.
Key services
Harbor towage, Sea towage, Icebreaking, Salvage, Escorting
Content quality
good
Branding
consistent

Technology

Stack
jQuery, Slick Slider, Font Awesome, Google Fonts, Google reCAPTCHA v3
Frameworks
Elementor, WordPress
Platforms
WordPress CMS
Performance
moderate
Mobile
good
Accessibility
basic
SEO
basic

Security

Observed score
65/100
Good practices seen
  • HTTPS enabled
  • Use of Google reCAPTCHA v3 on forms

Analytics and tracking

Tracking level
minimal
Privacy practices
poor

Advertising

Tracking pixels
Google reCAPTCHA
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. No privacy, cookie, or terms of service policies found on the site.
  3. Contact information is clearly presented in multiple locations.
  4. Website uses modern WordPress and Elementor technologies.
  5. Security posture is moderate but could be improved with DNSSEC and security headers.
  6. No analytics services detected beyond Google reCAPTCHA.
  7. Content is professional and relevant to maritime tugboat services.
  8. No suspicious or malicious content detected.
Technical notes

Notes

The website uses a modern WordPress CMS with Elementor page builder, supported by jQuery and Slick Slider for UI components. Google Fonts and Font Awesome provide typography and icons. Google reCAPTCHA v3 is integrated for form security. Hosting is behind Cloudflare DNS and CDN, improving performance and availability. The site is mobile optimized and has a clear navigation structure. However, accessibility features are basic and SEO could be further enhanced. No major technical debt is evident, but security hardening and privacy compliance require attention to reduce risks.
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 pkltugs.com. 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 pkltugs.com.

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.