Skip to main content

Security report for common-lisp.net

Common-Lisp.Net maintainers · Technology · N/a

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

Security score

50/100

Risk levelMedium

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

Common-Lisp.net is a specialized community platform dedicated to supporting the Common Lisp programming language ecosystem. It provides essential services such as project hosting, mailing lists, documentation, and community resources aimed at both new and experienced Lisp programmers. The website has a long-standing presence since 2003, reflecting a stable niche position within the programming community. Technically, the site employs modern frontend technologies including Bootstrap 4, jQuery, and FontAwesome, delivering a good user experience with responsive design and clear navigation. However, it lacks advanced SEO and accessibility features and does not use a CMS. From a security perspective, the website benefits from domain registration best practices such as clientTransferProhibited status and a long registration period, indicating good domain management. However, it lacks DNSSEC, security headers, and explicit privacy or cookie policies, which are important for modern compliance and security standards. No vulnerability disclosure or incident response information is provided, which could be improved to enhance trust and security readiness. Overall, the website is trustworthy and serves its community well but has room for improvement in privacy compliance and security hardening. The absence of tracking and analytics services suggests a privacy-conscious approach. Strategic enhancements in security headers, DNSSEC, and policy disclosures would strengthen the site's security posture and compliance standing.

Scanned

NIS2 and GDPR posture

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

9 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 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

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

Keep watching common-lisp.net

This scan found 26 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
42
Security headers
15
Email security
85
DNS health
80
Network security
40
GDPR outside view
35
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

Common-Lisp.net operates as a small, community-driven platform focused on the technology sector, specifically the Common Lisp programming language niche. Its business model centers on providing free, open source project hosting and community resources, supported by maintainers rather than commercial revenue streams. The platform targets developers and programmers interested in Lisp, offering mailing lists and documentation to foster collaboration and knowledge sharing. The long domain age and consistent branding indicate a stable presence. The absence of commercial advertising or analytics suggests a non-commercial, community-first approach. Partnerships appear limited to related Lisp community sites and services. Growth indicators include active news updates and migration to new hosting infrastructure. The platform's competitive advantage lies in its specialized focus and community trust.

Security posture

The website demonstrates a moderate security maturity level. Domain registration practices are sound, with clientTransferProhibited status and a long registration period. However, the lack of DNSSEC and absence of HTTP security headers such as Content Security Policy, HSTS, and X-Frame-Options represent gaps that could expose users to certain risks. No privacy or cookie policies are present, indicating compliance gaps with GDPR and related regulations. The site does not provide vulnerability disclosure or incident response information, limiting transparency and preparedness. No analytics or tracking scripts reduce privacy risks but also limit monitoring capabilities. Overall, the security posture is functional but would benefit from enhancements in DNS security, HTTP headers, and compliance documentation.

Recommendations

  1. Enable DNSSEC on the domain to protect against DNS spoofing and improve overall DNS security.
  2. Implement standard HTTP security headers including Content Security Policy (CSP), HTTP Strict Transport Security (HSTS), X-Frame-Options, and X-Content-Type-Options to mitigate common web vulnerabilities.
  3. Publish clear privacy and cookie policies to improve GDPR compliance and user trust.
  4. Add a vulnerability disclosure policy and incident response contact information to enhance security transparency and readiness.
  5. Consider adding accessibility improvements and SEO enhancements to broaden reach and usability.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Common-Lisp.Net maintainers
Description
Common-Lisp.net is a community-driven website providing resources, project hosting, mailing lists, and documentation for the Common Lisp programming language. It serves as a gateway and development hub for Common Lisp programmers, both new and experienced.
Key services
Project hosting for open source Common Lisp projects, Mailing lists for Common Lisp topics, Documentation and community resources
Content quality
good
Branding
consistent

Technology

Stack
HTML5, CSS (Bootstrap 4), JavaScript (jQuery, Popper.js, Bootstrap JS), FontAwesome icons, Google Fonts (Source Sans Pro)
Frameworks
Bootstrap 4
Performance
moderate
Mobile
good
Accessibility
basic
SEO
basic

Security

Observed score
50/100
Good practices seen
  • Domain status clientTransferProhibited to prevent unauthorized transfers

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
high

Key observations

  1. Website is a community resource hub for Common Lisp programming language.
  2. No privacy, cookie, or terms of service policies found, indicating compliance gaps.
  3. No security.txt or vulnerability disclosure information present.
  4. No contact phone numbers or physical addresses found; only email contact via mailing list.
  5. No analytics or tracking services detected, indicating privacy-friendly approach.
  6. Website uses modern frontend technologies but lacks advanced SEO and accessibility features.
  7. No security headers detected; DNSSEC not enabled, representing security improvement opportunities.
Technical notes

Notes

The website uses a modern frontend technology stack including Bootstrap 4 for responsive design, jQuery for scripting, and FontAwesome for icons. Google Fonts are used for typography. The site is static HTML-based without a detected CMS, which reduces complexity but may limit dynamic content management. Hosting appears stable with domain registration through Gandi SAS. Performance is moderate with no explicit indicators of slow loading. Mobile optimization is good due to Bootstrap usage. Accessibility is basic, with no ARIA or advanced accessibility features detected. SEO is basic, with meta tags present but no structured data or Open Graph tags. No analytics or tracking scripts are used, indicating minimal data collection. Technical risks include lack of DNSSEC and missing security headers, which should be addressed to reduce exposure to common web threats.
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 common-lisp.net. 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 common-lisp.net.

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.