Skip to main content

Security report for plentyone.com

PlentyONE GmbH · E-commerce · Germany

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

Security score

67/100

Risk levelMedium

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

PlentyONE GmbH operates a leading cloud-native all-in-one e-commerce ERP platform that connects brands, manufacturers, and retailers to over 150 global marketplaces. The company offers a scalable and flexible SaaS solution complemented by strategic consulting and operational support services. Their market position is strong, with over 55,000 users and significant transaction volumes, positioning them as a key player in the e-commerce sector. Technically, the website is built on HubSpot CMS, leveraging AWS hosting and Cloudflare CDN, with extensive use of marketing and analytics tools such as Google Analytics, HubSpot, and Cookiebot for privacy compliance. Security posture is generally good with modern TLS protocols and OCSP stapling, but improvements are recommended in HTTP security headers and DNS security. The website demonstrates excellent design, content quality, and user experience, supported by comprehensive cookie consent mechanisms and privacy policies. Overall, PlentyONE shows a mature digital presence with a strong focus on compliance and customer engagement.

Scanned

NIS2 and GDPR posture

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

5 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 X-Frame-Options header

      Prevents clickjacking attacks

      What to do: Add "X-Frame-Options: DENY" or "X-Frame-Options: SAMEORIGIN"

  2. GDPR outside view

    These are the privacy signals visitors and data protection authorities look for under GDPR.

    • 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

    • High

      No Cookie Consent Banner found

      GDPR requires explicit consent for non-essential cookies

      What to do: Implement a cookie consent banner that appears on first visit

  3. 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 SSL Key Length

      SSL certificate uses 256-bit key, which is considered weak

      What to do: Use at least 2048-bit RSA or 256-bit ECC key

      • CWE-326
      • OWASP A04:2025
      • Mozilla TLS: Mozilla Server Side TLS 6.0 intermediate: rsa_key_size 2048
  4. DNS health

    DNS sends visitors and email to the right servers. Misconfigured records can cause outages or let someone redirect your traffic.

    • High

      Unregistered MX Record

      MX record points to unregistered domain: ms37258694.msv1.invalid.plentyone.com

      What to do: Remove or fix MX record pointing to unregistered domain

      • RFC 5321 §5.1
      • NIS2 21(2)(i)
      • IR 2024/2690 12.4: Implementing Regulation (EU) 2024/2690, Annex point 12.4: Asset inventory
      • NIST CM-8: NIST SP 800-53 Rev. 5 CM-8: System Component Inventory

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

Keep watching plentyone.com

This scan found 23 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
72
Security headers
45
Email security
70
DNS health
70
Network security
100
GDPR outside view
43
Average
67

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 plentyone.com, from OffSeq Breach.

No leaked records found

Breach holds no records for plentyone.com 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

PlentyONE targets a broad audience including small to large businesses seeking scalable e-commerce solutions. Their business model combines SaaS platform offerings with personalized consulting and growth services, enabling multiple revenue streams. The company emphasizes partnerships with marketplaces like Amazon, Zalando, and OTTO, and integrates with major marketing platforms such as Google and Facebook. Growth indicators include high order volumes and GMV, supported by a strong partner ecosystem and customer testimonials. Strategic observations highlight their focus on internationalization, multichannel commerce, and cloud-native technology to maintain competitive advantage.

Security posture

The security maturity level of PlentyONE's website is good, with support for TLS 1.3 and 1.2, OCSP stapling enabled, and no critical SSL vulnerabilities detected. However, the absence of HSTS, DNSSEC, and CAA records indicates areas for improvement in hardening the security posture. The site employs a comprehensive cookie consent mechanism aligned with GDPR requirements, demonstrating strong data protection practices. Incident response and vulnerability disclosure policies are not publicly found, which could be a compliance gap. Overall, the security culture appears focused on compliance and user privacy, but could benefit from enhanced transparency and technical controls.

Recommendations

  1. Enable HTTP Strict Transport Security (HSTS) with includeSubDomains and preload to enforce HTTPS.
  2. Implement DNSSEC to protect against DNS spoofing and improve domain security.
  3. Add CAA DNS records to restrict which certificate authorities can issue certificates for the domain.
  4. Publish a vulnerability disclosure policy and security.txt file to improve transparency and incident handling.
  5. Enhance incident response readiness by providing clear security contact channels and procedures.
Technical notes

Notes

The website infrastructure is modern, leveraging HubSpot CMS for content management and forms, AWS for cloud hosting, and Cloudflare for CDN and security. The tech stack includes jQuery, Swiper.js for UI components, and extensive third-party integrations for analytics and marketing. Performance is currently slow with a large page size and high resource count, suggesting optimization opportunities. Mobile optimization and accessibility are good, supporting a broad user base. Technical risks include missing DNSSEC and HSTS, which could impact security and trust. Modernization efforts should focus on performance improvements 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 plentyone.com. 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 plentyone.com.

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.