Skip to main content

Security report for podi.lv

PODI.lv · Manufacturing · Latvia

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

Security score

58/100

Risk levelMedium

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

PODI.lv is a Latvian-based manufacturer specializing in frost-resistant concrete flower pots, vases, boxes, columns, and decorative architectural forms. Established in 1994, the company has a strong local presence serving both private and public sectors across Latvia. Their business model focuses on manufacturing and direct retail through an e-commerce platform built on WordPress and WooCommerce. The website reflects a mature business with consistent branding and a clear product catalog targeting customers seeking durable concrete products for interior and exterior use. Technically, the website leverages a modern WordPress infrastructure with popular plugins such as WooCommerce for e-commerce, Yoast SEO for search optimization, and Ajax Search for enhanced product search capabilities. The site uses HTTPS and integrates Google Analytics and Tag Manager for tracking. Mobile optimization and SEO practices are good, though accessibility features are basic. Performance is moderate, with room for improvement in security headers and privacy compliance. From a security perspective, the site uses HTTPS but lacks important security headers like Content-Security-Policy and HSTS. There is no visible security.txt or vulnerability disclosure policy, and privacy and cookie policies are not found in the provided content, indicating compliance gaps. No WHOIS data was available due to query limits, limiting domain legitimacy verification. Overall, the security posture is moderate but could be improved with better policy transparency and technical controls. The overall risk assessment suggests a legitimate small manufacturing business with a well-maintained website but with notable gaps in privacy compliance and security best practices. Strategic recommendations include publishing privacy and cookie policies, implementing security headers, adding a security.txt file, and ensuring regular updates and monitoring to enhance trust and compliance.

Scanned

NIS2 and GDPR posture

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

  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 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';…

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

Keep watching podi.lv

This scan found 24 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
75
Security headers
15
Email security
70
DNS health
75
Network security
100
GDPR outside view
10
Average
58

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

Breach exposure

Leaked credentials and lookalike domains from OffSeq Breach. The counts are free; the detailed lists are paid add-ons.

Dark web exposure

Add-on

Leaked records that mention podi.lv, from OffSeq Breach.

No leaked records found

Breach holds no records for podi.lv right now. New leaks arrive continuously, so monitoring on Breach alerts you if that changes.

Monitor on Breach (opens in a new tab)

Technical appendix

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

Business context

Business profile

PODI.lv holds a solid market position as a local Latvian manufacturer of concrete flower pots and architectural concrete products with over 25 years of operational history. Their competitive advantage lies in durable, frost-resistant products made using advanced casting and dry pressing methods with various finishing technologies. The business targets both private consumers and public sector clients in Latvia, leveraging direct e-commerce sales. The company maintains active social media channels to engage customers. Revenue streams are primarily product sales through the website. Growth indicators include a broad product catalog and consistent branding. The partnership ecosystem is not explicitly detailed, and no related or subsidiary domains were found. The company appears focused on maintaining a strong local presence with quality manufacturing and retail services.

Security posture

The website demonstrates a moderate security maturity level with HTTPS enabled and no visible exposure of sensitive data. However, the absence of key security headers such as Content-Security-Policy, X-Frame-Options, and HSTS reduces protection against common web attacks. The lack of a security.txt file or vulnerability disclosure policy indicates limited incident response readiness and transparency. Privacy compliance is weak due to missing privacy and cookie policies, which may expose the business to GDPR compliance risks. No explicit data protection officer contact or incident response channels were found. The use of popular and regularly updated WordPress plugins is a positive factor, but continuous monitoring and policy improvements are recommended to strengthen security culture and compliance.

Recommendations

  1. Publish comprehensive privacy and cookie policies on the website to improve GDPR compliance.
  2. Implement security headers such as Content-Security-Policy, X-Frame-Options, and HSTS to enhance web security.
  3. Add a security.txt file to provide clear vulnerability disclosure and incident response contact information.
  4. Regularly update WordPress core and plugins to mitigate vulnerabilities and maintain security posture.
  5. Enhance accessibility features and conduct periodic security audits to identify and remediate potential risks.

Contact details published on the site

Addresses
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
PODI.lv
Description
Izgatavojam sala izturīgus betona puķu podus, vāzes, kastes, kolonas, dekoratīvas arhitektoniskas formas, skulptūras. Izmantojam liešanas un sausās presēšanas metodes. Izmantojam dažādas apdares tehnoloģijas – dekoratīvie apmetumi, pigmentu iestrādes, krāsošana, pretmitruma apstrāde u.c. Ražotne darbojas no 1994. gada. Mūsu produkcija ir iekarojusi popularitāti visā Latvijā privātā un valsts sektorā. Latvijā ražoti, ilgmūžīgi un pamatīgi betona puķu podi interjeram, terasēm, dārziem, publiskām ārtelpām u.c.
Key services
Manufacture of frost-resistant concrete flower pots, Concrete vases, boxes, columns, sculptures, Use of casting and dry pressing methods
Content quality
good
Branding
consistent

Technology

Stack
WordPress 6.4.5, WooCommerce 8.6.1, jQuery 3.7.1, Yoast SEO plugin, Ajax Search for WooCommerce, Contact Form 7, Font Awesome 4.7.0 and 5.2.0, Owl Carousel, Nivo Lightbox, Total WordPress Theme
Frameworks
WooCommerce
Platforms
WordPress
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
65/100
Good practices seen
  • HTTPS enabled
  • No exposed sensitive data in HTML
  • Use of secure plugins

Analytics and tracking

Services
Google Analytics
Tracking level
moderate
Privacy practices
poor

Advertising

Transparency
basic

Site quality

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

Key observations

  1. Website is a WordPress WooCommerce e-commerce site selling concrete flower pots and related products.
  2. Content is in Latvian language with English locale tags.
  3. No privacy, cookie, or terms of service pages detected in the provided HTML content.
  4. Contact information including phone, email, and physical address is clearly provided in the footer.
  5. Social media links to Facebook and Instagram are present.
  6. Google Analytics and Google Tag Manager are used for tracking.
  7. No visible security.txt or vulnerability disclosure policy.
  8. No security headers detected in HTML source.
  9. WHOIS data unavailable due to query limit error; no registrar or domain age info extracted.
Technical notes

Notes

The website is built on a WordPress CMS platform using WooCommerce for e-commerce functionality. It employs modern JavaScript libraries including jQuery and various UI enhancement plugins like Owl Carousel and Nivo Lightbox. SEO is managed via Yoast SEO plugin, and product search is enhanced with Ajax Search for WooCommerce. The site uses Google Analytics and Google Tag Manager for analytics and tracking. Performance is moderate with good mobile optimization and basic accessibility. The technical stack is standard for small to medium e-commerce sites but lacks advanced security configurations such as HTTP security headers. Hosting provider details are not discernible from the HTML content. Overall, the technical infrastructure supports business needs but could benefit from security and privacy 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 podi.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 podi.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.