HubEnergy · Energy · Latvia
High risk. 10 critical or high findings in GDPR outside view, Network security and 2 other checks.
HubEnergy operates the website akum.lv, a specialized e-commerce platform focused on selling various types of batteries including AGM, LiFePO4 lithium, GEL batteries, and chargers. The company targets retail and wholesale customers primarily in Latvia, offering a range of energy storage solutions. The website is multilingual, supporting Latvian, Russian, and English, enhancing accessibility for a broader audience. The business model centers on direct online sales supported by clear contact information and customer service channels. HubEnergy appears to be a small-sized enterprise founded around 2016, with a consistent brand presence and a professional online storefront. Technically, the website is built on WordPress with WooCommerce, utilizing popular plugins such as Yoast SEO, RevSlider, and WPBakery Page Builder. The site demonstrates good SEO practices, mobile responsiveness, and moderate performance. Security measures include HTTPS enforcement and a cookie consent mechanism via CookieYes, though no explicit security policy or incident response contacts are published. The absence of WHOIS data limits full verification of domain legitimacy, but the website content and structure suggest a legitimate business operation. Security posture is solid with standard security headers and no visible vulnerabilities or exposed sensitive data. Privacy compliance is well addressed with comprehensive privacy and cookie policies, including GDPR compliance indicators. However, the site could improve by adding a security.txt file and explicit incident response contact information. Overall, the website presents a trustworthy and professional image with room for enhancements in security transparency and accessibility. The risk assessment is moderate-low given the lack of WHOIS data and some missing security policy details. Strategic recommendations include implementing vulnerability disclosure mechanisms, enhancing accessibility, and maintaining up-to-date software to mitigate potential risks.
Scanned
NIS2 Art. 21(2)
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.
10 findings rated critical or high. Fix these first.
These are the privacy signals visitors and data protection authorities look for under GDPR.
EU businesses are subject to strict GDPR requirements
What to do: Implement comprehensive GDPR compliance including privacy policy, cookie consent, and data protection measures
GDPR requires a clear and accessible privacy policy
What to do: Add a comprehensive privacy policy page and link to it prominently
Detected services: Google APIs
What to do: Document all third-party data sharing in your privacy policy
Services reachable from the internet are the first thing attackers probe. Anything open that does not need to be should be closed.
Port 3306 (MySQL) is publicly accessible - MySQL - Database server
What to do: Immediately restrict access to MySQL using firewall or VPN
Port 21 (FTP) is publicly accessible - FTP - Often unencrypted file transfer
What to do: Consider restricting access to FTP or implementing strong authentication
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.
Forces HTTPS connections
What to do: Add "Strict-Transport-Security: max-age=31536000; includeSubDomains; preload"
Prevents clickjacking attacks
What to do: Add "X-Frame-Options: DENY" or "X-Frame-Options: SAMEORIGIN"
Controls resources the browser is allowed to load
What to do: Implement a Content-Security-Policy appropriate for your application
Need hands-on remediation? Email guard@offseq.com
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.
€25per month
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.
€39.90one-time
Prices incl. 21% VAT. Secure checkout by Mollie; sold by SEQ SIA, Latvia.
Each check with its score, findings and the evidence it collected.
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
Not counted
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.
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
Leaked credentials and lookalike domains from OffSeq Breach. The counts are free; the detailed lists are paid add-ons.
Leaked records that mention akum.lv, from OffSeq Breach.
1 subdomain affected
See the 10 newest leaked credentials
A one-off add-on to this report that lists the most recent identifier and password pairs OffSeq Breach holds for akum.lv.
Select it in the checkout above.
Breach keeps ingesting new leaks, so these numbers can grow between scans.
Business context, site observations and technical notes gathered during the scan, and the standards behind each reference.
Automated reading of the public site. Ratings are indicative.
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
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 akum.lv. Every review is verified by email and published after moderation.
Community rating
No published reviews yet. Be the first to review akum.lv.