Skip to main content

Security report for ladrome.fr

Other · N/a

Partial score · DNS & email only

69/100

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

The website www.ladrome.fr is currently inaccessible due to a security block enforced by the Wordfence plugin, which has limited access with an HTTP 503 response. The site content is fully blocked, providing only a message about temporary access limitation and a form for WordPress administrators to request an unlock email. No business, contact, or policy information is available on the site. The domain WHOIS data is not found in the AFNIC database, indicating either privacy protection or non-registration, limiting trust and legitimacy assessment. Technically, the site runs on WordPress with Wordfence security but lacks visible security headers or SSL configuration details. Overall, the site is not analyzable in its current blocked state, resulting in a low AI score and limited insights.

Scanned

NIS2 and GDPR posture

GDPR outside view
25/ 100 · Critical
Checks completed
6of 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. 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

    • High

      No Privacy Policy found

      GDPR requires a clear and accessible privacy policy

      What to do: Add a comprehensive privacy policy page and link to it prominently

    • 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

    • 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

  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.

    • 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 ladrome.fr

This scan found 17 issues across 5 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
82
Email security
70
DNS health
70
Network security
100
GDPR outside view
25
Average
69

Not counted

  • Security headers: did not complete in this scan.
  • 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

Due to the lack of accessible content and absence of business information, no meaningful business intelligence can be derived. The site appears to be a WordPress-based website protected by Wordfence, but no details about the company, market positioning, or services are available. No external partnerships or related domains are identified. The domain's absence in WHOIS records further complicates business credibility evaluation.

Security posture

The security posture is partially observable through the use of Wordfence, a reputable WordPress security plugin, which is actively blocking access likely due to perceived security threats. However, the lack of visible security headers, SSL/TLS configuration details, and absence of security or privacy policies indicate gaps in comprehensive security implementation. The blocking mechanism may protect the site but also hinders legitimate access and analysis. Incident response and vulnerability disclosure information are missing, reducing transparency and readiness indicators.

Recommendations

  1. Review and fine-tune Wordfence blocking rules to minimize false positives and avoid blocking legitimate users.
  2. Publish clear privacy, cookie, and terms of service policies to improve compliance and user trust.
  3. Implement and verify HTTPS with strong SSL/TLS configuration and enforce security headers such as Content-Security-Policy, X-Frame-Options, and HSTS.
  4. Provide visible contact information and incident response channels to enhance transparency and support.
  5. Consider enabling vulnerability disclosure mechanisms such as security.txt and appointing a data protection officer to improve security culture.
Site observations

Automated reading of the public site. Ratings are indicative.

Wordfence detected. The site is blocked by Wordfence security plugin with HTTP 503 and an access limitation message. These observations may be incomplete. For a fuller analysis, contact guard@offseq.com.

Business

Content quality
poor
Branding
moderate

Technology

Stack
WordPress, Wordfence
Platforms
WordPress

Security

Observed score
25/100
Good practices seen
  • Use of Wordfence security plugin

Analytics and tracking

Tracking level
minimal
Privacy practices
poor

Advertising

Transparency
poor

Site quality

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

Key observations

  1. Website content is fully blocked by Wordfence security plugin
  2. No WHOIS data available from AFNIC WHOIS server
  3. No privacy, cookie, or terms of service policies found
  4. No contact information or business details available
  5. No external links except to wordfence.com documentation
  6. No analytics or advertising scripts detected
  7. Site uses WordPress CMS with Wordfence plugin
  8. No visible security headers or SSL configuration details
  9. Access blocked with HTTP 503 and message about temporary limitation
  10. Form present only for WordPress admin email unlock request
Technical notes

Notes

The website is built on WordPress and protected by the Wordfence security plugin. The HTML content is minimal and serves only as a block page with no SEO metadata, structured data, or external scripts beyond a small inline JavaScript for form activation. No analytics, advertising, or tracking technologies are detected. The site lacks visible performance or accessibility optimizations due to the blocked state. Hosting provider and infrastructure details are not discernible. The technical implementation is basic and currently dominated by security blocking rather than content delivery.
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 ladrome.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 ladrome.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.