Skip to main content

Security report for mercure.rocks

Les-Tilleuls.coop · Technology · N/a

Medium risk. 7 critical or high findings in Security headers, GDPR outside view and 2 other checks.

Security score

69/100

Risk levelMedium

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

Mercure.rocks is a technology-focused website offering an open-source protocol for real-time communications, designed to be fast, reliable, and battery-efficient. It targets developers and API providers looking to add streaming and asynchronous capabilities to REST and GraphQL APIs. The site is professionally designed, leveraging modern web technologies such as Next.js and Material-UI, and provides both free open-source software and managed cloud hosting services. The parent organization, Les-Tilleuls.coop, also offers training and professional services, reinforcing the business model. Technically, the website demonstrates a mature digital infrastructure with responsive design, good SEO, and modern JavaScript frameworks. It uses Server-Sent Events and HTTP/2+ for efficient real-time data delivery. Analytics are implemented via Cloudflare Insights, with minimal user tracking. However, some security headers are not explicitly visible, and cookie consent mechanisms are absent. From a security perspective, the site enforces HTTPS and avoids exposing sensitive data. The WHOIS data is limited due to TLD registry constraints, lacking registrant details and domain age information, but the website's professionalism and association with a known cooperative mitigate concerns. Privacy and terms of use policies are present and comprehensive, though incident response contacts and vulnerability disclosure information are missing. Overall, Mercure.rocks presents a trustworthy and technically sound platform for real-time API solutions, with room for improvement in security header implementation, cookie consent, and transparency around incident response. The domain's limited WHOIS data is a minor concern but does not detract significantly from the site's credibility.

Scanned

NIS2 and GDPR posture

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

7 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

    • 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. Email security

    SPF, DKIM and DMARC stop others sending email that looks like it comes from your domain, a common route to phishing and invoice fraud.

    • High

      No DMARC record found

      DMARC provides email authentication and reporting

      What to do: Add DMARC record: "v=DMARC1; p=none; rua=mailto:dmarc@yourdomain.com"

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

Keep watching mercure.rocks

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
62
Security headers
50
Email security
65
DNS health
85
Network security
100
GDPR outside view
53
Average
69

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

Mercure.rocks occupies a niche in the real-time communication technology market, offering an open protocol alternative to WebSockets. Its competitive advantage lies in its simplicity, native browser support, and integration with REST and GraphQL APIs. The business model combines open-source software distribution with managed cloud hosting and professional services, including training. The target customers are developers, enterprises needing real-time data streaming, and IoT device manufacturers. The partnership with Les-Tilleuls.coop enhances credibility and service offerings. The presence of notable users like M6 and Sensiolabs indicates market acceptance. Growth potential exists through expanding managed services and training programs. The ecosystem includes GitHub for code hosting and Twitter for community engagement.

Security posture

The website demonstrates a good security posture with enforced HTTPS and no visible exposure of sensitive information. The absence of explicit security headers such as Content Security Policy or HSTS is a gap that should be addressed to enhance protection against common web attacks. No vulnerable libraries or insecure forms were detected. Privacy policies are comprehensive and GDPR compliant, but cookie consent mechanisms are lacking. Incident response and vulnerability disclosure information are not provided, which limits transparency and preparedness. The WHOIS data limitations do not indicate malicious intent but reduce traceability. Overall, the site is secure for its purpose but would benefit from enhanced security headers and formalized incident response channels.

Recommendations

  1. Implement and enforce security headers including Content Security Policy (CSP), HTTP Strict Transport Security (HSTS), and X-Frame-Options.
  2. Add a cookie policy and consent mechanism to comply with privacy regulations and improve user trust.
  3. Publish a vulnerability disclosure policy or security.txt file to facilitate responsible reporting of security issues.
  4. Provide clear incident response contact information, such as a dedicated security or abuse email address.
  5. Consider deploying DNSSEC to improve domain name system security and integrity.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Les-Tilleuls.coop
Description
Mercure is an open solution for real-time communications designed to be fast, reliable, and battery-efficient. It is a modern and convenient replacement for both WebSockets and the higher-level libraries and services relying on it. Mercure is especially useful to add streaming and asynchronous capabilities to REST and GraphQL APIs. A free reference server and hosted service are available.
Key services
Mercure protocol implementation, Free open source reference server, Managed Mercure Hub cloud hosting, Training and professional services via Les-Tilleuls.coop
Content quality
excellent
Branding
consistent

Technology

Stack
React, Next.js, Material-UI, Server-Sent Events (SSE), HTTP/2+
Frameworks
Next.js, Material-UI
Platforms
Web browsers, Mobile, IoT devices
Performance
fast
Mobile
excellent
Accessibility
good
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • No exposed sensitive data in HTML
  • No visible vulnerable libraries
  • Secure external links with rel="noopener noreferrer"

Analytics and tracking

Services
Cloudflare Insights
Tracking level
minimal
Privacy practices
basic

Advertising

Tracking pixels
Cloudflare Insights
Transparency
basic

Site quality

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

Key observations

  1. Website is fully accessible with rich content.
  2. No WAF or blocking mechanisms detected.
  3. Strong focus on real-time API technology and developer audience.
  4. Clear links to parent cooperative and professional services.
  5. Good use of modern web technologies and responsive design.
  6. Limited WHOIS data due to TLD registry constraints.
  7. Privacy and terms policies are present and comprehensive.
  8. No contact phone numbers or physical addresses found.
  9. Email contact provided via footer link.
  10. No cookie consent mechanism detected.
Technical notes

Notes

The website is built using modern web technologies including React, Next.js, and Material-UI, ensuring a responsive and performant user experience. It leverages Server-Sent Events and HTTP/2+ protocols for efficient real-time communication. The site is well-structured with semantic HTML and good accessibility features. Performance is optimized with preloading and deferred scripts. Analytics are implemented via Cloudflare Insights with minimal tracking. No CMS is detected, indicating a custom or static site generation approach. Hosting details are not explicit but likely cloud-based. The technical stack is robust and suitable for the target developer audience, with minor opportunities for improvement in security header implementation and cookie management.
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 mercure.rocks. 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 mercure.rocks.

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.