Skip to main content

Security report for supacaz.com

SUPACAZ · Retail · N/a

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

Security score

68/100

Risk levelMedium

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

SUPACAZ is a niche cycling accessories brand emphasizing California style, offering premium products primarily through an e-commerce platform. The website is built on WordPress with WooCommerce and Elementor, indicating a modern and flexible technical infrastructure. The site integrates common marketing and analytics tools such as Google Tag Manager and Facebook Pixel, supporting moderate user tracking and marketing efforts. Security posture is generally good with HTTPS enabled and domain protections in place, though improvements are needed in security headers and privacy compliance. No blocking or WAF mechanisms interfere with content access, allowing full analysis. Overall, the site presents a professional and trustworthy front for its target cycling enthusiast audience.

Scanned

NIS2 and GDPR posture

GDPR outside view
85/ 100 · Low
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 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

  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 Protocols Supported

      Server supports weak protocols: TLSv1.1

      What to do: Disable TLS 1.0, TLS 1.1, and all SSL versions

      • CWE-327
      • OWASP A04:2025
      • ASVS V12.1.1

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

Keep watching supacaz.com

This scan found 23 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
57
Security headers
15
Email security
70
DNS health
80
Network security
100
GDPR outside view
85
Average
68

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 retail sector, focusing on cycling accessories with a lifestyle branding approach. Founded in 2011, it has a mature domain and consistent registration data. The business model is direct-to-consumer e-commerce, targeting cycling enthusiasts seeking stylish and high-quality products. The website's use of third-party marketing tools suggests active customer engagement and digital marketing strategies. No explicit partnerships or subsidiaries were identified in the content. The brand maintains consistent visual identity and content quality, supporting its market position as a premium niche player.

Security posture

The website uses HTTPS and has domain status protections that prevent unauthorized changes, indicating a baseline security maturity. However, the absence of security headers such as Content-Security-Policy and DNSSEC implementation are notable gaps. No evidence of vulnerability disclosure or incident response policies was found, which could be improved to enhance security transparency and readiness. The use of multiple third-party scripts introduces potential risk vectors that should be regularly audited. Overall, the security posture is moderate but could benefit from enhanced policies and technical controls.

Recommendations

  1. Implement comprehensive privacy and cookie policies with explicit user consent mechanisms to improve GDPR compliance.
  2. Add security headers including Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security to strengthen site security.
  3. Enable DNSSEC for the domain to protect against DNS spoofing and improve DNS security.
  4. Publish a vulnerability disclosure policy or security.txt file to facilitate responsible security reporting.
  5. Regularly audit third-party scripts and libraries for vulnerabilities and remove any unnecessary or outdated components.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
SUPACAZ
Description
SUPACAZ is a cycling brand focused on stylish, high-quality cycling accessories and products, emphasizing California style and culture.
Key services
Cycling handlebar tapes, Cycling accessories, Cycling gear
Content quality
good
Branding
consistent

Technology

Stack
JavaScript, jQuery, WooCommerce, WordPress, Elementor, Cloudflare DNS
Frameworks
WooCommerce, Elementor
Platforms
WordPress
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
75/100
Good practices seen
  • HTTPS enabled
  • Domain status includes clientDeleteProhibited and other EPP protections

Analytics and tracking

Services
Google Tag Manager, Facebook Pixel
Tracking level
moderate
Privacy practices
poor

Advertising

Tracking pixels
Facebook Pixel, Mailchimp
Marketing tools
Mailchimp, Facebook Pixel
Transparency
basic

Site quality

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

Key observations

  1. Website is a professional e-commerce site for cycling accessories.
  2. No explicit privacy or cookie policies found in the HTML content.
  3. Uses multiple third-party marketing and analytics services.
  4. No contact emails or phone numbers explicitly found in the provided HTML snippet.
  5. No security.txt or vulnerability disclosure information found.
  6. Domain is well-registered and maintained with standard protections.
  7. No WAF or blocking mechanisms detected.
Technical notes

Notes

The website is built on WordPress with WooCommerce and Elementor, leveraging a modern tech stack suitable for e-commerce. It uses Cloudflare DNS servers and GoDaddy as the registrar. Performance is moderate with preconnect and preload hints for resources, and fonts are optimized with WOFF2 formats. Mobile optimization is good, and SEO is supported by Rank Math plugin. Accessibility is basic but present. The site uses multiple marketing and analytics scripts, which require careful management to avoid performance or privacy issues. Overall, the technical implementation is solid but could be enhanced with additional security and privacy features.
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 supacaz.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 supacaz.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.