Skip to main content

Security report for endlessos.org

Other · N/a

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

Security score

73/100

Risk levelMedium

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

The website www.endlessos.org appears to represent a technology-related entity, likely associated with the Endless OS project, which is an open-source operating system. The site is built on the Wix platform, utilizing standard Wix scripts and third-party tracking tools such as Google Tag Manager and Facebook Pixel. However, the content provided is minimal and lacks detailed business descriptions, contact information, or privacy and cookie policies. The WHOIS data is unavailable due to a malformed response, which limits the ability to verify domain registration details and reduces trustworthiness. Technically, the site uses modern JavaScript libraries and polyfills but lacks advanced security headers and comprehensive privacy compliance mechanisms. Overall, the site is accessible and safe but requires improvements in transparency, security, and content richness to enhance credibility and compliance.

Scanned

NIS2 and GDPR posture

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

  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 endlessos.org

This scan found 23 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
35
Email security
75
DNS health
80
Network security
100
GDPR outside view
73
Average
73

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 business behind the website likely operates in the technology sector, focusing on open-source software or operating systems. The lack of detailed business information, contact details, and policies suggests a small or community-driven project rather than a large enterprise. The presence of Mastodon social links indicates engagement with open-source and decentralized social platforms. The business model may revolve around software distribution and community support. Market positioning appears niche, targeting users interested in alternative operating systems. No partnerships or subsidiaries are identified from the data. The website's minimal content and lack of trust signals limit its competitive advantage and growth indicators.

Security posture

The security posture of the website is basic. HTTPS is presumably enabled (inferred from the URL), but no explicit security headers are detected in the provided content. The site includes third-party tracking scripts, which may introduce privacy concerns. There is no evidence of vulnerability disclosure policies, incident response contacts, or security certifications. The absence of privacy and cookie policies indicates potential compliance gaps with GDPR and other data protection regulations. No forms or input fields are present to assess secure data handling. Overall, the site demonstrates minimal security best practices and would benefit from enhanced security configurations and transparency.

Recommendations

  1. Implement and publish comprehensive privacy and cookie policies with clear GDPR compliance statements.
  2. Add contact information including emails and phone numbers for business and security incident reporting.
  3. Configure and enforce security headers such as Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security.
  4. Obtain and display relevant security certifications or compliance badges to improve trust.
  5. Regularly audit and update third-party scripts to mitigate potential vulnerabilities and privacy risks.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Content quality
poor
Branding
moderate

Technology

Stack
Wix, JavaScript, core-js, focus-within-polyfill, Google Tag Manager, Facebook Pixel
Platforms
Wix.com Website Builder
Performance
moderate
Mobile
basic
Accessibility
basic
SEO
basic

Security

Observed score
30/100

Analytics and tracking

Services
Google Tag Manager, Facebook Pixel
Tracking level
moderate
Privacy practices
poor

Advertising

Tracking pixels
Facebook Pixel
Marketing tools
Facebook Pixel
Transparency
basic

Site quality

Design
basic
User experience
basic
Content relevance
poor
Navigation
basic
Professionalism
basic
Trustworthiness
moderate

Key observations

  1. Website is built using Wix platform with standard Wix scripts and styles.
  2. No WHOIS data available due to malformed WHOIS response.
  3. No privacy, cookie, or terms of service policies detected in the provided HTML content.
  4. No contact emails, phone numbers, or physical addresses found in the content.
  5. Social media links to Mastodon instances are present.
  6. No security headers or advanced security configurations detected in the HTML content.
  7. Tracking scripts for Google Tag Manager and Facebook Pixel are included.
  8. No forms detected in the provided HTML content.
  9. Content appears minimal or truncated; no detailed business or product information found.
  10. No evidence of WAF or blocking mechanisms; site is accessible.
Technical notes

Notes

The website is built on the Wix platform, leveraging its standard JavaScript libraries and polyfills for compatibility. It uses Google Tag Manager and Facebook Pixel for analytics and marketing purposes. The site appears to have moderate performance and basic mobile optimization. Accessibility features are minimal but present at a basic level. SEO optimization is limited, with no detected Open Graph or JSON-LD structured data in the provided content. The hosting provider is likely Wix's infrastructure. The technical stack is modern but lacks customization or advanced features. There is no evidence of server-side security configurations or advanced performance optimizations.
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 endlessos.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 endlessos.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.