Security report for enersys.com

Name: Dark-web exposure summary for enersys.com
Creator: OffSeq Breach

EnerSys · Energy · N/a

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

Security score

48/100

Risk levelHigh

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

EnerSys is a global leader in stored energy and power solutions, serving a broad range of industrial and mission-critical sectors including transportation, logistics, communications, aerospace, defense, medical, and energy utilities. The company offers a comprehensive portfolio of batteries, chargers, monitoring systems, energy systems, and maintenance services, positioning itself as a full turnkey power solutions provider. The website reflects a mature digital presence with professional design, clear navigation, and extensive content supporting its market leadership and sustainability commitments. Technically, the site leverages modern analytics and consent management tools, is built on Episerver CMS, and demonstrates good performance and accessibility. Security posture is strong with HTTPS enforcement and cookie consent mechanisms, though explicit security headers could be more visible. No critical vulnerabilities or exposed sensitive data were detected. Overall, the domain registration and WHOIS data align well with the company's claims, supporting legitimacy and trustworthiness.

Scanned

NIS2 and GDPR posture

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

16 findings rated critical or high. Fix these first.

GDPR outside view
These are the privacy signals visitors and data protection authorities look for under GDPR.
- Critical
  No HTTPS encryption
  GDPR requires appropriate security measures for personal data
  What to do: Implement SSL/TLS certificate for HTTPS
  References
  - CWE-319
  - OWASP A04:2025
  - ASVS V12.2.1
  - NIS2 21(2)(h)
  - IR 2024/2690 9.2(a): Implementing Regulation (EU) 2024/2690, Annex point 9.2(a): Cryptography
  - GDPR Art. 32(1)(a)
  - NIST SC-8: NIST SP 800-53 Rev. 5 SC-8: Transmission Confidentiality and Integrity
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
  No HTTPS Encryption
  Website does not use HTTPS encryption, making all data transmission vulnerable to interception
  What to do: Implement SSL/TLS certificate and redirect all HTTP traffic to HTTPS
  References
  - CWE-319
  - OWASP A04:2025
  - ASVS V12.2.1
  - NIS2 21(2)(h)
  - IR 2024/2690 9.2(a): Implementing Regulation (EU) 2024/2690, Annex point 9.2(a): Cryptography
  - GDPR Art. 32(1)(a)
  - NIST SC-8: NIST SP 800-53 Rev. 5 SC-8: Transmission Confidentiality and Integrity
Network security
Services reachable from the internet are the first thing attackers probe. Anything open that does not need to be should be closed.
- Critical
  Critical Service Exposed: Telnet
  Port 23 (Telnet) is publicly accessible - Telnet - Unencrypted remote access
  What to do: Immediately restrict access to Telnet using firewall or VPN
  References
  - NIS2 21(2)(e)
  - IR 2024/2690 6.7.2(f): Implementing Regulation (EU) 2024/2690, Annex point 6.7.2(f): Network security
  - NIST CM-7: NIST SP 800-53 Rev. 5 CM-7: Least Functionality
  - NIST SC-7: NIST SP 800-53 Rev. 5 SC-7: Boundary Protection
- Critical
  Critical Service Exposed: SMB
  Port 445 (SMB) is publicly accessible - SMB - Windows file sharing, high risk
  What to do: Immediately restrict access to SMB using firewall or VPN
  References
  - NIS2 21(2)(e)
  - IR 2024/2690 6.7.2(f): Implementing Regulation (EU) 2024/2690, Annex point 6.7.2(f): Network security
  - NIST CM-7: NIST SP 800-53 Rev. 5 CM-7: Least Functionality
  - NIST SC-7: NIST SP 800-53 Rev. 5 SC-7: Boundary Protection
- Critical
  Critical Service Exposed: MSSQL
  Port 1433 (MSSQL) is publicly accessible - MSSQL - Database server
  What to do: Immediately restrict access to MSSQL using firewall or VPN
  References
  - NIS2 21(2)(e)
  - IR 2024/2690 6.7.2(f): Implementing Regulation (EU) 2024/2690, Annex point 6.7.2(f): Network security
  - NIST CM-7: NIST SP 800-53 Rev. 5 CM-7: Least Functionality
  - NIST SC-7: NIST SP 800-53 Rev. 5 SC-7: Boundary Protection
- Critical
  Critical Service Exposed: Oracle
  Port 1521 (Oracle) is publicly accessible - Oracle - Database server
  What to do: Immediately restrict access to Oracle using firewall or VPN
  References
  - NIS2 21(2)(e)
  - IR 2024/2690 6.7.2(f): Implementing Regulation (EU) 2024/2690, Annex point 6.7.2(f): Network security
  - NIST CM-7: NIST SP 800-53 Rev. 5 CM-7: Least Functionality
  - NIST SC-7: NIST SP 800-53 Rev. 5 SC-7: Boundary Protection
- Critical
  Critical Service Exposed: MySQL
  Port 3306 (MySQL) is publicly accessible - MySQL - Database server
  What to do: Immediately restrict access to MySQL using firewall or VPN
  References
  - NIS2 21(2)(e)
  - IR 2024/2690 6.7.2(f): Implementing Regulation (EU) 2024/2690, Annex point 6.7.2(f): Network security
  - NIST CM-7: NIST SP 800-53 Rev. 5 CM-7: Least Functionality
  - NIST SC-7: NIST SP 800-53 Rev. 5 SC-7: Boundary Protection
- Critical
  Critical Service Exposed: RDP
  Port 3389 (RDP) is publicly accessible - RDP - Remote Desktop, prime ransomware target
  What to do: Immediately restrict access to RDP using firewall or VPN
  References
  - NIS2 21(2)(e)
  - IR 2024/2690 6.7.2(f): Implementing Regulation (EU) 2024/2690, Annex point 6.7.2(f): Network security
  - NIST CM-7: NIST SP 800-53 Rev. 5 CM-7: Least Functionality
  - NIST SC-7: NIST SP 800-53 Rev. 5 SC-7: Boundary Protection
- Critical
  Critical Service Exposed: PostgreSQL
  Port 5432 (PostgreSQL) is publicly accessible - PostgreSQL - Database server
  What to do: Immediately restrict access to PostgreSQL using firewall or VPN
  References
  - NIS2 21(2)(e)
  - IR 2024/2690 6.7.2(f): Implementing Regulation (EU) 2024/2690, Annex point 6.7.2(f): Network security
  - NIST CM-7: NIST SP 800-53 Rev. 5 CM-7: Least Functionality
  - NIST SC-7: NIST SP 800-53 Rev. 5 SC-7: Boundary Protection
- Critical
  Critical Service Exposed: Redis
  Port 6379 (Redis) is publicly accessible - Redis - In-memory database
  What to do: Immediately restrict access to Redis using firewall or VPN
  References
  - NIS2 21(2)(e)
  - IR 2024/2690 6.7.2(f): Implementing Regulation (EU) 2024/2690, Annex point 6.7.2(f): Network security
  - NIST CM-7: NIST SP 800-53 Rev. 5 CM-7: Least Functionality
  - NIST SC-7: NIST SP 800-53 Rev. 5 SC-7: Boundary Protection
- Critical
  Critical Service Exposed: MongoDB
  Port 27017 (MongoDB) is publicly accessible - MongoDB - NoSQL database
  What to do: Immediately restrict access to MongoDB using firewall or VPN
  References
  - NIS2 21(2)(e)
  - IR 2024/2690 6.7.2(f): Implementing Regulation (EU) 2024/2690, Annex point 6.7.2(f): Network security
  - NIST CM-7: NIST SP 800-53 Rev. 5 CM-7: Least Functionality
  - NIST SC-7: NIST SP 800-53 Rev. 5 SC-7: Boundary Protection
- High
  High-Risk Service Exposed: FTP
  Port 21 (FTP) is publicly accessible - FTP - Often unencrypted file transfer
  What to do: Consider restricting access to FTP or implementing strong authentication
  References
  - NIS2 21(2)(e)
  - IR 2024/2690 6.7.2(f): Implementing Regulation (EU) 2024/2690, Annex point 6.7.2(f): Network security
  - NIST CM-7: NIST SP 800-53 Rev. 5 CM-7: Least Functionality
  - NIST SC-7: NIST SP 800-53 Rev. 5 SC-7: Boundary Protection
- High
  High-Risk Service Exposed: RPC
  Port 135 (RPC) is publicly accessible - RPC - Windows RPC endpoint
  What to do: Consider restricting access to RPC or implementing strong authentication
  References
  - NIS2 21(2)(e)
  - IR 2024/2690 6.7.2(f): Implementing Regulation (EU) 2024/2690, Annex point 6.7.2(f): Network security
  - NIST CM-7: NIST SP 800-53 Rev. 5 CM-7: Least Functionality
  - NIST SC-7: NIST SP 800-53 Rev. 5 SC-7: Boundary Protection
- High
  High-Risk Service Exposed: NetBIOS
  Port 139 (NetBIOS) is publicly accessible - NetBIOS - Windows file sharing
  What to do: Consider restricting access to NetBIOS or implementing strong authentication
  References
  - NIS2 21(2)(e)
  - IR 2024/2690 6.7.2(f): Implementing Regulation (EU) 2024/2690, Annex point 6.7.2(f): Network security
  - NIST CM-7: NIST SP 800-53 Rev. 5 CM-7: Least Functionality
  - NIST SC-7: NIST SP 800-53 Rev. 5 SC-7: Boundary Protection
- High
  High-Risk Service Exposed: Elasticsearch
  Port 9200 (Elasticsearch) is publicly accessible - Elasticsearch - Search engine
  What to do: Consider restricting access to Elasticsearch or implementing strong authentication
  References
  - NIS2 21(2)(e)
  - IR 2024/2690 6.7.2(f): Implementing Regulation (EU) 2024/2690, Annex point 6.7.2(f): Network security
  - NIST CM-7: NIST SP 800-53 Rev. 5 CM-7: Least Functionality
  - NIST SC-7: NIST SP 800-53 Rev. 5 SC-7: Boundary Protection
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 Content-Security-Policy header
  Controls resources the browser is allowed to load
  What to do: Implement a Content-Security-Policy appropriate for your application
  References
  - 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 enersys.com

This scan found 27 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: 60
Email security: 80
DNS health: 85
Network security: 0
GDPR outside view: 63
Average: 48

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 · found on this site
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 enersys.com, from OffSeq Breach.

Total records: 167
Employees: 5
Customers: 89
Third parties: 73
Weak passwords: 8%

Latest record dated 2026-05-29 · 6 subdomains 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 enersys.com.

Select it in the checkout above.

Masked preview

–bsp.enersys.com2026-05-29
–webmail.enersys.com2025-07-28
–webmail.enersys.com2025-07-20
–webmail.enersys.com2025-07-19
–bsp.enersys.com2025-04-16

Breach keeps ingesting new leaks, so these numbers can grow between scans.

Open in Breach Monitor on Breach

Technical appendix

Business context, site observations and technical notes gathered during the scan, and the standards behind each reference.

Business context

Business profile

EnerSys operates as an enterprise-level B2B company with a global footprint, evidenced by multiple subsidiary brands and dedicated investor and career portals. Its market positioning as a global leader in energy storage is supported by a diverse product and service offering tailored to industrial and mission-critical applications. The company emphasizes sustainability, ethics, and compliance, which are prominently featured on the website. The presence of multiple industry-specific sections and resources indicates a strategic focus on targeted customer segments and thought leadership. The partnership ecosystem includes several subsidiary brands, enhancing market reach and product diversity. The business model centers on providing integrated energy solutions with strong after-sales support and maintenance services.

Security posture

The website demonstrates a mature security posture with mandatory HTTPS, use of cookie consent management via OneTrust, and integration of security analytics through Azure Application Insights. No exposed emails or phone numbers reduce the risk of spam or social engineering. The absence of explicit security policy or incident response contact information is a gap. Security headers are not explicitly visible in the HTML but may be configured at the server level. No vulnerable or outdated libraries were detected in the provided content. Overall, the site follows best practices for privacy compliance and user consent but could improve transparency on security policies and incident handling.

Recommendations

Implement and publicly disclose a dedicated security policy page including incident response procedures and contact channels.
Ensure all recommended security headers (X-Frame-Options, X-Content-Type-Options, Content-Security-Policy) are configured and verifiable.
Regularly audit third-party scripts and dependencies for vulnerabilities and update as needed.
Enhance transparency by providing direct contact information for data protection officers or privacy inquiries.
Maintain and update cookie consent mechanisms to comply with evolving privacy regulations.

Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company: EnerSys
Description: EnerSys is a global leader in stored energy solutions, delivering innovative batteries, chargers, and power systems for industrial and mission-critical applications.
Key services: Batteries, Battery Chargers, Monitoring and Fleet Management, Energy Systems, Maintenance and Aftermarket Services
Content quality: excellent
Branding: consistent

Technology

Stack: Google Tag Manager, Azure Application Insights, OneTrust Cookie Consent, Optimizely
Frameworks: Bootstrap (implied by classes), jQuery (likely via bundles/js/vendors)
Performance: moderate
Mobile: good
Accessibility: good
SEO: good

Security

Observed score

85/100

Good practices seen

HTTPS enforced
Cookie consent with opt-in/out
No exposed emails or phone numbers in HTML
Use of security analytics (Azure App Insights)

Analytics and tracking

Services: Google Tag Manager, Azure Application Insights, Optimizely
Tracking level: moderate
Privacy practices: good

Advertising

Tracking pixels: Azure Application Insights, Optimizely
Marketing tools: Optimizely
Transparency: good

Site quality

Design: excellent
User experience: excellent
Content relevance: excellent
Navigation: excellent
Professionalism: excellent
Trustworthiness: high

Key observations

Website is professionally designed with comprehensive content and clear navigation.
Strong focus on sustainability, ethics, and compliance.
Use of modern analytics and consent management tools.
No exposed sensitive data or obvious security vulnerabilities in HTML content.
Multiple subsidiary and partner brands linked, indicating a large enterprise structure.

Technical notes

Notes

The website is built on Episerver CMS, utilizing modern JavaScript libraries and frameworks such as Google Tag Manager, Azure Application Insights, OneTrust for cookie consent, and Optimizely for experimentation. The site is mobile optimized with responsive design and accessibility features. Performance is moderate with lazy loading of images and asynchronous script loading. SEO is supported by proper meta tags, Open Graph tags, and hreflang attributes for multilingual support. The technical infrastructure supports a robust user experience but could benefit from enhanced security header visibility and performance optimizations.

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.

OWASP Top 10:2025 (opens in a new tab)2025 (membership per CWE 4.20) · CC BY-SA 4.0
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
W3C WCAG 2.2 (opens in a new tab)W3C Recommendation (wcag.json) · W3C Software and Document License
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.

Priority findings

GDPR outside view

No HTTPS encryption

SSL/TLS

No HTTPS Encryption

Network security

Critical Service Exposed: Telnet

Critical Service Exposed: SMB

Critical Service Exposed: MSSQL

Critical Service Exposed: Oracle

Critical Service Exposed: MySQL

Critical Service Exposed: RDP

Critical Service Exposed: PostgreSQL

Critical Service Exposed: Redis

Critical Service Exposed: MongoDB

High-Risk Service Exposed: FTP

High-Risk Service Exposed: RPC

High-Risk Service Exposed: NetBIOS

High-Risk Service Exposed: Elasticsearch

Security headers

Missing Content-Security-Policy header

Keep watching enersys.com

Daily monitoring

Full report

Results by check

Security headers, 4 findings, score 60/100

SSL/TLS, 1 finding, score 0/100

Email security, 4 findings, score 80/100

DNS health, 2 findings, score 85/100

Network security, 14 findings, score 0/100

GDPR outside view, 2 findings, score 63/100

NIS2 outside view, Earlier method, rescan for details · not counted in the security score–