Skip to main content

Security report for envs.net

envs.net · Technology · N/a

Medium risk. 3 critical or high findings in Security headers and GDPR outside view.

Security score

68/100

Risk levelMedium

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

envs.net is a small, community-driven platform offering a shared Linux environment and a suite of self-hosted open source services tailored for Linux enthusiasts, programmers, and sysadmins. The platform emphasizes minimalism, non-commercial use, and collaboration, providing services such as shell accounts, file hosting, collaborative editing, microblogging, and federated social networking. The website and domain have been active since 2018, reflecting a stable and consistent presence in the niche Linux community space. Technically, envs.net runs on Debian GNU/Linux 11 and integrates multiple open source platforms like Gitea, Matrix, Pleroma, and Cryptpad. The website is well-structured with good SEO practices and basic mobile optimization. No advanced CMS or commercial hosting provider is evident, suggesting a self-managed infrastructure. Performance is moderate, suitable for the community's needs. From a security perspective, the site uses HTTPS and has domain transfer protections but lacks DNSSEC and security headers, which are recommended improvements. No cookie consent mechanism is present despite having a privacy policy, indicating partial privacy compliance. No incident response or vulnerability disclosure policies are published, which could be enhanced to improve trust and security posture. Overall, envs.net presents a trustworthy, privacy-respecting community platform with a solid technical foundation but could benefit from enhanced security practices and compliance measures to strengthen its position and user confidence.

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

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

This scan found 17 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
95
Security headers
65
Email security
70
DNS health
85
Network security
40
GDPR outside view
53
Average
68

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

envs.net occupies a niche market serving Linux and open source enthusiasts with a non-commercial, community-oriented business model. Its competitive advantage lies in offering a broad range of self-hosted services under one umbrella, fostering collaboration and shared resources. Revenue streams are likely minimal or donation-based, as indicated by the donate page. The target customers are technically skilled users seeking free shell accounts and related services. Growth indicators include a sizable user base of over 1,100 accounts and active online users. The platform's ecosystem includes federated social networks and decentralized communication tools, positioning it well within the open source community. Strategic observations suggest focusing on enhancing security and compliance to maintain and grow trust among users.

Security posture

The security maturity of envs.net is moderate. HTTPS is enforced, and domain transfer is protected, but DNSSEC is not enabled, and no security headers are detected, which are areas for improvement. The absence of published security policies, incident response plans, and vulnerability disclosure mechanisms indicates limited formal security governance. No exposed sensitive data or vulnerable libraries were detected in the HTML content. Privacy compliance is partial, with a privacy policy present but no cookie consent mechanism. The platform's open source nature and community focus suggest a security culture based on transparency and collaboration but would benefit from formalizing security processes and enhancing technical controls.

Recommendations

  1. Enable DNSSEC on the domain to improve DNS security and prevent spoofing.
  2. Implement standard security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options.
  3. Add a cookie consent banner or mechanism to comply with privacy regulations.
  4. Publish a formal security policy and incident response plan accessible on the website.
  5. Establish a vulnerability disclosure policy and provide a security.txt file for transparency.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
envs.net
Description
envs.net is a minimalist, non-commercial shared linux system and will always be free to use. It is a community of linux lovers, sysadmins, programmers and users who like to build webpages, write blogs, chat online, play console games and more.
Key services
shell accounts, file hosting and url shortener (envs.sh), collaborative real time editing (cryptpad), twtxt microblogging registry, self-hosted git service (gitea), collaborative markdown (hedgedoc), secure decentralized communication (matrix), federated social network (pleroma), graphical pastebin (privatebin), privacy-respecting metasearch engine (searxng)
Content quality
good
Branding
consistent

Technology

Stack
Debian GNU/Linux 11, HTML5, CSS, Fork Awesome icons, Gitea, Cryptpad, Matrix, Pleroma, PrivateBin, SearxNG, HedgeDoc
Platforms
Linux, Self-hosted services
Performance
moderate
Mobile
basic
Accessibility
basic
SEO
good

Security

Observed score
70/100
Good practices seen
  • HTTPS enabled
  • clientTransferProhibited domain status

Analytics and tracking

Tracking level
minimal
Privacy practices
good

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-driven, non-commercial Linux environment platform.
  2. No WAF or blocking detected; content fully accessible.
  3. No cookie consent mechanism present despite privacy policy.
  4. No explicit security policies or incident response info published.
  5. DNSSEC not enabled, which is a minor security gap.
  6. WHOIS data is transparent and consistent with website claims.
  7. No advertising or tracking detected, indicating privacy respect.
  8. Large active user base with many shell accounts.
  9. Multiple self-hosted open source services integrated.
  10. No adult or questionable content detected.
Technical notes

Notes

envs.net is built on a solid Debian GNU/Linux 11 base with a collection of well-known open source services integrated into the platform. The website uses standard HTML5 and CSS with Fork Awesome icons, indicating a lightweight and maintainable front-end. The absence of heavy frameworks or CMS suggests low technical debt and ease of maintenance. Performance is moderate, likely due to self-hosted infrastructure and community scale. Mobile optimization and accessibility are basic but functional. Opportunities exist to modernize the tech stack with enhanced security headers and improved privacy compliance mechanisms. Technical risks are low but include potential DNS spoofing due to lack of DNSSEC and limited formal security governance.
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 envs.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 envs.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.