Skip to main content

Security report for qblox.com

QBLOX BV · Technology · Netherlands

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

Security score

71/100

Risk levelMedium

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

QBLOX BV is a specialized technology company operating at the forefront of the quantum revolution, providing advanced quantum control hardware and software modules to scientists and industry professionals worldwide. The company positions itself as an innovator in quantum technology, offering a range of modular products designed to facilitate quantum research and industrial applications. Their market presence is supported by a professional and well-structured website that clearly communicates their business focus and product offerings. Technically, the website is built on modern web technologies including Webflow CMS, GSAP for animations, and integrates marketing and analytics tools such as HubSpot and Google Tag Manager. The site is mobile optimized and demonstrates good SEO and accessibility practices, although some accessibility features could be enhanced. Hosting is provided via Webflow's CDN, ensuring reliable performance. From a security perspective, the website enforces HTTPS and employs domain transfer lock status, indicating a basic but solid security posture. However, the absence of DNSSEC and security headers represents areas for improvement. Privacy compliance is well addressed with a clear privacy policy, cookie consent mechanism, and GDPR compliance indicators. No explicit security policy or incident response contacts are published, which could be enhanced to improve trust and readiness. Overall, the website and business demonstrate a high level of professionalism and trustworthiness with no critical security issues detected. Strategic recommendations include enabling DNSSEC, implementing security headers, publishing a security policy, and adding vulnerability disclosure information to further strengthen security posture and compliance.

Scanned

NIS2 and GDPR posture

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

  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
    • 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 qblox.com

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
57
Security headers
30
Email security
85
DNS health
85
Network security
100
GDPR outside view
68
Average
71

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 qblox.com, from OffSeq Breach.

Total records
2
Employees
0
Customers
0
Third parties
2
Weak passwords
0%

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

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

QBLOX BV operates in the niche quantum technology sector, targeting research institutions and industrial clients requiring quantum control solutions. Their business model is B2B, focusing on modular hardware and software products that support quantum experiments and applications. The company has maintained consistent domain registration since 2013, reflecting stable operations. Their marketing ecosystem includes HubSpot and Google Tag Manager, indicating a mature approach to lead generation and customer engagement. The absence of parent or subsidiary companies suggests an independent operation. The company leverages partnerships with technology platforms like Webflow for digital presence. Growth indicators include active content updates and product offerings tailored to evolving quantum research needs.

Security posture

The security posture of QBLOX's website is solid but not exhaustive. HTTPS is properly enforced, and domain transfer lock is enabled, reducing risk of domain hijacking. However, DNSSEC is not enabled, which could expose DNS to spoofing attacks. No security headers such as Content-Security-Policy or X-Frame-Options were detected, which are recommended to mitigate common web vulnerabilities. The site uses cookie consent mechanisms compliant with GDPR, but lacks published incident response or security contact information, limiting transparency in case of security events. No vulnerabilities or exposed sensitive data were found in the HTML content. Overall, the security maturity is moderate with room for improvement in header implementation and incident readiness.

Recommendations

  1. Enable DNSSEC on the domain to enhance DNS security and prevent spoofing.
  2. Implement security headers including Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security to harden the website against common attacks.
  3. Publish a formal security policy and incident response contact information to improve transparency and preparedness.
  4. Add a vulnerability disclosure policy or security.txt file to encourage responsible reporting of security issues.
  5. Regularly audit third-party scripts and libraries to ensure no vulnerable components are included.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
QBLOX BV
Description
At Qblox we operate at the frontier of the quantum revolution, driving advancements in quantum technology to aid scientists worldwide.
Key services
Quantum control modules (QCM, QCM-RF II, QRM, QRM-RF, QRC, QTM, QSM), Quantum technology solutions for research and industry
Content quality
good
Branding
consistent

Technology

Stack
Webflow CMS, Google Tag Manager, HubSpot forms and analytics, Cookiebot for cookie consent, GSAP animation library, jQuery 3.5.1
Frameworks
Webflow, GSAP
Platforms
Webflow hosting
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
80/100
Good practices seen
  • HTTPS enforced
  • Client transfer prohibited domain status
  • Cookie consent mechanism implemented

Analytics and tracking

Services
HubSpot Analytics, Google Analytics (via GTM)
Tracking level
moderate
Privacy practices
good

Advertising

Tracking pixels
Facebook Ads Pixel, HubSpot Ads Pixel
Marketing tools
HubSpot Marketing, Leadinfo
Transparency
good

Site quality

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

Key observations

  1. Website is professionally designed and well structured.
  2. Clear focus on quantum technology products and research applications.
  3. No signs of malicious or suspicious content.
  4. Good privacy and cookie consent implementation.
  5. No explicit security policy or incident response information published.
  6. No DNSSEC enabled, which is a minor security gap.
  7. Use of modern web technologies and marketing tools.
Technical notes

Notes

The website is built using Webflow CMS, leveraging modern front-end technologies such as GSAP for animations and jQuery for DOM manipulation. It integrates multiple marketing and analytics tools including HubSpot and Google Tag Manager, indicating a mature digital marketing infrastructure. Hosting is via Webflow's CDN, providing reliable content delivery. Performance is moderate with good mobile optimization and SEO practices. Accessibility is basic and could be improved. The site uses cookie consent management via Cookiebot, ensuring compliance with privacy regulations. No major technical debt or obsolete technologies were detected, but security header implementation is lacking, representing a technical risk that should be addressed.
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 qblox.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 qblox.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.