Skip to main content

Security report for com-saint-martin.fr

Error 404 (Not Found)!!1 · Other · France

High risk. 8 critical or high findings in GDPR outside view, SSL/TLS and 1 other check.

Security score

48/100

Risk levelHigh

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

The website com-saint-martin.fr currently serves a 404 error page indicating that the requested content is not found, resulting in no accessible business information or user-facing content. The domain is mature, registered since 2007 with a French registrar, and uses Google hosting infrastructure. However, the lack of a valid SSL certificate and HTTPS support severely impacts the security posture and user trust. Minimal security headers are present but some are misconfigured, and no privacy or cookie policies are found, indicating poor compliance with data protection regulations. Overall, the site appears abandoned or misconfigured, offering no business or contact information to visitors. Technically, the site is hosted on Google infrastructure with DNS managed by eolas.fr name servers. DNSSEC and CAA records are not enabled, which could improve DNS security. The site lacks modern TLS protocols and cipher suites, and no session resumption or OCSP stapling is configured. Performance data is unavailable due to the lack of content, but the minimal HTML suggests poor user experience and SEO. Security-wise, the absence of HTTPS and a valid SSL certificate is a critical vulnerability. The X-XSS-Protection header is disabled, and no advanced security headers like Content Security Policy are present. The DMARC policy is set to quarantine, which is a positive indicator for email security. No incident response or vulnerability disclosure information is available, limiting the ability to respond to security events. Given these findings, the overall risk level is high due to the lack of content, security controls, and compliance measures. Strategic recommendations include obtaining a valid SSL certificate, enabling HTTPS, improving security headers, publishing privacy and cookie policies, and providing clear contact information to enhance trust and compliance.

Scanned

NIS2 and GDPR posture

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

8 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

      EU business without adequate privacy measures

      EU businesses are subject to strict GDPR requirements

      What to do: Implement comprehensive GDPR compliance including privacy policy, cookie consent, and data protection measures

    • 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. 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 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';…

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

Keep watching com-saint-martin.fr

This scan found 22 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
35
Email security
85
DNS health
70
Network security
100
GDPR outside view
0
Average
48

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 domain com-saint-martin.fr is registered to a French entity with a mature registration history, suggesting a stable presence. However, the absence of any accessible website content or business information limits insight into market positioning or business model. No partnerships, subsidiaries, or certifications are evident. The domain's DNS and email configurations indicate use of Microsoft Outlook protection services and Google hosting, which are standard but do not provide direct business intelligence. The lack of privacy and security policies, as well as contact details, suggests limited digital maturity and possibly an inactive or placeholder website.

Security posture

The security posture of the website is weak. The absence of HTTPS and a valid SSL certificate exposes users to interception and man-in-the-middle attacks. Security headers are minimal and partially misconfigured, with X-XSS-Protection disabled and no HSTS policy. DNS security features like DNSSEC and CAA are not enabled, increasing risk of DNS spoofing or unauthorized certificate issuance. No vulnerability disclosure or incident response information is provided, indicating low readiness for security incidents. The DMARC policy is a positive aspect, helping to protect email domains from spoofing. Overall, the site does not meet basic security best practices and requires urgent improvements.

Recommendations

  1. Obtain and deploy a valid SSL/TLS certificate to enable HTTPS across the site.
  2. Enable and configure HSTS with includeSubDomains and preload to enforce secure connections.
  3. Implement DNSSEC and CAA records to enhance DNS security and certificate issuance control.
  4. Configure security headers properly, including Content Security Policy and Referrer-Policy.
  5. Publish clear privacy and cookie policies to comply with GDPR and inform users.
  6. Provide accessible contact information and incident response channels for transparency.
  7. Establish a vulnerability disclosure program or security.txt file to encourage responsible reporting.
  8. Improve website content and user experience to build trust and business credibility.
Technical notes

Notes

The website is hosted on Google infrastructure with DNS managed by eolas.fr name servers. The DNS configuration includes multiple A and AAAA records pointing to Google IPs, and MX records using Outlook protection services. DNSSEC and CAA are not enabled, representing a technical gap. The HTTP headers reveal a lack of HTTPS support and an invalid SSL certificate. No modern TLS protocols or cipher suites are supported. The site returns a minimal 404 error page with no metadata, structured data, or SEO elements. No analytics or marketing technologies are detected. Performance metrics are unavailable due to lack of content, but the minimal HTML suggests poor technical implementation and user experience.
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 com-saint-martin.fr. 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 com-saint-martin.fr.

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.