Skip to main content

Security report for laboratoiresbewell.com

Other · N/a

High risk. 9 critical or high findings in GDPR outside view, SSL/TLS and 2 other checks.

Security score

28/100

Risk levelHigh

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

The website laboratoiresbewell.com currently serves only a default hosting placeholder page with no accessible content, metadata, or business information. The domain is registered and hosted on OVH infrastructure, but no SSL certificate is installed, resulting in no HTTPS support. This severely limits the website's security posture and user trust. No privacy, cookie, or terms of service policies are present, and no contact information or forms are available, indicating the site is either inactive or under construction. From a technical perspective, the lack of content and modern security configurations reflects a low digital maturity level. The absence of security headers and encryption exposes the site to potential risks and undermines compliance with data protection regulations. Overall, the website is not currently functional as a business or informational platform, and its security and privacy posture is critically weak.

Scanned

This is an earlier scan of laboratoiresbewell.com. View the latest report

NIS2 and GDPR posture

GDPR outside view
15/ 100 · Critical
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

9 findings rated critical or high. Fix these first.

  1. GDPR outside view

    These are the privacy signals visitors and data protection authorities look for under GDPR.

    • Critical

      No HTTPS encryption

      GDPR requires appropriate security measures for personal data

      What to do: Implement SSL/TLS certificate for HTTPS

  2. 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.

    • Critical

      No HTTPS Encryption

      Website does not use HTTPS encryption, making all data transmission vulnerable to interception

      What to do: Implement SSL/TLS certificate and redirect all HTTP traffic to HTTPS

  3. Network security

    Services reachable from the internet are the first thing attackers probe. Anything open that does not need to be should be closed.

    • Critical

      Critical Service Exposed: MySQL

      Port 3306 (MySQL) is publicly accessible - MySQL - Database server

      What to do: Immediately restrict access to MySQL using firewall or VPN

      • NIS2 21(2)(e)
      • IR 2024/2690 6.7.2(f): Implementing Regulation (EU) 2024/2690, Annex point 6.7.2(f): Network security
      • NIST CM-7: NIST SP 800-53 Rev. 5 CM-7: Least Functionality
      • NIST SC-7: NIST SP 800-53 Rev. 5 SC-7: Boundary Protection

  4. 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"

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

Keep watching laboratoiresbewell.com

This scan found 18 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
0
Security headers
20
Email security
50
DNS health
85
Network security
0
GDPR outside view
15
Average
28

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 · found on this site
  • 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

Due to the lack of accessible content and metadata, no meaningful business intelligence can be derived. The domain is registered with OVH and uses their mail servers, but no company name, description, or services are presented. There are no indications of market positioning, target audience, or business model. The absence of contact details and trust indicators further limits any assessment of the company's operations or credibility. This suggests the domain may be reserved or inactive rather than actively representing a business entity.

Security posture

The security posture of laboratoiresbewell.com is poor. The site lacks a valid SSL certificate and does not support any TLS protocols, resulting in no HTTPS encryption. Security headers such as HSTS are not enabled, and no secure cipher suites are configured. There is no evidence of security policies, incident response contacts, or vulnerability disclosure mechanisms. These deficiencies expose the site to interception risks and reduce user trust. The DNS configuration is standard with OVH nameservers and mail servers, but the absence of DNSSEC and CAA records further limits domain security. Immediate remediation is required to implement HTTPS and improve security headers to protect users and comply with best practices.

Recommendations

  1. Obtain and install a valid SSL/TLS certificate to enable HTTPS across the site.
  2. Configure modern TLS protocols (TLS 1.2 or 1.3) and strong cipher suites to secure communications.
  3. Implement security headers including HSTS, Content Security Policy, and X-Frame-Options.
  4. Develop and publish privacy, cookie, and terms of service policies to improve compliance and transparency.
  5. Add clear contact information and security incident response details to enhance trust and readiness.
Technical notes

Notes

The website is hosted on OVH infrastructure as indicated by DNS records. The HTTP headers show Apache server with HTTP/2 upgrade support but no HTTPS. The site returns a minimal HTML page redirecting to a default cgi-sys page, indicating a placeholder or inactive site. No CMS, frameworks, or external scripts are detected. Performance metrics are unavailable due to lack of content. The absence of SSL and modern security configurations represents a critical technical debt. The site requires modernization including SSL deployment, content development, and implementation of SEO and accessibility best practices to become a functional and secure web presence.
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. 28/100High26 findingsView report
Reviews of this site

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