Skip to main content

Security report for concatenative.org

Stack Effects · Technology · United States

Medium risk. 8 critical or high findings in Email security, Security headers and 2 other checks.

Security score

50/100

Risk levelMedium

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

The website concatenative.org is a specialized wiki dedicated to the family of concatenative programming languages. It serves as a community-driven knowledge repository offering theoretical and practical information, targeting programmers, researchers, and enthusiasts interested in this niche programming paradigm. The site is built on a custom Factor-based framework and uses HTTPS for secure communication. The content is well-structured and relevant, with good navigation and mobile optimization, although it lacks formal privacy and cookie policies as well as explicit contact information. From a technical perspective, the site employs a modern, albeit custom, technology stack centered around the Factor language and its Furnace web framework. Hosting and DNS services are managed via Cloudflare, providing reliable infrastructure. Performance is moderate with good mobile responsiveness, but accessibility and SEO optimizations are basic. Security posture is adequate with HTTPS enabled and domain transfer protections, but the absence of DNSSEC and security headers represents areas for improvement. Security-wise, the site shows no signs of vulnerabilities or malicious content. However, the lack of published security policies, incident response contacts, and vulnerability disclosure mechanisms limits its compliance and readiness posture. The domain WHOIS data is consistent and indicates a legitimate, long-standing project with no suspicious patterns. Overall, the website is trustworthy and safe for general audiences but would benefit from enhanced privacy, security, and compliance disclosures. Strategic recommendations include enabling DNSSEC, implementing security headers, publishing privacy and cookie policies, and providing clear contact and incident response information to improve trust and compliance. These steps will strengthen the site's security posture and user confidence while maintaining its role as a valuable educational resource.

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

8 findings rated critical or high. Fix these first.

  1. Email security

    SPF, DKIM and DMARC stop others sending email that looks like it comes from your domain, a common route to phishing and invoice fraud.

    • Critical

      No email authentication configured

      Domain is vulnerable to email spoofing

      What to do: Implement SPF, DKIM, and DMARC immediately

  2. 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"

    • 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';…

  3. 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

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

Keep watching concatenative.org

This scan found 27 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
62
Security headers
15
Email security
60
DNS health
70
Network security
40
GDPR outside view
50
Average
50

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

concatenative.org operates as a niche educational platform focused on concatenative programming languages, positioning itself as a central knowledge hub for a specialized community. Its business model is community-driven, relying on contributions and shared knowledge rather than commercial services. The site targets programmers, language researchers, and enthusiasts, offering comprehensive articles, resources, and community links. The domain's long registration history since 2008 supports its credibility and sustained presence. The lack of commercial elements, advertising, or extensive marketing tools suggests a non-profit or hobbyist orientation. Partnerships or subsidiaries are not evident, indicating an independent operation. The site’s consistent branding and good content quality reinforce its reputation within its niche. Growth potential lies in expanding content, improving compliance, and enhancing community engagement.

Security posture

The website demonstrates a moderate security maturity level with HTTPS enabled and domain transfer protections in place. However, the absence of DNSSEC and security headers such as Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security reduces its defense-in-depth. No vulnerabilities or exposed sensitive data were detected in the content or forms. The lack of published security policies, incident response procedures, and vulnerability disclosure mechanisms indicates gaps in compliance and readiness. Data protection practices appear minimal, with no privacy or cookie policies found. Incident response readiness is unclear due to missing contact channels for security issues. Overall, the security posture is functional but could be significantly improved by adopting standard best practices and transparency measures.

Recommendations

  1. Enable DNSSEC to enhance DNS security and prevent spoofing.
  2. Implement standard security headers (CSP, X-Frame-Options, HSTS) to protect against common web attacks.
  3. Publish comprehensive privacy and cookie policies to improve GDPR and privacy compliance.
  4. Add clear contact information and incident response procedures for security issues.
  5. Consider adding a vulnerability disclosure policy or security.txt file to encourage responsible reporting.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Stack Effects
Description
This wiki collects information about concatenative programming languages, including theoretical results and practical programming advice. It aims to unify various language communities into a common knowledge repository. The site also covers related topics such as compiler design, developer tools, and meta-programming relevant to concatenative languages.
Key services
Wiki content on concatenative languages, Community links and resources, Searchable articles and revisions
Content quality
good
Branding
consistent

Technology

Stack
Factor programming language, OpenSSL (for HTTPS), Farkup markup language
Frameworks
Factor Furnace web framework
Performance
moderate
Mobile
good
Accessibility
basic
SEO
basic

Security

Observed score
70/100
Good practices seen
  • HTTPS enabled via OpenSSL
  • 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 niche technical wiki focused on concatenative programming languages.
  2. No privacy, cookie, or terms of service policies found.
  3. No contact emails or phone numbers explicitly provided.
  4. No social media links detected.
  5. No security or incident response policies published.
  6. Site uses a custom Factor-based framework and markup language.
  7. HTTPS is enabled but lacks advanced security headers.
  8. No advertising or tracking technologies detected.
  9. Content is safe and suitable for general audiences.
  10. Domain WHOIS data is consistent and indicates a legitimate long-term project.
Technical notes

Notes

The website is built on a custom technology stack using the Factor programming language and the Furnace web framework, with OpenSSL providing HTTPS support. The use of a custom wiki markup language (Farkup) and a relational database backend indicates a bespoke content management system. Hosting and DNS are managed via Cloudflare, ensuring reliable infrastructure and domain protection. The site exhibits good mobile optimization and basic accessibility features, though SEO and performance optimizations are moderate. No third-party analytics, advertising, or tracking technologies were detected, indicating a privacy-conscious design. Technical risks include the lack of DNSSEC and missing security headers, which could expose the site to DNS spoofing and certain web-based attacks. Modernization opportunities include adopting standard web security practices and enhancing accessibility and SEO.
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 concatenative.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 concatenative.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.