Skip to main content

Security report for oceancare.org

OceanCare · Non-profit · Switzerland

High risk. 8 critical or high findings in Network security, Security headers and 2 other checks.

Security score

49/100

Risk levelHigh

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

OceanCare is a Swiss-based international non-profit organization dedicated to ocean conservation and marine life protection since 1989. Recognized as a United Nations special advisor for marine protection, OceanCare operates with a strong focus on advocacy, public awareness, and scientific research to combat ocean pollution, destructive fishing practices, and underwater noise. The organization sustains its operations primarily through donations, memberships, and campaigns, targeting environmentally conscious individuals, NGOs, and policymakers. Technically, the website is built on WordPress using Elementor, enhanced with modern JavaScript libraries and analytics tools like Matomo and Google Tag Manager. It features GDPR-compliant cookie consent mechanisms and secure donation forms, reflecting a mature digital infrastructure. The site is well-optimized for SEO, mobile-friendly, and accessible, providing a professional user experience. From a security perspective, the site enforces HTTPS and employs cookie consent but lacks explicit advanced security headers. No vulnerabilities or exposed sensitive data were detected. The WHOIS data is unavailable, likely due to privacy protection, which is common and justified for non-profit entities. Overall, the website demonstrates a strong security posture and trustworthy business credibility. Strategically, OceanCare should enhance security headers and maintain regular audits of third-party scripts to mitigate risks. Continued transparency and compliance with privacy regulations will further strengthen user trust and organizational reputation.

Scanned

NIS2 and GDPR posture

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

8 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: MySQL

      Port 3306 (MySQL) is publicly accessible - MySQL - Database server

      What to do: Immediately restrict access to MySQL 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
    • 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';…

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

Keep watching oceancare.org

This scan found 21 issues across 5 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
77
Security headers
15
Email security
100
DNS health
70
Network security
0
GDPR outside view
85
Average
58
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

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 oceancare.org, from OffSeq Breach.

No leaked records found

Breach holds no records for oceancare.org 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

OceanCare holds a reputable position in the environmental non-profit sector, leveraging its UN special advisor status to influence marine protection policies globally. Its business model revolves around fundraising through donations, memberships, and advocacy campaigns. The organization targets environmentally aware supporters and stakeholders interested in ocean sustainability. Partnerships and networks are evident through social media and campaign collaborations. The website content and structure indicate a medium-sized organization with a consistent brand and high-quality content, supporting its mission and outreach effectively.

Security posture

The website exhibits a good security maturity level with enforced HTTPS, secure form handling, and GDPR-compliant cookie consent. However, the absence of explicit security headers like Content-Security-Policy and X-Frame-Options suggests room for improvement. No signs of vulnerabilities or data leaks were found. Incident response and security policy documentation are not publicly available, which could be enhanced to improve transparency and readiness. Overall, the security posture is solid for a non-profit but can benefit from implementing additional best practices.

Recommendations

  1. Implement and enforce security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options to enhance protection against common web attacks.
  2. Publish a clear security policy and incident response plan accessible to users to improve transparency and preparedness.
  3. Regularly update and audit all third-party plugins and scripts to mitigate potential vulnerabilities.
  4. Enhance data protection officer contact visibility and provide explicit information about data processing practices.
  5. Maintain and improve cookie consent mechanisms to ensure ongoing compliance with evolving privacy regulations.

Contact details published on the site

Addresses
Legal name
OceanCare
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
OceanCare
Description
Seit 1989 erhebt OceanCare die Stimme für das Leben im Meer. Die internationale Organisation mit Sitz in der Schweiz ist UNO-Sonderberaterin für den Meeresschutz und trägt zur Erreichung der globalen Nachhaltigkeitsziele bei.
Key services
Meeresschutz Advocacy, Informationskampagnen, Petitionen, Forschung und Monitoring, Mitgliedschaft und Spendenakquise
Content quality
excellent
Branding
consistent

Technology

Stack
WordPress, Elementor, PHP, jQuery, Matomo Analytics, Borlabs Cookie Consent, Google Tag Manager
Frameworks
Elementor Page Builder
Platforms
WordPress CMS
Performance
moderate
Mobile
good
Accessibility
good
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • Cookie consent mechanism implemented
  • No exposed sensitive data in HTML
  • Use of nonce tokens in forms

Analytics and tracking

Services
Matomo
Tracking level
moderate
Privacy practices
good

Advertising

Tracking pixels
Matomo
Marketing tools
Borlabs Cookie Consent, Nelio A/B Testing
Transparency
good

Site quality

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

Key observations

  1. Website is fully accessible with no blocking or WAF challenges.
  2. Content is professionally presented in German with English alternate language.
  3. Strong focus on ocean conservation and environmental advocacy.
  4. Multiple donation and membership options with secure forms.
  5. Cookie consent and privacy policy are implemented and GDPR compliant.
  6. Use of modern web technologies and analytics tools.
  7. No suspicious or malicious content detected.
  8. WHOIS data unavailable, likely privacy protected.
Technical notes

Notes

The website is built on a modern WordPress CMS platform using Elementor for page building, supported by jQuery and other JavaScript libraries. It integrates Matomo for analytics and Borlabs Cookie for consent management, indicating a focus on privacy compliance. The site loads moderately fast with good mobile optimization and accessibility features. The use of CDN for fonts and scripts improves performance. However, the hosting provider is not explicitly identified. The technical stack is well-maintained but could benefit from enhanced security headers and continuous performance monitoring.
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 oceancare.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 oceancare.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.