Skip to main content

Security report for pureko.pl

Pureko · Manufacturing · Poland

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

Security score

55/100

Risk levelMedium

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

Pureko is a Polish manufacturing company specializing in the production of PUR foams and fluffy nonwoven materials. The website serves primarily as a business presence targeting industrial clients interested in these products. The site is built on WordPress using the Divi theme, with a basic but functional design and moderate mobile optimization. However, the website lacks critical privacy and cookie policies, contact information, and security policies, which limits its compliance and trustworthiness from a security and privacy perspective. No advanced security headers or incident response contacts are published, indicating a low security maturity level. Overall, the site is safe and business-focused but requires significant improvements in privacy compliance and security posture to meet modern standards.

Scanned

NIS2 and GDPR posture

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

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 pureko.pl

This scan found 26 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
32
Security headers
15
Email security
70
DNS health
75
Network security
100
GDPR outside view
40
Average
55

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 operates in the manufacturing sector, focusing on foam and nonwoven products, likely serving B2B clients in Poland and possibly neighboring regions. The business model is manufacturing and direct sales, with no evident e-commerce or online transaction capabilities on the site. The market position appears to be a specialized producer in its niche. The website content is basic, with limited trust signals such as certifications or testimonials. No partnerships or subsidiaries are indicated. The lack of contact details and policies may hinder customer trust and regulatory compliance.

Security posture

The website currently exhibits a low security posture. It lacks HTTPS security headers, privacy and cookie policies, and incident response information. No vulnerability disclosure or security.txt files are present. The absence of security best practices and contact channels for security incidents suggests limited preparedness for security events. There is no evidence of tracking or analytics scripts, which reduces privacy risks but also limits business intelligence. The site should implement HTTPS, security headers, privacy policies, and incident response contacts to improve its security maturity and compliance.

Recommendations

  1. Implement HTTPS with a valid SSL certificate and enforce secure connections.
  2. Publish comprehensive privacy and cookie policies to comply with GDPR and other regulations.
  3. Add clear contact information including company emails and phone numbers for customer and security incident reporting.
  4. Implement security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options.
  5. Create a vulnerability disclosure policy and publish a security.txt file to facilitate responsible reporting.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Pureko
Description
Producer of PUR foams and fluffy nonwovens
Key services
production of PUR foams, production of fluffy nonwovens
Content quality
basic
Branding
moderate

Technology

Stack
HTML5, CSS3, JavaScript, Google Fonts
Frameworks
Divi Theme
Performance
moderate
Mobile
good
Accessibility
basic
SEO
basic

Analytics and tracking

Tracking level
minimal
Privacy practices
poor

Advertising

Transparency
poor

Site quality

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

Key observations

  1. Website is a small manufacturing company site with basic content and structure.
  2. No privacy, cookie, or terms of service policies found.
  3. No explicit contact emails or phone numbers found in the HTML content.
  4. No security policies or incident response information published.
  5. Uses WordPress with Divi theme and Google Fonts.
  6. No analytics or tracking scripts detected.
  7. No advertising or affiliate programs detected.
  8. No security headers or advanced security measures detected.
  9. Content is safe and business-focused.
Technical notes

Notes

The website uses WordPress CMS with the Divi theme, a popular and flexible framework. It loads Google Fonts externally and uses standard HTML5, CSS3, and JavaScript. The site appears moderately optimized for mobile devices but lacks advanced SEO and accessibility features. No analytics or marketing tools are detected, indicating minimal tracking. Performance is moderate, with no explicit indicators of slow loading but also no advanced optimization. The technical stack is standard but could benefit from modernization and enhanced security configurations.
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 pureko.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 pureko.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.