Skip to main content

Security report for miraheze.org

WikiTide Foundation, Inc. · Technology · United States

Low risk. 4 critical or high findings in GDPR outside view and SSL/TLS.

Security score

78/100

Risk levelLow

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

Miraheze is a non-profit organization operating under WikiTide Foundation, Inc., providing free, ad-free wiki hosting services powered by expert MediaWiki volunteers. The platform targets individuals and organizations seeking customizable wiki solutions without advertising distractions. Miraheze's market position is strong within the niche of free wiki hosting, supported by a medium-sized team and a clear mission to serve users with expert technical support and extensive customization options. Technically, the website leverages a modern tech stack including MediaWiki, Bootstrap 5, FontAwesome, and privacy-focused Matomo analytics. The site is well-optimized for performance, mobile responsiveness, and accessibility, with a clean and professional design. Hosting infrastructure includes Cloudflare DNS services, though DNSSEC is not enabled. From a security perspective, the site enforces HTTPS and avoids third-party ad scripts, enhancing user privacy. However, it lacks some advanced security headers and a formal published security policy or incident response plan. No vulnerabilities or exposed sensitive data were detected. Privacy compliance is strong with a comprehensive privacy policy and GDPR considerations, though no cookie consent mechanism is present. Overall, Miraheze presents a trustworthy, professional, and secure platform with a high level of transparency and user focus. Strategic improvements in DNS security, security policy publication, and security headers would further strengthen its posture.

Scanned

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

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.

    • 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

  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.

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

This scan found 17 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
57
Security headers
90
Email security
85
DNS health
85
Network security
100
GDPR outside view
53
Average
78

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

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

Total records
11,415
Employees
0
Customers
11,359
Third parties
56
Weak passwords
15%

1,243 subdomains affected

See the 10 newest leaked credentials

A one-off add-on to this report that lists the most recent identifier and password pairs OffSeq Breach holds for miraheze.org.

Select it in the checkout above.

Breach keeps ingesting new leaks, so these numbers can grow between scans.

Technical appendix

Business context, site observations and technical notes gathered during the scan, and the standards behind each reference.

Business context

Business profile

Miraheze operates in the technology and non-profit sectors, focusing on free wiki hosting services. Its business model relies on donations and volunteer expertise rather than commercial advertising or subscription fees. The platform's competitive advantage lies in its ad-free experience, extensive customization, and expert volunteer support. Target customers include hobbyists, educators, researchers, and communities needing wiki solutions. Growth indicators include a large user base (680,000 users) and over 22,000 hosted wikis. The organization maintains a transparent partnership ecosystem with open communication channels and active community engagement. Strategic observations highlight the importance of maintaining privacy and security standards to uphold user trust and sustain growth.

Security posture

Miraheze demonstrates a mature security posture with mandatory HTTPS, no ads or third-party trackers, and use of privacy-respecting analytics. The absence of DNSSEC and some security headers represents minor gaps. No formal security or incident response policies are published, which could impact readiness for security incidents. GDPR compliance is addressed through a comprehensive privacy policy, but cookie consent mechanisms are lacking. The platform shows a strong security culture with expert volunteers and transparent operations. No vulnerabilities or exposed sensitive data were found, indicating good operational security practices.

Recommendations

  1. Enable DNSSEC on miraheze.org to improve DNS security and prevent spoofing.
  2. Publish a formal security policy and incident response plan accessible to users.
  3. Implement security headers such as Content-Security-Policy, X-Content-Type-Options, and Strict-Transport-Security.
  4. Add a security.txt file to facilitate vulnerability disclosure and improve transparency.
  5. Introduce a cookie consent mechanism to enhance GDPR compliance and user privacy controls.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
WikiTide Foundation, Inc.
Description
Miraheze offers free, ad-free wiki hosting powered by expert MediaWiki volunteers. It is a non-profit platform allowing users to create and manage wikis on a wide variety of topics with extensive customization and support.
Key services
Free wiki hosting, Custom domain support, Extensive MediaWiki extensions and skins, VisualEditor support, Friendly expert support
Content quality
excellent
Branding
consistent

Technology

Stack
MediaWiki, Bootstrap 5, FontAwesome, Matomo Analytics, Cloudflare DNS
Frameworks
Bootstrap
Platforms
Web
Performance
fast
Mobile
excellent
Accessibility
good
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • No ads or third-party ad scripts
  • No exposed sensitive data in HTML
  • Use of Matomo analytics with disabled cookies

Analytics and tracking

Services
Matomo
Tracking level
minimal
Privacy practices
good

Advertising

Tracking pixels
Matomo
Marketing tools
Matomo Analytics
Transparency
excellent

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 and well-structured.
  3. Strong emphasis on privacy and ad-free hosting.
  4. Use of open-source and privacy-respecting analytics (Matomo).
  5. No signs of suspicious or malicious activity.
  6. WHOIS data supports legitimacy and transparency.
Technical notes

Notes

The website uses a modern and well-maintained technology stack centered on MediaWiki, enhanced with Bootstrap 5 for responsive design and FontAwesome for icons. Matomo analytics is used with cookies disabled, reflecting a privacy-conscious approach. The site loads quickly and is optimized for mobile devices with good accessibility features. Hosting is supported by Cloudflare DNS, though DNSSEC is not enabled, representing a minor security risk. The HTML and CSS are valid and well-structured, supporting SEO and user experience. There is no evidence of technical debt or outdated libraries. Overall, the technical infrastructure is robust and supports the business goals effectively.
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. 84/100Low22 findingsView report
Reviews of this site

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