Skip to main content

Security report for head.com

Other · N/a

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

Security score

72/100

Risk levelMedium

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

The website www.head.com is a commercial retail platform focused on sports equipment and accessories. The site employs modern frontend technologies such as React and integrates payment processing through Adyen Checkout, with customer review functionality powered by Yotpo. The website content is accessible without any WAF or security challenge blocking, indicating good availability. However, the site lacks visible privacy, cookie, and terms of service policies, as well as explicit contact information, which impacts compliance and trust. Security headers are not detected, and SSL configuration details are limited, suggesting room for improvement in security posture. Overall, the site appears legitimate and safe for general audiences but would benefit from enhanced transparency and security best practices.

Scanned

NIS2 and GDPR posture

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

4 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 Strict-Transport-Security header

      Forces HTTPS connections

      What to do: Add "Strict-Transport-Security: max-age=31536000; includeSubDomains; preload"

      • CWE-319
      • OWASP A04:2025
      • ASVS V3.4.1
    • 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 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 head.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
100
Security headers
20
Email security
75
DNS health
65
Network security
100
GDPR outside view
73
Average
72

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

HEAD operates in the retail sports equipment sector, targeting consumers interested in sports gear. The business model is e-commerce focused, leveraging online sales with integrated payment solutions. The use of Yotpo indicates an emphasis on customer engagement and marketing through reviews. The absence of detailed business information and contact data on the site limits deeper business intelligence insights. The domain's WHOIS data is privacy protected, which is typical for commercial brands but reduces transparency. No suspicious domains or partners were identified from the HTML content.

Security posture

The website uses HTTPS, but no detailed SSL configuration information is available. No security headers such as Content-Security-Policy or X-Frame-Options were detected, which are recommended to mitigate common web attacks. The absence of privacy and cookie policies indicates potential compliance gaps with GDPR and other privacy regulations. No incident response or security contact information is provided, limiting the ability to report security issues. The integration of third-party services like Adyen and Yotpo introduces dependencies that require monitoring for vulnerabilities. Overall, the security posture is moderate but requires enhancements to meet best practices and regulatory compliance.

Recommendations

  1. Implement and publish comprehensive privacy and cookie policies to improve GDPR compliance and user trust.
  2. Add security headers including Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security to enhance protection against web attacks.
  3. Provide clear contact information including security incident response contacts to facilitate vulnerability reporting and compliance.
  4. Conduct regular security audits and vulnerability assessments, especially for third-party integrations like Adyen and Yotpo.
  5. Improve website content quality and navigation clarity to enhance user experience and business credibility.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Content quality
poor
Branding
moderate

Technology

Stack
React, Adyen Checkout, Yotpo
Frameworks
React
Performance
moderate
Mobile
good
Accessibility
basic
SEO
basic

Security

Observed score
50/100

Analytics and tracking

Tracking level
minimal
Privacy practices
poor

Advertising

Tracking pixels
Yotpo
Marketing tools
Yotpo
Transparency
basic

Site quality

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

Key observations

  1. Website content is accessible and not blocked by WAF or security challenges.
  2. No WHOIS data available publicly, indicating privacy protection or registry restrictions.
  3. No visible privacy, cookie, or terms of service policies found in the HTML content.
  4. No explicit contact emails, phone numbers, or physical addresses found in the provided HTML.
  5. Website uses modern frontend technologies including React and integrates payment via Adyen Checkout.
  6. Yotpo is used for customer reviews and marketing.
  7. No security headers detected in the provided data; SSL is present but configuration details unknown.
  8. Content is commercial retail focused, safe for general audiences.
  9. No suspicious or malicious content detected.
Technical notes

Notes

The website is built using React, indicating a modern frontend framework. Payment processing is handled via Adyen Checkout, a reputable payment platform. Customer reviews and marketing tools are provided by Yotpo. The site appears to be hosted on infrastructure associated with the domain mcprod.head.com, though specific hosting provider details are not available. Performance is moderate with good mobile optimization. Accessibility features are basic, and SEO optimization is minimal based on meta tags and content structure. The lack of visible CMS suggests a custom or proprietary platform. Technical debt and modernization opportunities exist in improving security headers, privacy compliance, and content richness.
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

Earlier scans of this domain

  1. 75/100Medium21 findings · partial scanView report
  2. 29/100High27 findingsView report
Reviews of this site

Share your experience with head.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 head.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.