Skip to main content

Security report for lurk.org

Private by Design, LLC · Technology · United States

Medium risk. 8 critical or high findings in Security headers, GDPR outside view and 2 other checks.

Security score

57/100

Risk levelMedium

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

LURK is a volunteer-run community platform established in 2006 that hosts and archives discussions on net- and computational culture, free culture practices, and experimental media arts. It offers a suite of community services including mailing lists, federated instant messaging via XMPP, an Icecast streaming server, and a Mastodon Fediverse instance. The platform targets individuals and collectives seeking alternatives to corporate social media and surveillance capitalism, emphasizing open source and self-hosting principles. The business model relies on donations and community support rather than commercial revenue streams. Technically, LURK operates on a modest infrastructure using VPS providers and open source software such as mailman3, hyperkitty, Prosody, Icecast, and a customized Mastodon fork. The website is functional with good content quality and basic mobile optimization but lacks advanced CMS or modern web frameworks. SEO and accessibility are basic but adequate for the community-focused audience. From a security perspective, the domain is well-established with protective domain status flags but lacks DNSSEC and visible security headers. The platform supports modern end-to-end encryption for chat services but does not publish formal security or incident response policies. Privacy compliance is minimal, with no cookie consent mechanism and only a basic privacy policy linked via TOS.txt. Contact information is limited to an obfuscated email address and Mastodon profiles. Overall, LURK presents a trustworthy, niche community service with a moderate security posture and basic privacy compliance. Strategic improvements in DNS security, formal security policies, and privacy transparency would enhance trust and resilience.

Scanned

NIS2 and GDPR posture

GDPR outside view
43/ 100 · High
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. 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';…

  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

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

This scan found 28 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
52
Security headers
15
Email security
70
DNS health
60
Network security
100
GDPR outside view
43
Average
57

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

LURK occupies a niche market segment focused on alternative digital culture and community-driven services outside mainstream corporate platforms. Its competitive advantage lies in its long-standing presence since 2006, volunteer-driven ethos, and integration of multiple open source communication tools. The business model is non-commercial, relying on donations and community engagement. Target customers are technically savvy individuals and groups interested in self-hosting, privacy, and federated social networks. Partnerships with VPS providers and related open source communities support its operations. Growth is organic and community-based, with a capped Mastodon instance to maintain quality. Strategic observations include the need to formalize security and privacy practices to sustain trust and compliance as the community grows.

Security posture

LURK demonstrates a moderate security maturity level with domain protections and encrypted chat services. However, the absence of DNSSEC, security headers, and published security policies indicates gaps in defense-in-depth and transparency. No incident response or vulnerability disclosure mechanisms are publicly available, limiting readiness for security events. Privacy compliance is basic, lacking cookie consent and detailed data protection statements. The platform’s volunteer nature and limited scale reduce exposure but also constrain formal security governance. Business impact of vulnerabilities is moderate given the community focus, but improvements in DNS security, policy publication, and privacy mechanisms are recommended to mitigate risks and align with GDPR and best practices.

Recommendations

  1. Enable DNSSEC on the domain to improve DNS integrity 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, HSTS, and X-Frame-Options on the web server.
  4. Add a clear cookie policy and consent mechanism to comply with privacy regulations.
  5. Consider establishing 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
Private by Design, LLC
Description
Hosts, facilitates, and archives discussions around net- and computational culture and politics, proto- and post-free culture practices, experimental sound, new media, software art, and related topics.
Key services
Mailing lists hosting, Federated instant messaging (XMPP chat), Icecast audio streaming server, Fediverse Mastodon instance, Wiki documentation
Content quality
good
Branding
consistent

Technology

Stack
mailman3, hyperkitty, XMPP, Prosody, Icecast, Mastodon (modified Hometown fork)
Platforms
Fediverse, Mailman mailing lists, XMPP chat
Performance
moderate
Mobile
basic
Accessibility
basic
SEO
basic

Security

Observed score
65/100
Good practices seen
  • Domain status includes clientDeleteProhibited and clientTransferProhibited
  • Use of E2E encryption in XMPP chat
  • Limited Mastodon instance size to control community

Analytics and tracking

Tracking level
minimal
Privacy practices
basic

Advertising

Transparency
poor

Site quality

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

Key observations

  1. Volunteer-run community platform focused on alternative digital culture.
  2. No commercial advertising or tracking detected.
  3. Limited account numbers on Mastodon instance to maintain community quality.
  4. No cookie consent mechanism or explicit privacy policy page found.
  5. No visible security headers or advanced security policies published.
  6. Contact information is obfuscated to reduce spam but present.
  7. No phone numbers or physical addresses provided.
  8. Website content is well structured and informative.
Technical notes

Notes

The technical infrastructure is composed of multiple VPS-hosted machines running open source software for mailing lists, chat, streaming, and social networking. The use of mailman3, hyperkitty, Prosody, Icecast, and a customized Mastodon fork reflects a mature but modest tech stack focused on community services. Hosting is distributed across known VPS providers with a backup machine at a university. Website performance is moderate with basic mobile and accessibility features. No modern CMS or advanced frameworks detected, indicating potential for modernization. Lack of DNSSEC and security headers suggests technical debt in security hardening. Overall, the infrastructure supports the community’s needs but could benefit from modernization and enhanced security controls.
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 lurk.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 lurk.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.