Skip to main content

Security report for meteo.pf

METEO FRANCE · Government · French Polynesia

Medium risk. 7 critical or high findings in Email security, Security headers and 2 other checks.

Security score

65/100

Risk levelMedium

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

Météo-France Polynésie Française operates as the official meteorological service for French Polynesia, providing comprehensive weather forecasts, marine data, cyclone tracking, and climate information. The website serves residents and visitors with timely and region-specific meteorological data, positioning itself as a trusted government entity in the region. The business model is focused on public service and information dissemination, supported by the parent organization Météo-France. The site maintains a consistent brand identity and leverages official social media channels for outreach. Technically, the website is built on Drupal 9, utilizing modern web technologies such as Leaflet.js for interactive maps and Google Tag Manager for analytics. It incorporates GDPR-compliant cookie consent mechanisms via Didomi and Privacy Center SDKs, reflecting a mature digital infrastructure. The site is mobile-optimized and accessible, with good SEO practices and moderate performance. From a security perspective, the site enforces HTTPS and employs consent management for privacy compliance. While explicit security headers are not fully visible in the provided data, the overall posture is strong with no evident vulnerabilities or exposed sensitive data. However, the site could improve by publishing explicit security policies and incident response contacts. Overall, the website is a reliable and professional platform with high trustworthiness, suitable for its government service role. Strategic recommendations include enhancing security header implementation, publishing security and incident response policies, and maintaining vigilance on third-party scripts to sustain security and compliance.

Scanned

NIS2 and GDPR posture

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

    • Critical

      No email authentication configured

      Domain is vulnerable to email spoofing

      What to do: Implement SPF, DKIM, and DMARC immediately

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

  3. GDPR outside view

    These are the privacy signals visitors and data protection authorities look for under GDPR.

    • 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 Consent Banner found

      GDPR requires explicit consent for non-essential cookies

      What to do: Implement a cookie consent banner that appears on first visit

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

Keep watching meteo.pf

This scan found 24 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
40
Email security
60
DNS health
75
Network security
100
GDPR outside view
50
Average
65

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

Météo-France Polynésie Française holds a strong market position as the official meteorological authority in French Polynesia, backed by the national Météo-France organization. Its competitive advantage lies in localized, authoritative weather data and alerts tailored to the region's unique climate and cyclone risks. The business model is public service-oriented, focusing on information provision rather than commercial revenue. The target customers include local residents, government agencies, maritime operators, and tourists. Growth indicators include digital modernization and integration of interactive mapping and consent management tools. The partnership ecosystem includes related meteorological and climate data providers, enhancing service breadth and reliability.

Security posture

The website demonstrates a mature security posture with enforced HTTPS, GDPR-compliant cookie consent, and use of privacy SDKs. No critical vulnerabilities or exposed sensitive data were detected. However, the absence of explicit security headers like X-Frame-Options and X-Content-Type-Options suggests room for improvement. There is no publicly visible security policy or incident response contact, which could hinder transparency and user trust in case of incidents. Compliance with GDPR is evident, but additional documentation on data protection and incident handling would strengthen the security culture. Overall, the site is secure but could benefit from enhanced security communication and header implementation.

Recommendations

  1. Implement and explicitly declare security headers such as X-Frame-Options and X-Content-Type-Options to improve defense-in-depth.
  2. Publish a clear security policy and incident response contact information to enhance transparency and user trust.
  3. Regularly audit and update third-party scripts and SDKs to mitigate potential vulnerabilities.
  4. Enhance user privacy controls by providing detailed data retention and processing information.
  5. Maintain and improve mobile optimization and accessibility to ensure broad user reach and compliance.

Contact details published on the site

Addresses
Legal name
METEO FRANCE
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
METEO FRANCE
Description
Retrouvez les prévisions météo de Météo-France sur la Polynésie française - Tahiti, Moorea, Bora-Bora, îles Marquises, … - pour aujourd'hui, demain et les prochains jours
Key services
Weather forecasts, Marine weather information, Cyclone tracking and alerts, Climatological data and bulletins, Satellite animations and isofront maps, Vigilance and weather warnings
Content quality
good
Branding
consistent

Technology

Stack
Drupal 9, Leaflet.js, Google Tag Manager, Didomi Consent SDK, Privacy Center SDK
Frameworks
Drupal
Performance
moderate
Mobile
good
Accessibility
good
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • Cookie consent with opt-in/out
  • No exposed sensitive data in HTML
  • Use of privacy SDKs for consent management

Analytics and tracking

Services
Google Tag Manager
Tracking level
moderate
Privacy practices
good

Advertising

Ad networks
Google DoubleClick
Tracking pixels
Hubvisor
Transparency
basic

Site quality

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

Key observations

  1. Official meteorological website for French Polynesia operated by Météo-France.
  2. Comprehensive weather and climate information including forecasts, marine data, cyclone tracking, and vigilance alerts.
  3. Uses modern web technologies and consent management for GDPR compliance.
  4. No signs of malicious or suspicious activity detected.
  5. Social media presence on Facebook and YouTube for outreach.
  6. No direct contact emails or phone numbers found on the main page.
  7. No explicit security or incident response policies publicly visible.
  8. Advertising and tracking are present but managed with consent.
Technical notes

Notes

The website is built on Drupal 9, a modern and widely supported CMS, ensuring a solid foundation for content management and security. It uses Leaflet.js for interactive maps, enhancing user engagement with weather data visualization. Google Tag Manager and Didomi SDKs are integrated for analytics and privacy compliance, reflecting a mature approach to data governance. Performance is moderate, with preloading of fonts and asynchronous loading of scripts to optimize speed. The site is mobile-optimized and accessible, with semantic HTML and ARIA roles. Technical risks are minimal but include potential dependency on third-party scripts and the need for explicit security headers. Opportunities exist to further modernize by adopting HTTP/2 or newer protocols and enhancing security headers.
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 meteo.pf. 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 meteo.pf.

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.