Skip to main content

Security report for wikiversity.org

Wikiversity · Education · N/a

Medium risk. 5 critical or high findings in Security headers, GDPR outside view and 1 other check.

Security score

68/100

Risk levelMedium

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

Wikiversity is a Wikimedia Foundation project dedicated to providing free, open educational resources across multiple languages. It serves a global audience of learners, educators, and self-directed students by offering a collaborative platform for creating and sharing learning materials. The site is part of the larger Wikimedia ecosystem, which includes Wikipedia, Wikibooks, and other sister projects, reinforcing its position as a trusted source of free knowledge. Technically, the website is built on the MediaWiki platform, leveraging Wikimedia's robust infrastructure. The site demonstrates excellent performance, mobile optimization, and accessibility, ensuring a high-quality user experience. The use of HTTPS and secure form handling indicates a strong baseline security posture, although some security headers could be improved. From a security perspective, the site benefits from Wikimedia Foundation's established practices, including comprehensive privacy and terms of use policies that comply with GDPR. No critical vulnerabilities or suspicious content were detected. However, the absence of explicit security policies or incident response contacts suggests room for enhancement in transparency and readiness. Overall, Wikiversity presents a low-risk, high-trust profile with excellent content quality and technical implementation. Strategic recommendations include enhancing security headers, publishing a vulnerability disclosure policy, and providing clearer security contact information to further strengthen trust and compliance.

Scanned

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

NIS2 and GDPR posture

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

5 findings rated critical or high. Fix these first.

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

  2. GDPR outside view

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

    • 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

    • 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

  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 SSL Key Length

      SSL certificate uses 256-bit key, which is considered weak

      What to do: Use at least 2048-bit RSA or 256-bit ECC key

      • CWE-326
      • OWASP A04:2025
      • Mozilla TLS: Mozilla Server Side TLS 6.0 intermediate: rsa_key_size 2048

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

Keep watching wikiversity.org

This scan found 21 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
75
Security headers
30
Email security
70
DNS health
80
Network security
100
GDPR outside view
53
Average
68

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

Wikiversity operates as a non-profit educational platform under the Wikimedia Foundation umbrella, targeting a broad audience interested in free learning resources. Its competitive advantage lies in its integration with the Wikimedia ecosystem, multilingual support, and community-driven content creation model. Revenue streams are primarily donation-based, supporting the open knowledge mission. The platform's partnerships with sister Wikimedia projects create a synergistic ecosystem that enhances user engagement and content richness. Growth indicators include extensive language offerings and a large volume of learning resources. The absence of commercial advertising aligns with its non-profit status and educational focus.

Security posture

The website exhibits a mature security posture with enforced HTTPS and secure form handling. The lack of visible security headers such as Content-Security-Policy and X-Frame-Options represents an area for improvement. No exposed sensitive data or vulnerable libraries were detected in the provided HTML. Privacy policies are comprehensive and GDPR compliant, reflecting strong data protection practices. However, the absence of a published security.txt or explicit incident response contacts limits transparency and may delay vulnerability reporting. Overall, the security culture appears robust but could benefit from enhanced communication and formalized vulnerability disclosure mechanisms.

Recommendations

  1. Implement comprehensive security headers including Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security.
  2. Publish a security.txt file to facilitate vulnerability disclosure and improve transparency.
  3. Add visible security contact information or dedicated incident response channels on the website.
  4. Enhance cookie policy visibility and implement a consent mechanism to improve privacy compliance.
  5. Regularly audit third-party scripts and dependencies to ensure no vulnerable libraries are included.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Wikiversity
Description
Wikiversity is a Wikimedia Foundation project providing free learning resources and educational content in multiple languages.
Key services
Free learning resources, Multilingual educational content, Community-driven course and lesson creation
Content quality
excellent
Branding
consistent

Technology

Stack
JavaScript, CSS3, HTML5, MediaWiki
Performance
fast
Mobile
excellent
Accessibility
good
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • Secure search form with POST method
  • No exposed sensitive data in HTML

Analytics and tracking

Tracking level
minimal
Privacy practices
excellent

Advertising

Transparency
poor

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 rich, multilingual, and educational.
  3. Strong affiliation with Wikimedia Foundation and sister projects.
  4. No direct contact emails or phone numbers found on main page.
  5. Privacy and terms policies are clearly linked and comprehensive.
  6. No advertising or tracking scripts detected in provided HTML.
  7. Uses MediaWiki CMS and Wikimedia hosting infrastructure.
  8. No security.txt or explicit vulnerability disclosure found.
  9. No suspicious or malicious content detected.
Technical notes

Notes

Wikiversity is powered by the MediaWiki CMS, hosted on Wikimedia Foundation infrastructure, ensuring high availability and performance. The site uses modern web standards including HTML5, CSS3, and JavaScript, with responsive design for mobile optimization. The technical implementation is clean with no broken elements detected. SEO is supported through proper meta tags and multilingual content. There is no evidence of legacy or deprecated technologies, indicating good technical maintenance. Opportunities exist to improve security headers and formalize vulnerability disclosure processes to reduce technical risks.
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. 68/100Medium30 findingsView report
Reviews of this site

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