Skip to main content

Security report for coollabs.io

coolLabs Technologies Bt. · Technology · Iceland

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

Security score

64/100

Risk levelMedium

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

coolLabs Technologies Bt. operates a privacy-focused technology website offering free and open-source applications designed to help users control their digital footprint and enhance online privacy. The company targets a general audience interested in privacy and self-hosting solutions, positioning itself as a niche provider with a strong community presence and open-source ethos. Key services include Coolify, a self-hosting platform, and other privacy-friendly tools such as Fonts and Safetyper. The business model revolves around open-source software, community engagement, and sponsorships. Technically, the website is built using modern frameworks like Astro, hosted with Cloudflare DNS and CDN services, and employs privacy-respecting analytics via Plausible. The site demonstrates good performance, mobile optimization, and accessibility, with a clean and professional design. However, some improvements could be made in security headers and cookie consent mechanisms. From a security perspective, the site uses HTTPS with a strong SSL configuration and domain transfer protections. The WHOIS data shows privacy protection consistent with the company's privacy focus and domain age appropriate for its business maturity. No critical vulnerabilities or exposed sensitive data were detected, though the absence of security headers and explicit security policies suggests room for enhancement. Overall, coolLabs presents a trustworthy and professional online presence with a solid technical foundation and privacy-centric approach. Strategic recommendations include enabling DNSSEC, adding security headers, implementing cookie consent, and publishing formal security and incident response policies to further strengthen compliance and user trust.

Scanned

NIS2 and GDPR posture

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

    • 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 coollabs.io

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
72
Security headers
15
Email security
65
DNS health
80
Network security
100
GDPR outside view
53
Average
64

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

coolLabs operates in the technology sector with a focus on privacy and open-source software. Its market positioning is niche but growing, supported by a community of over 12,000 members on Discord and active GitHub repositories. The business model leverages open-source projects, sponsorships, and community engagement rather than direct sales. The company targets privacy-conscious users and developers interested in self-hosting and digital footprint control. Partnerships with related projects like Coolify enhance its ecosystem. The company was founded in 2018 and is based in Iceland, aligning with its privacy emphasis. Growth indicators include multiple active projects and a consistent brand presence across platforms.

Security posture

The security posture of coolLabs is solid but not exhaustive. HTTPS is enforced with a good SSL configuration, and domain transfer protections are in place. However, the absence of DNSSEC and security headers such as Content-Security-Policy or X-Frame-Options reduces the overall security hardening. No incident response or security policy pages were found, indicating potential gaps in formal security governance. The use of privacy-friendly analytics and lack of exposed sensitive data are positive indicators. The WHOIS privacy protection is justified given the business focus on privacy. Overall, the site is secure for general use but could benefit from enhanced security controls and transparency.

Recommendations

  1. Enable DNSSEC to improve domain name system security and prevent spoofing.
  2. Implement standard security headers like Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security.
  3. Add a cookie consent banner and detailed cookie policy to comply with privacy regulations.
  4. Publish a formal security policy and incident response plan accessible to users.
  5. Consider adding terms of service to clarify user rights and obligations.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
coolLabs Technologies Bt.
Description
Free and open-source applications and services built for your online safety, focusing on controlling digital footprint and privacy.
Key services
Coolify - self-hosting platform, Serverless Horrors - blog, Fonts - privacy-friendly Google Fonts replacement, Jata - todo app, Safetyper - Grammarly alternative
Content quality
good
Branding
consistent

Technology

Stack
Astro, Cloudflare DNS, Plausible Analytics
Frameworks
Astro
Performance
fast
Mobile
good
Accessibility
good
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • Domain status clientTransferProhibited

Analytics and tracking

Services
Plausible Analytics
Tracking level
minimal
Privacy practices
good

Advertising

Tracking pixels
Plausible Analytics
Transparency
basic

Site quality

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

Key observations

  1. Website is fully accessible with no blocking or WAF challenges.
  2. Strong focus on privacy and open-source software.
  3. No direct contact emails or phone numbers found on main site; contact via linked Coolify site.
  4. No cookie consent banner or explicit cookie policy found.
  5. No terms of service page detected.
  6. Good mobile responsiveness and modern design.
  7. Use of privacy-friendly analytics (Plausible).
  8. No security.txt or vulnerability disclosure page found.
  9. WHOIS privacy protection used, justified by business nature.
  10. No explicit security headers detected in HTML content.
Technical notes

Notes

The website uses a modern tech stack centered on Astro for static site generation, with Cloudflare providing DNS and likely CDN services. The site loads quickly and is mobile optimized with responsive design. SEO is well addressed with comprehensive meta tags and Open Graph data. The use of Plausible Analytics reflects a commitment to privacy. No CMS was detected, indicating a custom or static site approach. The technical infrastructure is robust with minimal technical debt, though the lack of security headers and cookie consent mechanisms are notable gaps. Overall, the technical implementation supports a professional and performant user experience.
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 coollabs.io. 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 coollabs.io.

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.