Security report for powerbee.co.uk
PowerBee Ltd · Energy · United Kingdom
Medium risk. 7 critical or high findings in Security headers, GDPR outside view and 2 other checks.
PowerBee Ltd operates a UK-based e-commerce website specializing in solar-powered lighting and garden products. The company targets homeowners and gardening enthusiasts seeking sustainable and battery-powered outdoor lighting solutions. Their market position is supported by a strong presence in the niche solar lighting retail sector, with a significant number of positive customer reviews indicating high customer satisfaction. The website offers a broad range of products including solar garden lights, solar water features, solar pumps, and related accessories, emphasizing quality and competitive pricing with free UK delivery and a 30-day return policy. Technically, the website is built on the Magento platform, leveraging modern JavaScript libraries such as jQuery, RequireJS, and Owl Carousel for enhanced user experience. It integrates Google Tag Manager and Stripe for analytics and payment processing respectively. The site demonstrates good mobile optimization and SEO practices, although accessibility features are basic. Performance is moderate, with lazy loading and cookie consent mechanisms implemented to improve user experience and compliance. From a security perspective, the site enforces HTTPS and uses invisible reCAPTCHA on forms to mitigate spam and abuse. Cookie consent is managed via a comprehensive mechanism aligned with GDPR requirements. However, some security headers like Content-Security-Policy and X-Frame-Options are missing, which could be improved to enhance protection against clickjacking and content injection attacks. No vulnerabilities or exposed sensitive data were detected in the analysis. Overall, the website presents a professional and trustworthy front for PowerBee Ltd's business operations. The main concern lies in the WHOIS data, which is incomplete due to domain naming rules issues with Nominet UK, raising questions about domain registration legitimacy. Despite this, the business information and website content appear consistent and cr…
Scanned
NIS2 and GDPR posture
- GDPR outside view
- 50/ 100 · Medium
- Checks completed
- 7of 7
NIS2 Art. 21(2)
- (a) Risk analysis and security policies: Not visible from outside
- (b) Incident handling: One indicator
- (c) Business continuity, backups and crisis management: Not visible from outside
- (d) Supply chain security: Not visible from outside
- (e) Secure acquisition, development and maintenance, including vulnerability handling: Partly checked
- (f) Assessing the effectiveness of security measures: Not visible from outside
- (g) Cyber hygiene and security training: Not visible from outside
- (h) Cryptography and encryption: Partly checked
- (i) HR security, access control and asset management: One indicator
- (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
7 findings rated critical or high. Fix these first.
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
- RFC 6797 §6.1.1
- Mozilla TLS: Mozilla Server Side TLS 6.0 intermediate: hsts_min_age 63072000
- NIS2 21(2)(h)
- IR 2024/2690 9.2(a): Implementing Regulation (EU) 2024/2690, Annex point 9.2(a): Cryptography
- NIST SC-8: NIST SP 800-53 Rev. 5 SC-8: Transmission Confidentiality and Integrity
- 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';…
- High
GDPR outside view
These are the privacy signals visitors and data protection authorities look for under GDPR.
- 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
- GDPR Art. 12
- GDPR Art. 13
- NIST PT-5: NIST SP 800-53 Rev. 5 PT-5: Privacy Notice
- 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
Third-party services without privacy policy
Detected services: Google Analytics, Facebook, Twitter, LinkedIn, Google APIs
What to do: Document all third-party data sharing in your privacy policy
- High
Need hands-on remediation? Email guard@offseq.com
Keep watching powerbee.co.uk
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. 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
- 57
- Security headers
- 45
- Email security
- 75
- DNS health
- 65
- Network security
- 20
- GDPR outside view
- 50
- 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
Security posture
Recommendations
- Implement Content-Security-Policy and X-Frame-Options HTTP headers to strengthen protection against content injection and clickjacking.
- Conduct a thorough review and correction of domain registration details with Nominet UK to resolve naming rules issues and ensure domain legitimacy.
- Enhance website accessibility features to meet WCAG standards, improving usability for all users and compliance with accessibility regulations.
- Publish formal security and incident response policies on the website to increase transparency and customer confidence.
- Regularly audit third-party scripts and dependencies for vulnerabilities and update them to maintain a secure technology stack.
Contact details published on the site
- Addresses
- Legal name
- PowerBee Ltd
- Registration number
- 060486578
Site observations
Automated reading of the public site. Ratings are indicative.
Business
- Company
- PowerBee Ltd
- Description
- Best Priced Lighting for Your Garden Powered by Solar & Battery, Shop Quality Solar Lights that Lasts Longer, Best Prices, Great Reviews, Free UK Delivery
- Key services
- Solar Garden Lights, Solar Water Features, Solar Pumps, Outdoor Lighting, Battery Operated Lights, Fairy and Festoon Lights, Pond Supplies
- Content quality
- good
- Branding
- consistent
Technology
- Stack
- Magento, jQuery, RequireJS, Google Tag Manager, Stripe Payments, Amasty Invisible Captcha, Magefan Cookie Consent, Owl Carousel, LazyLoad
- Frameworks
- Magento Commerce
- Platforms
- Web
- Performance
- moderate
- Mobile
- good
- Accessibility
- basic
- SEO
- good
Security
- Observed score
- 80/100
- Good practices seen
- HTTPS enforced
- Invisible reCAPTCHA on forms
- Cookie consent mechanism implemented
- No exposed sensitive data in HTML
Analytics and tracking
- Services
- Google Analytics (implied by GTM)
- Tracking level
- moderate
- Privacy practices
- good
Advertising
- Tracking pixels
- Trustpilot
- Marketing tools
- Trustpilot Widget
- Transparency
- good
Site quality
- Design
- good
- User experience
- good
- Content relevance
- good
- Navigation
- good
- Professionalism
- good
- Trustworthiness
- high
Key observations
- Website is a professional e-commerce platform selling solar lighting and garden products.
- Strong customer trust signals with many positive Google reviews.
- Uses Magento CMS with modern JavaScript libraries and Google Tag Manager.
- Implements GDPR-compliant cookie consent and privacy policies.
- WHOIS data is unavailable due to domain naming rules error, which is unusual and warrants further investigation.
- No signs of malware, phishing, or adult content detected.
- Security headers could be improved for enhanced protection.
Technical notes
Notes
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.
- MITRE CWE (opens in a new tab)4.20 (2026-04-30) · CWE Terms of Use (free use with attribution, © MITRE)
- OWASP Top 10:2025 (opens in a new tab)2025 (membership per CWE 4.20) · CC BY-SA 4.0
- MITRE CAPEC (opens in a new tab)3.9 (2023-01-24) · CAPEC Terms of Use (free use with attribution, © MITRE)
- OWASP ASVS (opens in a new tab)5.0.0 · CC BY-SA 4.0
- OWASP Web Security Testing Guide (opens in a new tab)latest (checklist.json, master) · CC BY-SA 4.0
- OWASP Secure Headers Project (opens in a new tab)2026-10-18 · Apache-2.0
- Mozilla Server Side TLS (intermediate) (opens in a new tab)6.0 · MPL-2.0
- NIST SP 800-53 Rev. 5 (OSCAL catalog) (opens in a new tab)5.2.0 · Public domain (US Government work)
- Directive (EU) 2022/2555 (NIS2) (opens in a new tab)OJ L 333, 27.12.2022 · EUR-Lex reuse under Commission Decision 2011/833/EU (© European Union)
- Commission Implementing Regulation (EU) 2024/2690 (opens in a new tab)OJ L, 18.10.2024 · EUR-Lex reuse under Commission Decision 2011/833/EU (© European Union)
- Regulation (EU) 2016/679 (GDPR) (opens in a new tab)OJ L 119, 4.5.2016 · EUR-Lex reuse under Commission Decision 2011/833/EU (© European Union)
- Directive 2002/58/EC (ePrivacy), consolidated (opens in a new tab)19.12.2009 · EUR-Lex reuse under Commission Decision 2011/833/EU (© European Union)
- RFC Editor metadata (opens in a new tab)per-RFC (obsolete RFCs rejected) · IETF Trust Legal Provisions (metadata only)
- NIST CSRC, W3C TR, IETF Datatracker, EDPB, EUR-Lex CELLAR and gesetze-bayern.de (opens in a new tab)per document · Titles and links only
- NIST NVD CVE API 2.0 (opens in a new tab)live records · Public domain (NVD); CVE® records © MITRE, free use
- W3C WCAG 2.2 (opens in a new tab)W3C Recommendation (wcag.json) · W3C Software and Document License
- ETSI EN 301 549 (opens in a new tab)V3.2.1 (2021-03), clause headings · Clause numbers and titles only (© ETSI)
- Directive (EU) 2019/882 (European Accessibility Act) (opens in a new tab)OJ L 151, 7.6.2019 · EUR-Lex reuse under Commission Decision 2011/833/EU (© European Union)
- Directive (EU) 2016/2102 (Web Accessibility Directive) (opens in a new tab)OJ L 327, 2.12.2016 · EUR-Lex reuse under Commission Decision 2011/833/EU (© European Union)
Retrieved 2026-10-25
Feedback on this report
Rate this report, add an optional comment, and tell us if you want a security specialist to follow up.
Reviews of this site
Share your experience with powerbee.co.uk. Every review is verified by email and published after moderation.
Community rating
No published reviews yet. Be the first to review powerbee.co.uk.