Skip to main content

Security report for parc-marais-poitevin.fr

Parc naturel régional du Marais Poitevin · Hospitality · France

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

Security score

46/100

Risk levelHigh

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

The website represents the official online presence of the Parc naturel régional du Marais Poitevin, a regional natural park in France focused on tourism and nature discovery. It provides visitors with information on activities, itineraries, and experiences within the park, targeting tourists and nature enthusiasts. The site is built on WordPress with a range of plugins including Yoast SEO and Mapbox for mapping features. While the content quality and SEO are good, the site lacks a valid SSL certificate and does not serve content over HTTPS, which is a critical security flaw. The presence of SPF and DMARC records with strict policies indicates good email security practices. Social media integration and cookie consent mechanisms are well implemented, supporting GDPR compliance. However, the absence of visible phone numbers and physical addresses limits direct contact options. Overall, the site is functional and professional but requires urgent security improvements to protect user data and enhance trust.

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

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

      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

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

    • 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 parc-marais-poitevin.fr

This scan found 25 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. The full timeline opens with your unlock code.

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
75
Security headers
15
Email security
80
DNS health
85
Network security
20
GDPR outside view
0
Average
46

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 Parc naturel régional du Marais Poitevin operates as a government or non-profit entity promoting regional tourism and environmental awareness. Its market position is authoritative within its niche, supported by partnerships with regional government bodies. The business model is informational and promotional, relying on content and digital engagement to attract visitors. Key services include providing detailed itineraries, multimedia content, and experiential suggestions. The partnership ecosystem includes regional departments and a digital agency. Growth indicators include multilingual support and active social media channels. Revenue streams are not explicit but likely involve regional funding and tourism promotion.

Security posture

The website's security posture is weak due to the lack of HTTPS and an invalid SSL certificate, exposing users to potential data interception risks. While DNS-based email security (SPF and DMARC) is properly configured with a reject policy, the web server reveals PHP version information, increasing attack surface. No advanced security headers or mechanisms like HSTS or OCSP stapling are enabled. The cookie consent mechanism is comprehensive and GDPR compliant, indicating awareness of privacy regulations. Incident response and security policy documentation are absent, suggesting limited formal security governance. Immediate remediation of SSL/TLS issues is critical to reduce risk.

Recommendations

  1. Obtain and deploy a valid SSL/TLS certificate to enable HTTPS across the entire site.
  2. Enable HSTS with includeSubDomains and preload to enforce secure connections.
  3. Remove or obfuscate server and PHP version headers to reduce fingerprinting.
  4. Implement OCSP stapling and session resumption to improve security and performance.
  5. Publish clear security and incident response policies to enhance trust and compliance.
Technical notes

Notes

The site uses a mature WordPress CMS with PHP 7.4.33 on an nginx server, hosted likely by Infomaniak. It leverages common web technologies including jQuery, Mapbox GL JS, and Yoast SEO for content optimization. The site is mobile-optimized with responsive CSS and includes accessibility considerations. However, performance metrics are missing or zero, indicating potential monitoring gaps. The absence of HTTPS is a major technical debt and security risk. The technology stack is standard but requires modernization in security protocols. The site integrates multiple third-party services for analytics, advertising, and social media, which are well managed with cookie consent controls.
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 parc-marais-poitevin.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 parc-marais-poitevin.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.