Skip to main content

Security report for envs.sh

Technology · Germany

Medium risk. 5 critical or high findings in Email security, Security headers and 1 other check.

Security score

64/100

Risk levelMedium

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

envs.sh is a small technology service providing file hosting and URL shortening functionalities primarily targeted at developers and users seeking lightweight, ephemeral file sharing solutions. The service emphasizes decentralization and open source principles, encouraging users to self-host and contribute via its public GitHub repository. The website content is well-structured, providing clear usage instructions and an explicit acceptable use policy to prevent misuse. Technically, the site uses basic HTML and CSS with external stylesheets and icon fonts. It supports HTTPS and employs token-based file management for security. However, DNSSEC is not enabled, and no advanced security headers are detected, indicating room for improvement in security hardening. The site does not implement privacy or cookie policies, which may pose compliance risks. From a security perspective, the service enforces file type restrictions and expiration controls, with a clear abuse contact channel. No WAF or blocking mechanisms are detected, and no adult or questionable content is present, making the site safe for general audiences. The domain registration data is consistent and appropriate for the service age and type, enhancing trustworthiness. Overall, envs.sh presents a functional and transparent service with moderate technical maturity and security posture. Strategic improvements in privacy compliance, security headers, and DNS security would enhance its trust and resilience.

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

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

    • 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.sh

This scan found 18 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
60
DNS health
75
Network security
40
GDPR outside view
50
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

Breach exposure

Leaked credentials and lookalike domains from OffSeq Breach. The counts are free; the detailed lists are paid add-ons.

Dark web exposure

Add-on

Leaked records that mention envs.sh, from OffSeq Breach.

No leaked records found

Breach holds no records for envs.sh right now. New leaks arrive continuously, so monitoring on Breach alerts you if that changes.

Monitor on Breach (opens in a new tab)

Technical appendix

Business context, site observations and technical notes gathered during the scan, and the standards behind each reference.

Business context

Business profile

envs.sh operates in a niche market of file hosting and URL shortening, differentiating itself through open source availability and decentralization advocacy. Its business model appears to be community-supported with optional donations rather than commercial monetization. The target customers are developers and privacy-conscious users needing ephemeral file sharing. The lack of advertising and tracking indicates a privacy-first approach. The service maintains a clear abuse policy and contact channels, supporting operational integrity. Its partnership with envs.net and presence on GitHub suggest a small but engaged ecosystem. Growth potential depends on community adoption and security enhancements.

Security posture

The security posture of envs.sh is moderate. HTTPS is enforced, and file upload restrictions reduce risk exposure. The use of token-based file management adds a layer of control for users. However, the absence of DNSSEC and security headers such as Content-Security-Policy and Strict-Transport-Security weakens defense-in-depth. No formal security policy or vulnerability disclosure program is published, which limits transparency and incident response readiness. The abuse contact email is clearly provided, facilitating incident reporting. Overall, the site is secure for its purpose but would benefit from adopting additional security best practices and formal policies.

Recommendations

  1. Enable DNSSEC on the domain to improve DNS security and prevent spoofing.
  2. Implement and publish a comprehensive privacy policy and cookie policy to enhance GDPR compliance.
  3. Add security headers such as Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security to harden the website against common attacks.
  4. Establish a formal vulnerability disclosure program or security.txt file to encourage responsible reporting of security issues.
  5. Consider adding accessibility and mobile optimization improvements to enhance user experience across devices.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Description
envs.sh is a file hosting and URL shortening service branded as 'THE NULL POINTER'. It allows users to upload files or shorten URLs via HTTP POST requests, with options for expiration and secret tokens for management.
Key services
File hosting with expiration control, URL shortening, File management via tokens
Content quality
good
Branding
moderate

Technology

Stack
HTML5, CSS (external stylesheets), curl (usage instructions), Fork Awesome icons
Performance
moderate
Mobile
basic
Accessibility
basic
SEO
basic

Security

Observed score
65/100
Good practices seen
  • HTTPS enforced (implied by usage of https:// in URLs)
  • Domain status clientTransferProhibited
  • No Java archive file uploads allowed
  • Token-based file management for deletion and expiration

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 fully accessible with no blocking or WAF challenges
  2. No privacy or cookie policies found, indicating potential compliance gaps
  3. Clear and detailed usage instructions for file hosting and URL shortening
  4. Open source code repository linked, promoting transparency
  5. Explicit acceptable use policy with prohibited content clearly listed
  6. Contact email for abuse and hostmaster provided
  7. No analytics or tracking scripts detected, indicating privacy-conscious design
  8. No social media links found except GitHub repository link
  9. No security.txt or vulnerability disclosure policy found
  10. No phone numbers or physical addresses provided
Technical notes

Notes

The website uses a simple but effective technical stack with HTML5 and CSS, leveraging external stylesheets and icon fonts. It supports HTTPS, ensuring encrypted communication. The site performance is moderate with no heavy scripts or tracking, contributing to fast load times. The lack of CMS or complex frameworks reduces attack surface but also limits advanced features. The site is not fully optimized for mobile or accessibility, which could be improved. Hosting details are limited but registrar and DNS servers are known. No analytics or tracking scripts are present, reflecting a privacy-conscious design. Overall, the technical implementation is solid but basic, suitable for the service scope.
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.sh. 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.sh.

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.