Skip to main content

Security report for hrx.lv

HRX Latvija · Transportation · Latvia

Medium risk. 3 critical or high findings in Security headers and SSL/TLS.

Security score

65/100

Risk levelMedium

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

HRX Latvija is a logistics and freight transportation company operating primarily in Latvia with international service offerings. The company provides reliable and secure logistics, international and local freight transport, warehouse services, and cargo forwarding. The website is professionally designed using WordPress CMS with SEO optimization via Yoast and integrates Google Analytics and Google Tag Manager for marketing and analytics purposes. Cookie consent is managed through Cookiebot, ensuring compliance with cookie regulations. However, explicit privacy policy and terms of service pages are not found in the provided content, which is a compliance gap. The website uses HTTPS and shows no signs of WAF or content blocking, indicating good accessibility and security posture. WHOIS data could not be retrieved due to query limits, but no suspicious indicators were found in the website content or technical setup.

Scanned

NIS2 and GDPR posture

GDPR outside view
83/ 100 · Low
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

3 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 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. 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.

    • High

      Weak Protocols Supported

      Server supports weak protocols: TLSv1.1

      What to do: Disable TLS 1.0, TLS 1.1, and all SSL versions

      • CWE-327
      • OWASP A04:2025
      • ASVS V12.1.1

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

Keep watching hrx.lv

This scan found 20 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
62
Security headers
50
Email security
70
DNS health
85
Network security
40
GDPR outside view
83
Average
65

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 targets businesses and individuals requiring freight and logistics services in Latvia and neighboring countries, supported by sister sites in multiple European countries. The business model focuses on transportation and logistics services, including warehousing and cargo forwarding. The website content and structure suggest a medium-sized enterprise with a consistent brand presence and a regional market position. The use of multiple country-specific domains indicates a broader regional footprint. The absence of direct contact details on the main page may limit immediate customer engagement but could be present on other pages not included in the data.

Security posture

The website enforces HTTPS and uses a cookie consent mechanism, which are positive security indicators. However, no explicit security headers were detected in the provided data, and there is no visible security policy or incident response information. The absence of a vulnerability disclosure policy or security.txt file suggests limited transparency in security practices. No vulnerabilities or exposed sensitive data were found in the HTML content. Overall, the security posture is moderate but could be improved by implementing recommended headers, publishing security policies, and enhancing incident response readiness.

Recommendations

  1. Publish a comprehensive privacy policy and terms of service pages to improve compliance and user trust.
  2. Implement standard security headers such as Content-Security-Policy, Strict-Transport-Security, X-Frame-Options, and X-Content-Type-Options.
  3. Add explicit contact information including company emails and phone numbers on the website for better business credibility.
  4. Develop and publish a vulnerability disclosure policy and security.txt file to enhance transparency and security culture.
  5. Improve accessibility features to ensure compliance with accessibility standards and enhance user experience.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
HRX Latvija
Description
HRX Latvija – ātri, uzticami un droši loģistikas, starptautiskie un kravu pārvadājumi Latvijā, kā arī noliktavu un kravu ekspedīcijas pakalpojumi.
Key services
International freight transport, Local freight transport, Warehouse services, Cargo forwarding services
Content quality
good
Branding
consistent

Technology

Stack
WordPress 6.7.2, Yoast SEO plugin, jQuery, Cookiebot consent management, Google Tag Manager, Google Maps API
Platforms
WordPress
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

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

Analytics and tracking

Services
Google Analytics
Tracking level
moderate
Privacy practices
basic

Advertising

Ad networks
Google
Tracking pixels
Cookiebot
Marketing tools
Cookiebot
Transparency
basic

Site quality

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

Key observations

  1. Website is a professional logistics and freight transport service provider in Latvia.
  2. Content is in Latvian with alternate language versions for other countries.
  3. Cookie consent is implemented via Cookiebot with detailed cookie categories.
  4. No explicit privacy policy or terms of service pages found in the provided HTML.
  5. WHOIS data unavailable due to query limit error.
  6. Website uses WordPress CMS with Yoast SEO and Google Analytics.
  7. No contact emails or phone numbers explicitly found in the HTML snippet.
  8. No social media links explicitly found in the provided content.
  9. No security.txt or vulnerability disclosure policy detected.
  10. No incident response or security policy information found.
Technical notes

Notes

The website is built on WordPress 6.7.2 with Yoast SEO plugin, jQuery, and Cookiebot for cookie consent management. Google Tag Manager and Google Maps API are integrated for analytics and location services. The site is mobile optimized with good SEO practices including meta tags and structured data (JSON-LD). Performance is moderate with room for improvement in loading speed and accessibility. Hosting provider details are not evident from the HTML content. The technical stack is modern and suitable for a medium-sized logistics business but could benefit from enhanced security configurations and performance optimizations.
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 hrx.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 hrx.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.