Skip to main content

Security report for hbh.sh

HBH · Technology · United Kingdom

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

Security score

69/100

Risk levelMedium

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

HBH is a well-established non-profit cybersecurity education community founded in 2003, offering a wide range of simulated challenges, virtual labs, forums, and educational content aimed at individuals and teams interested in learning about hacking techniques and defensive measures. The platform is supported by a large active membership and funded through advertising and sponsorships, with transparent reinvestment of funds into the project. Technically, the website employs modern frontend technologies including Bootstrap, jQuery, FontAwesome, and Google services such as reCAPTCHA and Tag Manager, hosted via Cloudflare for performance and security. The site is mobile optimized and provides a good user experience with clear navigation and professional design. Security posture is solid with HTTPS enforced, CSRF tokens on forms, and use of Google reCAPTCHA; however, DNSSEC is not enabled and some security headers are missing. Privacy compliance is partially met with a comprehensive privacy policy and terms of service, but lacks a cookie consent mechanism despite the use of ads and tracking scripts. No direct company contact emails or phone numbers are published, relying on a contact form instead. Overall, the website is trustworthy and professional, with room for improvement in security and privacy transparency.

Scanned

NIS2 and GDPR posture

GDPR outside view
53/ 100 · Medium
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"

    • 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';…
  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

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

Keep watching hbh.sh

This scan found 21 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
75
Security headers
40
Email security
70
DNS health
75
Network security
100
GDPR outside view
53
Average
69

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 hbh.sh, from OffSeq Breach.

Total records
968
Employees
0
Customers
968
Third parties
0
Weak passwords
7%

2 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 hbh.sh.

Select it in the checkout above.

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

Technical appendix

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

Business context

Business profile

HBH occupies a niche in the cybersecurity education sector as a non-profit community platform with a long history and a large active user base. Its business model relies on community support, advertising, and sponsorships, reinvesting all income back into the project. The platform targets a broad audience including individuals, educational institutions, companies, and hacker groups, offering collaborative features and a variety of learning resources. The presence of active forums, numerous challenges, and ongoing development of labs and courses indicates a growth-oriented and engaged ecosystem. Partnerships appear limited to social media and advertising networks, with no detected subsidiaries or parent companies. The transparent approach to funding and public financial disclosures enhances credibility and trust within the community.

Security posture

The website demonstrates a mature security posture with HTTPS enforced and clientTransferProhibited domain status to prevent unauthorized transfers. Use of Google reCAPTCHA and CSRF tokens on forms mitigates automated abuse and cross-site request forgery risks. However, the absence of DNSSEC reduces DNS security, and missing security headers like Content-Security-Policy and X-Frame-Options could expose the site to certain web-based attacks. No explicit security policy, vulnerability disclosure, or incident response information is published, which limits transparency and readiness perception. Privacy compliance is partial, lacking cookie consent despite tracking and advertising. Overall, the security posture is good but could be enhanced by implementing DNSSEC, additional headers, and publishing security policies.

Recommendations

  1. Enable DNSSEC on the domain to improve DNS integrity and security.
  2. Publish a formal security policy and vulnerability disclosure guidelines to enhance transparency and community trust.
  3. Implement additional HTTP security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options.
  4. Add a cookie consent mechanism to comply fully with GDPR and improve privacy transparency.
  5. Consider publishing direct contact emails for security and incident response to improve communication channels.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
HBH
Description
HBH is a non-profit community designed to inform and teach the various methods and tactics used by malicious hackers to access protected systems. Founded in 2003, it offers simulated challenges, virtual machine based labs, forums, articles, and a code bank to educate users on cybersecurity.
Key services
Simulated cybersecurity challenges, Virtual machine based labs, Forums and articles for information sharing, Code bank for sharing code snippets, Teams functionality for collaborative learning, Academy courses in development
Content quality
good
Branding
consistent

Technology

Stack
Bootstrap, jQuery, FontAwesome, Google reCAPTCHA, Google Tag Manager, Chart.js, TypeIt.js
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
75/100
Good practices seen
  • HTTPS enforced
  • Use of Google reCAPTCHA on contact form
  • CSRF token present in forms
  • ClientTransferProhibited domain status

Analytics and tracking

Services
Google Tag Manager, Cloudflare Insights
Tracking level
moderate
Privacy practices
basic

Advertising

Ad networks
Carbon Ads, Google Adsense
Tracking pixels
Cloudflare Insights
Transparency
basic

Site quality

Design
good
User experience
good
Content relevance
good
Navigation
good
Professionalism
good
Trustworthiness
high

Key observations

  1. Website is a well-established non-profit cybersecurity education platform.
  2. Content is rich with community engagement metrics and educational resources.
  3. No direct company contact emails or phone numbers found; contact via form only.
  4. No cookie consent banner detected despite use of ads and tracking scripts.
  5. Security posture is good but could be improved with DNSSEC and additional headers.
  6. No explicit vulnerability disclosure or incident response information published.
  7. Use of modern frontend technologies and analytics tools.
  8. Social media presence on Twitter, YouTube, and GitHub.
Technical notes

Notes

The website uses a modern and widely adopted technology stack including Bootstrap for responsive design, jQuery for DOM manipulation, FontAwesome for icons, and Google services for analytics and bot protection. Hosting via Cloudflare provides performance benefits and some security features. The site loads external scripts asynchronously and defers non-critical JavaScript to optimize performance. Accessibility is basic but functional, with room for improvement. SEO is supported by proper meta tags and Open Graph data. No CMS is detected, indicating a custom-built platform. Overall, the technical infrastructure is solid with moderate performance and good mobile optimization, though some technical debt may exist in missing advanced accessibility features and security headers.
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 hbh.sh. 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 hbh.sh.

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.