Skip to main content

Security report for lemonsh.moe

Technology · Poland

Medium risk. 5 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

The website lemonsh.moe is a personal portfolio and blog site operated by an individual named lemonsh, a technology enthusiast from Poland. The site focuses on topics such as *nix operating systems, networking, programming, and retro-computing, with additional interests in music, cycling, photography, and graphic design. The site serves as a platform to showcase projects, share blog content, and provide contact information for community engagement. It is positioned as a niche personal tech presence rather than a commercial business. Technically, the website is built using the Zola static site generator and hosted with Cloudflare DNS services. The tech stack includes Rust, C, C#, Java, HTML/CSS, Bash, and some JavaScript, reflecting the owner's programming skills. The site is served over HTTPS with a good SSL configuration but lacks DNSSEC and security headers. Performance and mobile optimization are moderate to basic, with no detected analytics or tracking scripts, indicating a privacy-conscious approach. From a security perspective, the site benefits from HTTPS and WHOIS privacy protection, which is justified for a personal site. However, it lacks formal privacy, cookie, or terms of service policies, and no incident response or vulnerability disclosure information is provided. No security headers are detected, and no forms or data collection mechanisms are present, reducing attack surface but also limiting user interaction. The site content is safe for general audiences with no adult or questionable material. Overall, the website demonstrates a good level of professionalism and technical competence for a personal project. The main risks relate to missing privacy and security policies and the absence of security headers. Strategic improvements in these areas would enhance trust and compliance. The domain registration is legitimate and consistent with the site’s nature, with no suspicious indicators.

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

    • 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 lemonsh.moe

This scan found 22 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
30
Email security
70
DNS health
60
Network security
100
GDPR outside view
50
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

Lemonsh.moe operates as a personal technology portfolio and blog targeting technology enthusiasts, programmers, and networking hobbyists. The business model is non-commercial, focusing on community engagement and knowledge sharing. The site leverages partnerships with like-minded individuals and networks such as dn42 and friends' websites, forming a small ecosystem of tech collaborators. The domain age and WHOIS privacy protection align with a personal project started in 2021. Revenue streams are not evident, consistent with a personal site. Growth indicators include active project maintenance and open source code availability. The site’s competitive advantage lies in the owner’s technical expertise and niche interests in retro-computing and networking.

Security posture

The security posture of lemonsh.moe is moderate. The site uses HTTPS with a good SSL configuration and benefits from WHOIS privacy protection. However, it lacks DNSSEC and important security headers such as Content-Security-Policy and X-Frame-Options. No forms or user input fields reduce exposure to injection attacks, but the absence of privacy and cookie policies indicates compliance gaps. No incident response or vulnerability disclosure mechanisms are present, limiting readiness for security incidents. The site does not use analytics or tracking, reducing privacy risks. Overall, the site is low risk but could improve by implementing security headers, formal policies, and incident response contacts.

Recommendations

  1. Enable DNSSEC on the domain to improve DNS security and integrity.
  2. Implement and publish privacy and cookie policies to enhance compliance and user trust.
  3. Add security headers such as Content-Security-Policy, X-Content-Type-Options, and X-Frame-Options to harden the site against common web attacks.
  4. Establish an incident response contact channel and consider publishing a vulnerability disclosure policy or security.txt file.
  5. Consider improving mobile optimization and accessibility to enhance user experience and SEO.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Description
Personal website of lemonsh, a tech enthusiast from Poland interested in *nix operating systems, networking, programming, retro-computing, electronics, music, cycling, photography, and graphic design. Mainly codes in Rust and maintains a network on dn42.
Key services
Technical projects, Blog content, Network co-maintenance
Content quality
good
Branding
consistent

Technology

Stack
Rust, C#, Java, HTML, CSS, Bash, x86 ASM, JavaScript, Alpine Linux
Frameworks
Zola
Performance
moderate
Mobile
basic
Accessibility
basic
SEO
basic

Security

Observed score
75/100
Good practices seen
  • HTTPS enabled
  • No exposed sensitive data in HTML
  • Use of privacy protection in WHOIS

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. No privacy, cookie, or terms of service policies found.
  2. No forms or data collection mechanisms detected.
  3. No security.txt or vulnerability disclosure found.
  4. Website is a personal portfolio and blog with technical content.
  5. No advertising or tracking scripts detected.
  6. Site uses HTTPS and Cloudflare DNS but lacks DNSSEC.
  7. WHOIS privacy protection is enabled and justified.
  8. Content is safe and suitable for general audiences.
Technical notes

Notes

The website is built using the Zola static site generator, indicating a modern and lightweight technical infrastructure. The tech stack includes multiple programming languages reflecting the owner's skills, with Rust as the primary language. Hosting is via Cloudflare DNS and nameservers, providing reliable DNS service but lacking DNSSEC. The site uses HTTPS with a good SSL configuration, but no advanced security headers are detected. Performance is moderate with basic mobile optimization and accessibility. No analytics or tracking scripts are present, indicating a privacy-focused approach. The site source code is publicly available on GitHub, supporting transparency and community trust. Overall, the technical implementation is solid for a personal site but could benefit from enhanced security and compliance features.
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 lemonsh.moe. 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 lemonsh.moe.

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.