Skip to main content

Security report for hackint.org

Chaos Computer Club Darmstadt e.V. · Technology · Germany

Medium risk. 6 critical or high findings in Security headers and GDPR outside view.

Security score

56/100

Risk levelMedium

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

hackint.org operates as a specialized communication network primarily serving the hacker community, offering IRC-based services compliant with IRCv3 standards, along with modern communication transports such as Matrix, Tor, and DN42. The network is managed by Chaos Computer Club Darmstadt e.V., a German non-profit organization, reflecting a community-driven, non-commercial model. The website provides detailed documentation, news updates, and support resources, positioning itself as a niche but trusted platform within the hacker and technology enthusiast ecosystem. From a technical perspective, the site employs standard web technologies including HTML5 and CSS3, and supports modern communication protocols. Hosting is provided by http.net Internet GmbH, a reputable German hosting provider. The site demonstrates good mobile optimization and clear navigation, though accessibility and SEO optimizations are basic. Security-wise, the domain benefits from a long registration history and transfer protection, and TLS 1.3 support is implemented. However, DNSSEC is not enabled, and no security headers or explicit security policies are published, indicating room for improvement in hardening the web presence. Security posture is moderate; while no critical vulnerabilities or malware indicators are present, the absence of privacy and cookie policies, security headers, and incident response information limits compliance and transparency. No contact emails or phone numbers are publicly listed, which may hinder user support and trust. Overall, the site is safe, professional, and trustworthy but would benefit from enhanced security and privacy disclosures to align with best practices and regulatory expectations.

Scanned

NIS2 and GDPR posture

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

6 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 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

    • 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

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

Keep watching hackint.org

This scan found 22 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
85
Security headers
30
Email security
70
DNS health
75
Network security
40
GDPR outside view
35
Average
56

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 hackint.org, from OffSeq Breach.

Total records
16
Employees
0
Customers
16
Third parties
0
Weak passwords
38%

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 hackint.org.

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

hackint.org is positioned as a community-centric technology network focused on hacker culture communication. Its competitive advantage lies in providing specialized IRC and modern transport protocols bridging, appealing to a niche audience of hackers and tech enthusiasts. The business model is non-commercial, supported by a registered non-profit entity, which aligns with its open and community-driven ethos. Revenue streams are not evident, suggesting volunteer or organizational funding. The target customers are technically proficient users seeking decentralized and privacy-conscious communication channels. Growth indicators include ongoing updates and protocol support enhancements. The partnership ecosystem includes open-source projects and related hacker networks, though no formal commercial partnerships are identified. Strategic observations highlight the importance of maintaining technical modernization and improving compliance to sustain trust and community engagement.

Security posture

The current security maturity level of hackint.org is moderate. The domain is secured with TLS 1.3 and transfer protection, and the long domain age supports legitimacy. However, the lack of DNSSEC, security headers, and published security policies represents gaps in defense-in-depth and transparency. No vulnerability disclosure or incident response contacts are provided, limiting the ability to manage security incidents effectively. Data protection practices are not explicitly documented, and GDPR compliance indicators are absent. The security culture appears informal, consistent with a community network rather than a commercial enterprise. Business impact of these gaps is moderate, primarily affecting user trust and regulatory compliance rather than immediate operational risk.

Recommendations

  1. Enable DNSSEC on the domain to improve DNS security and integrity.
  2. Implement and publish comprehensive privacy and cookie policies to enhance compliance and user trust.
  3. Add security headers such as Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security to harden the web application.
  4. Publish a security policy and incident response contact information, including abuse and security email addresses.
  5. Consider establishing a vulnerability disclosure program or security.txt file to facilitate responsible reporting.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Chaos Computer Club Darmstadt e.V.
Description
hackint is a communication network for the hacker community, providing IRCv3.1 and partial IRCv3.2 compliant services and various communication transports.
Key services
IRC network services, Webchat, Matrix bridging, Tor transport, DN42 transport, Jabber/XMPP transport, Documentation and support
Content quality
good
Branding
consistent

Technology

Stack
HTML5, CSS3, IRCv3.1, IRCv3.2 (partial), Matrix, Tor, DN42, Jabber/XMPP
Performance
moderate
Mobile
good
Accessibility
basic
SEO
basic

Security

Observed score
55/100
Good practices seen
  • Domain status clientTransferProhibited to prevent unauthorized transfers
  • Use of modern IRC protocols (IRCv3.1 and partial IRCv3.2)
  • TLS 1.3 enabled since 2020

Analytics and tracking

Tracking level
minimal
Privacy practices
poor

Advertising

Transparency
poor

Site quality

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

Key observations

  1. Website is a community-driven communication network for hackers.
  2. No privacy, cookie, or terms of service policies found on the site.
  3. No contact emails or phone numbers explicitly provided.
  4. No security.txt or vulnerability disclosure information present.
  5. Content is well structured with clear navigation and documentation.
  6. No advertising or tracking technologies detected.
  7. TLS 1.3 support announced and presumably implemented.
  8. DNSSEC not enabled, which is a security improvement opportunity.
Technical notes

Notes

The website is built with standard web technologies (HTML5, CSS3) and supports modern IRC protocols and communication transports like Matrix and Tor. Hosting is stable and provided by a German ISP. Performance is moderate with good mobile responsiveness and clear navigation. However, accessibility features are basic and SEO optimizations limited. There is no detected CMS or advanced frameworks, indicating a lightweight, possibly custom-built site. Technical risks include lack of DNSSEC and missing security headers, which could expose users to DNS spoofing or clickjacking attacks. Modernization opportunities include enhancing accessibility, SEO, and implementing security best practices to reduce technical debt and improve resilience.
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 hackint.org. 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 hackint.org.

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.