Skip to main content

Security report for perrigny.fr

Commune de Perrigny · Government · France

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

Security score

44/100

Risk levelHigh

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

The website www.perrigny.fr serves as the official online presence for the Commune de Perrigny, a small local government entity in France. It provides residents and visitors with essential information about municipal services, local news, contact details, and community events. The site is designed to facilitate communication between the municipality and its citizens, featuring practical resources such as opening hours, downloadable documents, and a photo gallery. The integration of the PanneauPocket application enhances real-time information dissemination. Technically, the website employs a modern technology stack including Bootstrap for responsive design, jQuery for interactivity, FontAwesome for icons, and Google Analytics for visitor tracking. Cookie consent is managed through the Tarteaucitron framework, indicating attention to privacy compliance. The site is mobile-optimized and structured for good SEO performance, although accessibility features are basic. From a security perspective, the site uses HTTPS and implements cookie consent mechanisms, but lacks visible advanced security headers and a published security policy or incident response information. The absence of WHOIS data limits domain trust assessment, but the website content and official contact information strongly indicate legitimacy. No vulnerabilities or malicious content were detected. Overall, www.perrigny.fr is a well-maintained municipal website with good content quality and user experience. Strategic improvements in security headers, transparency on security policies, and WHOIS data availability would enhance trust and compliance.

Scanned

NIS2 and GDPR posture

GDPR outside view
28/ 100 · High
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

    • 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

  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 perrigny.fr

This scan found 29 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
72
Security headers
15
Email security
70
DNS health
60
Network security
20
GDPR outside view
28
Average
44

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

Breach exposure

Leaked credentials and lookalike domains from OffSeq Breach. The counts are free; the detailed lists are paid add-ons.

Dark web exposure

Add-on

Leaked records that mention perrigny.fr, from OffSeq Breach.

No leaked records found

Breach holds no records for perrigny.fr right now. New leaks arrive continuously, so monitoring on Breach alerts you if that changes.

Monitor on Breach (opens in a new tab)

Technical appendix

Business context, site observations and technical notes gathered during the scan, and the standards behind each reference.

Business context

Business profile

The Commune de Perrigny operates as a local government entity providing essential public services and information to its community. Its market position is that of a small municipal authority focused on transparency and citizen engagement. The business model is non-commercial, centered on public service delivery. Revenue streams are typical of local governments, likely funded by public budgets rather than commercial activities. The target audience includes residents, local businesses, and visitors seeking municipal information. The partnership ecosystem includes regional community organizations and digital service providers like PanneauPocket. Growth indicators are limited due to the nature of the entity, but digital adoption through mobile app integration suggests modernization efforts. The website supports community cohesion and administrative efficiency.

Security posture

The website demonstrates a moderate security maturity level with HTTPS enforced and cookie consent implemented, reflecting compliance with basic privacy regulations such as GDPR. However, the absence of key security headers (e.g., Content Security Policy, HSTS) and lack of published security or incident response policies indicate areas for improvement. No exposed sensitive data or vulnerable libraries were detected in the provided content. The site does not publish a security.txt file or provide explicit channels for vulnerability reporting, which could hinder incident response readiness. Overall, the security posture is adequate for a municipal informational site but would benefit from enhanced security controls and transparency.

Recommendations

  1. Implement comprehensive HTTP security headers including Content Security Policy, HSTS, X-Frame-Options, and X-Content-Type-Options to strengthen site security.
  2. Publish a detailed security policy and incident response plan on the website to improve transparency and preparedness.
  3. Create and maintain a security.txt file to facilitate responsible vulnerability disclosure and communication.
  4. Regularly audit and update third-party scripts and libraries to mitigate potential vulnerabilities.
  5. Enhance accessibility features to comply with recognized standards and improve user experience for all visitors.

Contact details published on the site

Addresses
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Commune de Perrigny
Description
Informations et services de la commune de Perrigny, village fleuri au cœur de l'Yonne (89) en Bourgogne.
Key services
Municipal services information, Local news and announcements, Contact and administrative information, Community events and galleries
Content quality
good
Branding
consistent

Technology

Stack
Bootstrap 5.3.3, jQuery 3.5.1, FontAwesome 6.7.2, Google Analytics (gtag.js), Tarteaucitron cookie consent
Frameworks
Bootstrap
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
75/100
Good practices seen
  • HTTPS enforced
  • Cookie consent banner implemented

Analytics and tracking

Services
Google Analytics
Tracking level
moderate
Privacy practices
good

Advertising

Marketing tools
PanneauPocket app integration
Transparency
basic

Site quality

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

Key observations

  1. Official municipal website for Perrigny commune in France
  2. Content is in French and well structured
  3. Includes contact info, opening hours, local news, and community services
  4. Uses modern web technologies and cookie consent tools
  5. No signs of malicious or adult content
  6. WHOIS data unavailable, limiting domain trust assessment
Technical notes

Notes

The website is built using a modern and widely adopted technology stack, including Bootstrap 5.3.3 for responsive design, jQuery 3.5.1 for DOM manipulation, and FontAwesome 6.7.2 for iconography. Google Analytics is used for visitor tracking, and cookie consent is managed via Tarteaucitron. The site loads external resources from reputable CDNs, which supports performance and reliability. The HTML structure is well-formed with appropriate meta tags for SEO and viewport settings for mobile optimization. Performance is moderate, with potential for improvement through optimization of image sizes and script loading strategies. The absence of a detected CMS suggests a custom or lightweight platform. Technical debt appears low, but adding modern security headers and improving accessibility would reduce risks and enhance compliance.
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 perrigny.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 perrigny.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.