Skip to main content

Security report for isbetabroken.com

Technology · N/a

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

Security score

69/100

Risk levelMedium

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

The website 'isbetabroken.com' serves as a status and monitoring page for the Wikimedia Foundation's Beta Cluster, a production-like environment used for final-stage testing of Wikimedia projects. It provides real-time operational status for various Wikimedia beta projects and deployment processes. The site is targeted primarily at developers and testers involved with Wikimedia projects, offering transparency into system health and deployment status. Technically, the site employs modern web technologies including JavaScript ES modules, Vue.js framework, and is built using the Vite toolchain. It is hosted on Cloudflare infrastructure with DNS managed by Cloudflare, ensuring reliable and performant delivery. The site is mobile-optimized and shows good design and navigation clarity, though accessibility features are basic. From a security perspective, the site uses HTTPS and has domain transfer protections enabled. However, DNSSEC is not enabled, and no explicit security headers or policies are visible in the content. There is a lack of privacy, cookie, and terms of service policies, as well as no contact or incident response information, which limits compliance and user trust. No tracking or analytics scripts are detected, indicating minimal user data collection. Overall, the site is a functional and focused technical status page with moderate trustworthiness and good technical implementation. The absence of privacy and security policies and DNSSEC are areas for improvement. Strategic recommendations include implementing DNSSEC, publishing privacy and cookie policies, adding contact and incident response details, and enhancing security headers to improve compliance and trust.

Scanned

NIS2 and GDPR posture

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

6 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 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 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 Privacy Policy found

      GDPR requires a clear and accessible privacy policy

      What to do: Add a comprehensive privacy policy page and link to it prominently

    • 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

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

Keep watching isbetabroken.com

This scan found 22 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
75
Security headers
30
Email security
80
DNS health
80
Network security
100
GDPR outside view
50
Average
69

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

The website supports the Wikimedia Foundation's beta testing ecosystem by providing a dedicated monitoring platform for Wikimedia beta projects and deployment statuses. Its niche positioning as a beta cluster status page limits its direct commercial business model but is essential for Wikimedia's development lifecycle. The site leverages partnerships with Wikimedia Cloud Services and Cloudflare for hosting and DNS management. The target audience is technical users such as Wikimedia developers and testers. The business model is service-oriented, focusing on operational transparency and reliability. Growth indicators include continuous uptime monitoring and deployment tracking. The site does not engage in advertising or marketing, reflecting its specialized purpose.

Security posture

The security posture of the website is moderate. HTTPS is enforced, and domain transfer protections are in place, which are positive indicators. However, the lack of DNSSEC reduces DNS security. No security headers such as Content-Security-Policy or X-Frame-Options are evident in the HTML content, which could expose the site to certain web-based attacks. There is no visible privacy or security policy, nor incident response contact information, which are important for compliance and user trust. No vulnerabilities or exposed sensitive data were detected in the content. The site does not collect user data or use tracking scripts, reducing privacy risks. Overall, the site would benefit from enhanced security headers, DNSSEC implementation, and published security policies.

Recommendations

  1. Enable DNSSEC on the domain to improve DNS security and prevent spoofing.
  2. Publish comprehensive privacy and cookie policies to enhance GDPR compliance and user trust.
  3. Add clear contact information and incident response channels for security reporting and support.
  4. Implement security headers such as Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security.
  5. Consider adding accessibility improvements to meet broader user needs and compliance standards.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Description
The Wikimedia Foundation's Beta Cluster is a functional, production-like environment hosted in WMCS, suitable for final-stage testing of new features.
Key services
Beta testing environment for Wikimedia projects, Monitoring of Wikimedia beta project statuses, Deployment status monitoring
Content quality
good
Branding
consistent

Technology

Stack
JavaScript ES Modules, Vite build tool, FontAwesome icons
Platforms
WMCS (Wikimedia Cloud Services)
Performance
fast
Mobile
good
Accessibility
basic
SEO
basic

Security

Observed score
75/100
Good practices seen
  • HTTPS enabled
  • Domain status clientTransferProhibited

Analytics and tracking

Tracking level
minimal
Privacy practices
poor

Advertising

Transparency
poor

Site quality

Design
good
User experience
good
Content relevance
good
Navigation
good
Professionalism
good
Trustworthiness
moderate

Key observations

  1. Website is a status and monitoring page for Wikimedia Foundation's Beta Cluster environment.
  2. No privacy, cookie, or terms of service policies found.
  3. No contact information or security policies disclosed.
  4. No forms or data collection mechanisms detected.
  5. No analytics or tracking scripts detected.
  6. Website uses modern JavaScript modules and Vue.js framework.
  7. Site is hosted with Cloudflare DNS and registrar.
  8. Content is technical and targeted at Wikimedia developers and testers.
  9. No advertising or marketing tools present.
  10. No security headers detected in HTML content; may be set at server level but not visible here.
Technical notes

Notes

The website is built using modern web technologies including Vue.js and JavaScript ES modules, bundled with Vite. It uses FontAwesome for icons and is hosted on Cloudflare infrastructure, providing reliable DNS and registrar services. The site loads quickly and is mobile-optimized with a clean and consistent design. There is no evidence of a traditional CMS; the site appears to be a custom-built single-page application. No analytics or tracking scripts are present, indicating minimal data collection. The site lacks visible security headers in the HTML, which may be set at the server level but are not confirmed here. Overall, the technical implementation is solid with opportunities for security and compliance enhancements.
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 isbetabroken.com. 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 isbetabroken.com.

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.