Skip to main content

Security report for grimex.lv

GRIMEX SIA · Other · Latvia

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

Security score

51/100

Risk levelMedium

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

GRIMEX SIA is a Latvian company offering a diverse range of services including web development, advertising, rental of offices, warehouses, equipment, and professional workers, as well as sales agency services. The company targets businesses looking to expand or operate in Latvia and Scandinavia, positioning itself as a versatile business partner with a 5-year presence in the Scandinavian market. The website content is basic and marketing-focused, with limited detailed business information and no visible privacy or cookie policies. Technically, the website is built on WordPress with Yoast SEO and uses common marketing and analytics tools such as Google Tag Manager, Google Analytics, and Facebook Pixel. However, the site suffers from a lack of a valid SSL certificate and does not serve content over HTTPS, which is a critical security shortfall. Performance is slow, and mobile optimization and accessibility are basic. SEO is reasonably well implemented through meta tags and structured data. From a security perspective, the site has some positive configurations such as SPF and DMARC DNS records and HSTS header enabled, but the absence of a valid SSL certificate and modern TLS protocols severely undermines the security posture. No security policies, incident response contacts, or vulnerability disclosures are present, and domain registration lacks protection locks, which could pose risks. Overall, the website presents moderate business credibility but has significant security and privacy compliance gaps. Strategic improvements in SSL deployment, privacy policy publication, and security best practices are recommended to enhance trust and compliance.

Scanned

NIS2 and GDPR posture

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

    • 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

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

This scan found 22 issues across 5 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
100
Security headers
40
Email security
77
DNS health
70
Network security
20
GDPR outside view
0
Average
51

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

GRIMEX SIA operates as a small-sized service provider in Latvia with a focus on multiple sectors including marketing, sales agency, and rental services. The company leverages partnerships in Scandinavia to expand its market reach. Its business model is diversified, offering both digital services like web development and physical services such as equipment rental and professional worker leasing. The website indicates a growth-oriented approach with an emphasis on collaboration and market conquest in Scandinavia. However, the lack of detailed business data and contact information on the website limits transparency. The company uses common digital marketing tools and tracking technologies to support its outreach and customer engagement strategies.

Security posture

The security posture of grimex.lv is currently weak due to the absence of a valid SSL certificate and lack of HTTPS, which exposes users to potential interception and undermines trust. While DNS records show proper SPF and DMARC configurations, and HSTS is enabled, the lack of TLS protocol support and missing security headers beyond HSTS indicate incomplete security hardening. No incident response or security policy information is available, and no vulnerability disclosure or security.txt file is found. The domain registration is active and consistent but lacks domain protection locks, which could increase risk of unauthorized changes. Overall, the site requires urgent improvements in SSL/TLS deployment and security policy transparency to meet modern security standards.

Recommendations

  1. Obtain and install a valid SSL/TLS certificate to enable HTTPS and secure user connections.
  2. Enable modern TLS protocols (TLS 1.2 or TLS 1.3) and disable outdated or insecure protocols.
  3. Publish comprehensive privacy and cookie policies to improve GDPR compliance and user trust.
  4. Add security headers such as Content-Security-Policy, X-Content-Type-Options, and X-Frame-Options.
  5. Implement domain protection locks to prevent unauthorized domain modifications.
  6. Provide clear contact information including phone numbers and physical addresses on the website.
  7. Establish and publish a security policy and incident response contact channels.
  8. Consider adding a vulnerability disclosure policy or security.txt file to encourage responsible reporting.
Technical notes

Notes

The website is built on WordPress CMS with Yoast SEO plugin, leveraging Google Tag Manager, Google Analytics, and Facebook Pixel for marketing and analytics. The site uses GTranslate for multilingual support. Performance is slow with a page load time of over 5 seconds and a large page size (~480 KB). Mobile optimization and accessibility are basic but functional. SEO is enhanced with meta tags, Open Graph, and JSON-LD structured data. However, the lack of a valid SSL certificate and disabled TLS protocols are critical technical deficiencies. DNS configuration is standard but lacks DNSSEC and CAA records. The site would benefit from performance optimization and modern security enhancements.
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 grimex.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 grimex.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.