Skip to main content

Security report for lubella.pl

Lubella · Retail · Poland

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

Security score

52/100

Risk levelMedium

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

Lubella.pl is the official website of the Lubella brand, a well-established Polish food manufacturer specializing in pasta, cereals, and snacks. The site reflects a mature brand presence supported by its parent company Maspex, with a focus on family-oriented food products and recipes. The website is professionally designed with consistent branding and clear navigation, targeting general consumers and families in Poland. Technically, the site uses modern web technologies including jQuery, Google Tag Manager, and a custom CMS, delivering moderate performance and good mobile optimization. Security posture is solid with HTTPS enforced and cookie consent implemented, though there is room for improvement in security headers and explicit incident response policies. Privacy compliance is well addressed with accessible privacy and cookie policies. Overall, the site presents a trustworthy and professional digital presence for the Lubella brand.

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

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

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

Keep watching lubella.pl

This scan found 19 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
55
Email security
70
DNS health
60
Network security
100
GDPR outside view
25
Average
52

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

Lubella operates in the retail and manufacturing sectors, focusing on food products such as pasta and cereals. The business model centers on product manufacturing and direct consumer engagement through recipes and promotions. The brand enjoys a strong market position in Poland, supported by partnerships with national research bodies and EU funding programs. The website's integration with partner domains like Maspex.com and Uwielbiam.pl indicates a collaborative ecosystem enhancing brand reach. The absence of direct contact emails or phone numbers on the homepage suggests a preference for social media and partner channels for customer interaction. The site’s content and structure support a medium to large enterprise with a focus on brand consistency and consumer trust.

Security posture

The website demonstrates a good security baseline with HTTPS enabled and cookie consent mechanisms in place. However, no advanced security headers such as Content-Security-Policy or X-Frame-Options were detected, which could enhance protection against common web attacks. There is no publicly available security policy or incident response contact information, which limits transparency in security management. No vulnerabilities or exposed sensitive data were found in the HTML content. The use of Google Tag Manager without a configured Google Analytics ID suggests limited tracking, which may reduce privacy risks. Overall, the security posture is adequate but could benefit from formalized policies and enhanced header configurations.

Recommendations

  1. Implement and publish a comprehensive security policy and incident response plan on the website.
  2. Add security headers such as Content-Security-Policy, X-Content-Type-Options, and X-Frame-Options to improve protection.
  3. Consider publishing a security.txt file to facilitate vulnerability disclosure and improve transparency.
  4. Enhance accessibility features to improve compliance and user experience for all users.
  5. Provide clear and direct contact information including company emails and phone numbers for customer support and security reporting.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Lubella
Description
Pasja i zaangażowanie ludzi na każdym etapie powstawania produktów Lubelli to gwarancja udanych rodzinnych chwil ze smakiem
Key services
Production and sale of pasta, Production and sale of cereals and snacks
Content quality
good
Branding
consistent

Technology

Stack
jQuery, Bootstrap (implied by navbar classes), Google Tag Manager, Google Custom Search Engine
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
75/100
Good practices seen
  • HTTPS enforced
  • No visible exposed sensitive data
  • Cookie consent implemented

Analytics and tracking

Services
Google Tag Manager
Tracking level
moderate
Privacy practices
good

Advertising

Marketing tools
Google Custom Search Engine
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. Content is professionally presented and relevant to the food manufacturing and retail sector.
  3. Cookie consent and privacy policy are implemented and accessible.
  4. No direct contact emails or phone numbers found on the homepage; contact is mainly via social media and partner sites.
  5. No explicit security or incident response policies published.
  6. No terms of service page detected.
  7. Use of Google Tag Manager indicates tracking but no Google Analytics ID configured.
  8. Branding is consistent and supported by parent company Maspex.
  9. EU funding and national research partner logos indicate legitimate business partnerships.
Technical notes

Notes

The website uses a custom or proprietary CMS with JavaScript libraries like jQuery and Google Tag Manager for analytics and marketing. The site is mobile optimized and uses responsive design techniques. Performance is moderate with no major issues detected in the HTML content. SEO is supported by proper meta tags including description and keywords. The site lacks explicit use of modern frameworks or platforms such as React or Angular, indicating a traditional web architecture. Hosting provider details are not disclosed. There is an opportunity to modernize the tech stack and improve accessibility compliance to reduce technical debt and enhance user experience.
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 lubella.pl. 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 lubella.pl.

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.