Skip to main content

Security report for hitcluster.com

Technology · N/a

Medium risk. 7 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

Hitcluster.com is a technology-focused website providing a login portal with support for two-factor authentication, indicating a focus on secure user access. The site appears to serve a small to medium user base, likely customers or members requiring authenticated access. The business behind the domain was established in 2015, consistent with the domain registration date, suggesting a stable presence in its niche. However, public-facing content is minimal, limited to login functionality without additional business or contact information. Technically, the site uses common web technologies such as Bootstrap, jQuery, and Font Awesome, providing a modern but basic user interface. Mobile optimization is adequate, but SEO and accessibility features are limited. Security posture shows some strengths with two-factor authentication UI, but lacks critical security headers and visible SSL configuration details, which are essential for protecting user data and trust. Privacy and cookie policies are absent, indicating compliance gaps with GDPR and other privacy regulations. Overall, the site is functional but would benefit from enhanced transparency and security measures to improve user trust and regulatory compliance.

Scanned

NIS2 and GDPR posture

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

7 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 hitcluster.com

This scan found 20 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
67
Security headers
35
Email security
85
DNS health
75
Network security
100
GDPR outside view
50
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

Technical appendix

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

Business context

Business profile

The business operates in the technology sector, likely providing a platform or service requiring secure user authentication. The lack of public business information and contact details suggests a focus on existing users rather than public marketing. The domain's age and stable registration indicate a legitimate operation, but absence of certifications or trust signals limits competitive advantage. No partnerships or subsidiaries are evident from the data. The business model appears to be service-oriented, possibly SaaS or membership-based, targeting users needing secure login capabilities. Growth indicators and revenue streams are not discernible from the available data. The ecosystem is minimal with no external marketing or analytics integrations detected.

Security posture

The website demonstrates a moderate security posture with implementation of two-factor authentication, which is a positive control for user account security. However, the absence of security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options reduces protection against common web attacks. The lack of visible SSL/TLS configuration details is a concern, though HTTPS is assumed but not confirmed. No vulnerability disclosure or incident response information is provided, limiting transparency and preparedness. Privacy compliance is weak due to missing policies. Overall, the security maturity is basic, with room for significant improvements to meet industry best practices and regulatory requirements.

Recommendations

  1. Implement and enforce HTTPS with strong SSL/TLS configuration and verify via external tools.
  2. Add comprehensive privacy and cookie policies to the website to improve GDPR compliance.
  3. Publish terms of service and security policy documents to enhance transparency and trust.
  4. Deploy security headers including Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options.
  5. Establish and publicize a vulnerability disclosure program and incident response contact information.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Content quality
basic
Branding
consistent

Technology

Stack
Bootstrap, jQuery, Font Awesome
Performance
moderate
Mobile
good
Accessibility
basic
SEO
basic

Security

Observed score
50/100
Good practices seen
  • Two-factor authentication UI present

Analytics and tracking

Tracking level
minimal
Privacy practices
poor

Advertising

Transparency
poor

Site quality

Design
basic
User experience
basic
Content relevance
poor
Navigation
basic
Professionalism
basic
Trustworthiness
moderate

Key observations

  1. Website is a login portal with minimal public content.
  2. No privacy, cookie, or terms of service policies found on the login page.
  3. Two-factor authentication is supported via UI modals.
  4. No contact information or business details are publicly displayed.
  5. No external social media or marketing/analytics scripts detected.
  6. WHOIS data shows domain is stable and not privacy protected.
  7. No security headers detected in HTML content; SSL status unknown.
  8. No advertising or tracking technologies detected.
Technical notes

Notes

The website uses a standard front-end technology stack including Bootstrap for responsive design, jQuery for DOM manipulation, and Font Awesome for icons. The HTML structure is valid and includes basic meta tags but lacks Open Graph or JSON-LD structured data for SEO enhancement. Performance is likely moderate given the lightweight nature of the page, but no explicit performance optimizations or CDN usage are evident. Accessibility features are minimal, with no ARIA roles or landmarks detected. The site does not appear to use a CMS or third-party hosting provider identifiable from the data. Technical debt is low due to simplicity but modernization opportunities exist in SEO, accessibility, and security configurations.
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 hitcluster.com. 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 hitcluster.com.

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.