Skip to main content

Security report for iphronline.org

International Partnership for Human Rights (IPHR) · Non-profit · Belgium

High risk. 6 critical or high findings in Network security, Security headers and 1 other check.

Security score

49/100

Risk levelHigh

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

International Partnership for Human Rights (IPHR) is a Brussels-based independent NGO founded in 2008, focusing on human rights advocacy and support in Central Asia, Eastern Europe, and the South Caucasus. The organization empowers local civil society groups, conducts research and reporting on human rights violations, and engages in advocacy with international institutions. Their website reflects a mature digital presence with comprehensive content, clear navigation, and consistent branding. Technically, the site is built on WordPress, hosted on SiteGround, and uses modern SEO and GDPR compliance tools. Security posture is good with HTTPS and domain transfer protections, though DNSSEC is not enabled and some security headers appear missing. No direct contact emails or phone numbers are publicly listed, relying on contact forms and social media channels. Overall, the site is professional, trustworthy, and safe for general audiences.

Scanned

NIS2 and GDPR posture

GDPR outside view
95/ 100 · Low
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

6 findings rated critical or high. Fix these first.

  1. Network security

    Services reachable from the internet are the first thing attackers probe. Anything open that does not need to be should be closed.

    • Critical

      Critical Service Exposed: PostgreSQL

      Port 5432 (PostgreSQL) is publicly accessible - PostgreSQL - Database server

      What to do: Immediately restrict access to PostgreSQL using firewall or VPN

      • NIS2 21(2)(e)
      • IR 2024/2690 6.7.2(f): Implementing Regulation (EU) 2024/2690, Annex point 6.7.2(f): Network security
      • NIST CM-7: NIST SP 800-53 Rev. 5 CM-7: Least Functionality
      • NIST SC-7: NIST SP 800-53 Rev. 5 SC-7: Boundary Protection

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

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

    • High

      Weak Protocols Supported

      Server supports weak protocols: TLSv1.1

      What to do: Disable TLS 1.0, TLS 1.1, and all SSL versions

      • CWE-327
      • OWASP A04:2025
      • ASVS V12.1.1

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

Keep watching iphronline.org

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. 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
72
Security headers
15
Email security
75
DNS health
75
Network security
0
GDPR outside view
95
Average
55
After the cap
49

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 · found on this site
  • 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

IPHR operates as a non-profit advocacy organization with a clear focus on human rights issues in specific geopolitical regions. Their business model centers on partnerships, capacity building, and advocacy rather than commercial revenue. The organization maintains a strong partnership ecosystem visible through their website and social media. Their market position is that of a specialized NGO with over a decade of experience, targeting civil society actors, international bodies, and the public interested in human rights. The website content and structure support their mission effectively, though the absence of explicit privacy and terms policies may be a gap for compliance and transparency.

Security posture

The website benefits from HTTPS encryption and domain registration protections that prevent unauthorized transfers or updates. The use of a GDPR cookie consent plugin indicates awareness of privacy compliance. However, the lack of DNSSEC and absence of visible security headers such as Content-Security-Policy or X-Frame-Options suggest room for improvement. No vulnerability disclosure or incident response information is provided, which could be a concern for security transparency. No exposed sensitive data or vulnerable libraries were detected. Overall, the security posture is solid but could be enhanced with additional best practices and published policies.

Recommendations

  1. Enable DNSSEC on the domain to improve DNS security and prevent spoofing.
  2. Implement and configure security headers like Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options.
  3. Publish a clear privacy policy and terms of service pages accessible from the homepage.
  4. Add a vulnerability disclosure policy or security.txt file to facilitate responsible reporting.
  5. Provide explicit incident response contact information to improve transparency and trust.

Contact details published on the site

Addresses
Legal name
International Partnership for Human Rights (IPHR)
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
International Partnership for Human Rights (IPHR)
Description
International Partnership for Human Rights (IPHR) is an independent, non-governmental organisation founded in Brussels in 2008. It cooperates with civil society groups in Central Asia, Eastern Europe and the South Caucasus to promote accountability for human rights violations. IPHR empowers partner groups to conduct their work locally and assists them in raising human rights concerns internationally.
Key services
Supporting victims of transnational repression, Civil society support and capacity building, Monitoring and reporting human rights violations, Advocacy and communications, Crisis response, Holistic accountability, Promoting rights of vulnerable groups
Content quality
excellent
Branding
consistent

Technology

Stack
WordPress, Yoast SEO plugin, jQuery, SiteGround Optimizer
Platforms
WordPress
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
80/100
Good practices seen
  • HTTPS enabled
  • ClientTransferProhibited and clientUpdateProhibited domain status
  • Use of GDPR cookie consent plugin

Analytics and tracking

Tracking level
minimal
Privacy practices
basic

Advertising

Transparency
poor

Site quality

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

Key observations

  1. Website is a professionally maintained NGO site focused on human rights.
  2. Content is rich, well-structured, and regularly updated with news and reports.
  3. Strong social media presence across multiple platforms.
  4. Uses WordPress CMS with SEO and GDPR compliance plugins.
  5. No direct contact emails or phone numbers found on homepage; contact form is primary contact method.
  6. No explicit privacy policy or terms of service pages detected in the provided content.
  7. Cookie consent mechanism is implemented via moove_gdpr plugin.
  8. No visible security.txt or vulnerability disclosure policy.
  9. No advertising or tracking scripts detected in the provided content.
Technical notes

Notes

The website is built on WordPress CMS with the Yoast SEO plugin and jQuery library, hosted on SiteGround servers. The site uses a combined CSS optimizer for performance and a GDPR compliance plugin for cookie consent. The design is responsive and mobile-friendly with good SEO metadata including Open Graph and JSON-LD structured data. Performance is moderate, with potential for improvement through further optimization. Accessibility is basic but functional. No major technical debt or outdated libraries were detected in the provided content. The site architecture supports clear navigation and content discovery.
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 iphronline.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 iphronline.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.