Skip to main content

Security report for sitejs.org

Small Technology Foundation · Technology · Ireland

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

Security score

70/100

Risk levelMedium

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

Site.js is an open-source web construction set developed and maintained by the Small Technology Foundation, a non-profit organization based in Ireland. The platform targets individual users and small-scale developers, providing tools to develop, test, sync, and deploy static and dynamic websites easily. It integrates modern technologies such as Node.js, Express.js, Hugo static site generator, and DotJS for dynamic routing, with automatic TLS provisioning via Let’s Encrypt and mkcert. The project emphasizes simplicity, security by default, and freedom, catering to the 'Small Web' community rather than enterprises or governments. Technically, Site.js demonstrates a mature and modern infrastructure with support for multiple platforms (Linux, macOS, Windows), integrated static site generation, dynamic JavaScript routing, WebSocket support, and a built-in JavaScript database (JSDB). The website is well-designed, mobile-optimized, and provides comprehensive documentation and examples, reflecting a high level of digital maturity. From a security perspective, Site.js benefits from automatic TLS everywhere, secure WebSocket implementations, and no visible vulnerabilities or exposed sensitive data. However, the website lacks explicit security headers and formal privacy or cookie policies, which are areas for improvement. The WHOIS data is malformed and lacks transparency, but the website's open-source nature and non-profit affiliation support its legitimacy. Overall, Site.js presents a low-risk profile with strong technical and business credibility, though it would benefit from enhanced privacy compliance and security policy disclosures to further strengthen trust and compliance.

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 X-Frame-Options header

      Prevents clickjacking attacks

      What to do: Add "X-Frame-Options: DENY" or "X-Frame-Options: SAMEORIGIN"

  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 sitejs.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
82
Security headers
40
Email security
75
DNS health
75
Network security
100
GDPR outside view
50
Average
70

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

Site.js occupies a niche market focused on empowering individuals and small developers to host and manage their own websites with ease and security. Its competitive advantage lies in its all-in-one binary tool that simplifies deployment and management, automatic TLS provisioning, and integration with popular static and dynamic site technologies. The business model is donation-funded open source, targeting a community valuing privacy, simplicity, and control. The foundation's non-profit status and transparent open-source code foster trust and community engagement. Partnerships with Owncast and integration with Hugo expand its ecosystem. Growth indicators include active GitHub repositories and recent content updates. Strategic observations highlight a focus on decentralization and user empowerment rather than commercial enterprise solutions.

Security posture

Site.js demonstrates a strong security posture with HTTPS enforced by default using Let’s Encrypt and mkcert, secure WebSocket support, and no detected vulnerabilities in the provided content. The platform's design encourages secure defaults and ease of use, reducing common misconfigurations. However, the absence of explicit security headers such as Content-Security-Policy and lack of published privacy and security policies represent compliance gaps. Incident response mechanisms and vulnerability disclosure policies are not evident on the site, which could be improved to enhance security readiness. The WHOIS data's lack of transparency is a minor concern but mitigated by the open-source and non-profit nature of the project. Overall, the security culture appears proactive but could benefit from formalized policies and disclosures.

Recommendations

  1. Publish comprehensive privacy and cookie policies to improve GDPR compliance and user trust.
  2. Implement and display explicit security headers (e.g., Content-Security-Policy, X-Frame-Options) to enhance protection against common web attacks.
  3. Establish and publicize a vulnerability disclosure policy and security contact information to improve incident response readiness.
  4. Improve WHOIS transparency if possible to strengthen domain trustworthiness.
  5. Consider adding a security.txt file to facilitate security communications and disclosures.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Small Technology Foundation
Description
Site.js is a small web construction set designed for individuals to develop, test, sync, and deploy websites and web applications easily. It supports static and dynamic sites, automatic TLS, and includes features like WebSockets and a built-in JavaScript database. The project is maintained by the Small Technology Foundation, a tiny not-for-profit based in Ireland focused on tools for individuals rather than enterprises or governments.
Key services
Static and dynamic site hosting, Automatic TLS provisioning, Integrated Hugo static site generator, DotJS dynamic routing, WebSocket support, JavaScript in-memory database (JSDB), Proxy server with automatic TLS
Content quality
excellent
Branding
consistent

Technology

Stack
Node.js, Express.js, DotJS, Hugo, JavaScript, WebSockets, Let’s Encrypt, mkcert
Frameworks
Express.js, Hugo static site generator
Platforms
Linux, macOS, Windows
Performance
fast
Mobile
good
Accessibility
good
SEO
good

Security

Observed score
90/100
Good practices seen
  • Automatic TLS everywhere
  • Secure WebSocket support
  • No exposed sensitive data in HTML
  • No vulnerable libraries detected in scripts
  • Secure dynamic routing with DotJS
  • Automatic certificate renewal

Analytics and tracking

Services
archive.org internal analytics
Tracking level
minimal
Privacy practices
basic

Advertising

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 rich content and no blocking detected.
  2. No privacy or cookie policies found on the site.
  3. No explicit contact emails or phone numbers provided.
  4. Strong focus on small-scale, individual web hosting and development.
  5. Open source and non-profit oriented project.
  6. Good technical implementation with modern tools and automatic TLS.
  7. No advertising or tracking beyond archive.org analytics.
  8. No security headers detected in HTML response (based on available data).
  9. WHOIS data is incomplete and malformed, limiting domain trust analysis.
Technical notes

Notes

The website is built on a modern and robust technical stack including Node.js, Express.js, Hugo, and DotJS, supporting both static and dynamic content efficiently. The integration of automatic TLS provisioning and WebSocket support indicates a well-architected infrastructure prioritizing security and performance. The site is mobile-optimized and accessible, with good SEO practices evident in meta tags and structured content. The use of a single binary tool simplifies deployment and reduces technical debt. Performance appears fast with minimal external dependencies beyond essential libraries and archive.org resources. Opportunities exist to enhance security headers and formalize privacy and security policies to reduce compliance 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

Reviews of this site

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