Skip to main content

Security report for unfpa.org

United Nations Population Fund · Non-profit · N/a

High risk. 4 critical or high findings in GDPR outside view, SSL/TLS and 1 other check.

Security score

48/100

Risk levelHigh

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

The United Nations Population Fund (UNFPA) operates a comprehensive and professional website serving as the global platform for its sexual and reproductive health and population data initiatives. The site targets a broad international audience including governments, humanitarian organizations, donors, and the general public. It offers extensive content on programs, campaigns, data dashboards, and humanitarian efforts, reflecting its position as a leading UN agency in its sector. Technically, the website is built on Drupal CMS, hosted on Pantheon infrastructure, and integrates modern marketing and analytics tools such as Google Tag Manager and Visual Website Optimizer. The site is mobile optimized and SEO friendly with clear navigation and multilingual support. However, a critical security weakness is the absence of a valid SSL certificate and HTTPS support, which severely impacts the security posture and user trust. Security headers are partially implemented but require correction, especially the HSTS header. Privacy and cookie policies are present with consent mechanisms, indicating good privacy compliance. Contact information is primarily via web forms, with no direct emails or phone numbers exposed. WHOIS data is privacy protected, consistent with the organization's profile. Overall, the site is content-rich and credible but urgently needs to address its SSL/TLS configuration to improve security and trust.

Scanned

This is an earlier scan of unfpa.org. View the latest report

NIS2 and GDPR posture

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

4 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

      No HTTPS encryption

      GDPR requires appropriate security measures for personal data

      What to do: Implement SSL/TLS certificate for HTTPS

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

    • Critical

      No HTTPS Encryption

      Website does not use HTTPS encryption, making all data transmission vulnerable to interception

      What to do: Implement SSL/TLS certificate and redirect all HTTP traffic to HTTPS

  3. 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 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 unfpa.org

This scan found 15 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
0
Security headers
55
Email security
50
DNS health
50
Network security
100
GDPR outside view
33
Average
48

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

UNFPA holds a strong market position as the UN's sexual and reproductive health agency, delivering programs and data services worldwide. Its business model is non-profit and donor-funded, focusing on advocacy, humanitarian aid, and data dissemination. The website reflects this with transparency portals, policy documents, and campaign information. The organization leverages partnerships and global networks but no explicit partner domains were identified in the website content. The use of advanced marketing tools and multilingual content supports broad outreach and engagement. The lack of exposed contact emails or phone numbers suggests a controlled communication strategy, likely to manage inquiries centrally. The domain's privacy-protected WHOIS registration aligns with typical UN practices, supporting legitimacy. Growth indicators include active campaigns and frequent news updates. Strategic observations include the need to enhance security infrastructure to maintain donor and public trust.

Security posture

The website's security posture is currently weak due to the absence of a valid SSL certificate and lack of HTTPS support, which is a critical vulnerability affecting confidentiality and integrity of user data. Security headers such as X-Content-Type-Options, X-Frame-Options, and X-XSS-Protection are present, providing some protection against common web attacks. However, the Strict-Transport-Security header is misconfigured, reducing its effectiveness. No known SSL vulnerabilities like Heartbleed or POODLE were detected, but the lack of TLS protocols and session resumption mechanisms indicates outdated or incomplete SSL/TLS setup. No explicit incident response or vulnerability disclosure policies were found, which could be improved to enhance security culture and transparency. Privacy policies and cookie consent mechanisms are well implemented, supporting compliance. Overall, the site requires urgent remediation of SSL/TLS issues and enhancement of security policies to meet modern standards.

Recommendations

  1. Obtain and deploy a valid SSL/TLS certificate to enable HTTPS across the entire site immediately.
  2. Correct the HSTS header configuration and enable includeSubDomains to enforce HTTPS and prevent downgrade attacks.
  3. Implement OCSP stapling and session resumption to improve SSL performance and security.
  4. Publish explicit vulnerability disclosure and incident response policies to improve transparency and security culture.
  5. Enhance accessibility features and provide direct verified contact information to improve user trust and compliance.
Technical notes

Notes

The website is built on Drupal CMS and hosted on Pantheon infrastructure, leveraging modern marketing and analytics tools such as Google Tag Manager and Visual Website Optimizer. The site supports multiple languages and is mobile optimized with responsive design. Performance data was not available, but the use of CDN and caching headers suggests moderate to good performance. The HTML content is well structured with proper meta tags and Open Graph data for SEO and social sharing. However, the SSL/TLS configuration is incomplete with no valid certificate and no enabled TLS protocols, which is a major technical risk. Security headers are partially implemented but require correction. The site uses JavaScript-based tracking and consent mechanisms for cookies, indicating a mature approach to privacy compliance. Overall, the technical infrastructure is modern but requires urgent security upgrades to ensure safe and trusted operations.
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

Earlier scans of this domain

  1. 74/100Medium29 findingsView report
Reviews of this site

Share your experience with unfpa.org. 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 unfpa.org.

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.