Skip to main content

Security report for eps-dev.de

Lilly Schramm · Technology · Germany

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

Security score

52/100

Risk levelMedium

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

EPS-DEV is a personal portfolio website of Lilly Schramm, a young German full-stack developer showcasing her projects including Booklify, TwitterDB, and a Tor relay service. The site targets developers and tech enthusiasts interested in open source and free internet initiatives. The business model is primarily personal branding and project demonstration with open source contributions. Technically, the site is built with Angular 16.2.0, uses modern CSS frameworks like Tailwind, and is hosted with Cloudflare DNS. The site is performant, mobile optimized, and uses minimal tracking via Umami analytics. Security posture is good with HTTPS enforced and no exposed sensitive data, but lacks security headers and formal policies. Overall, the site is trustworthy and professional but would benefit from adding privacy, cookie, and security policies to improve compliance and user trust.

Scanned

NIS2 and GDPR posture

GDPR outside view
25/ 100 · Critical
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

8 findings rated critical or high. Fix these first.

  1. GDPR outside view

    These are the privacy signals visitors and data protection authorities look for under GDPR.

    • Critical

      EU business without adequate privacy measures

      EU businesses are subject to strict GDPR requirements

      What to do: Implement comprehensive GDPR compliance including privacy policy, cookie consent, and data protection measures

    • 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

  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 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';…

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

Keep watching eps-dev.de

This scan found 25 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
20
Email security
85
DNS health
70
Network security
40
GDPR outside view
25
Average
52

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

The website positions Lilly as an independent developer with niche projects targeting manga collectors and social media analytics. The projects demonstrate technical skill and community engagement, such as running a Tor relay to support internet freedom. The business model is non-commercial and focused on personal growth and open source sharing. The site links to multiple external domains related to her projects and social presence, indicating a well-connected ecosystem. Growth potential lies in expanding Booklify and maintaining community trust through transparency and security improvements.

Security posture

The site enforces HTTPS and avoids exposing sensitive data, which is positive. However, it lacks key security headers like Content-Security-Policy and X-Frame-Options, which could mitigate certain attack vectors. No incident response or vulnerability disclosure information is provided, limiting readiness for security events. Privacy compliance is weak due to absence of privacy and cookie policies. The use of PGP key for contact is a strong trust signal. Overall, security maturity is moderate but can be improved with formal policies and headers.

Recommendations

  1. Implement and publish a comprehensive privacy policy and cookie policy with consent mechanisms.
  2. Add security headers such as Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security.
  3. Provide incident response and vulnerability disclosure contact information to enhance security transparency.
  4. Improve accessibility features and SEO metadata for better user experience and discoverability.
  5. Regularly audit third-party scripts and analytics for privacy compliance and minimal tracking.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Lilly Schramm
Description
Personal portfolio website of Lilly Schramm, a 20-year-old Full-Stack Developer from Germany showcasing personal projects and services.
Key services
Booklify - manga collection management and sharing, TwitterDB - Twitter statistics project (frozen), Tor Relay - supporting free internet access
Content quality
good
Branding
consistent

Technology

Stack
Angular 16.2.0, Font Awesome 6, Tailwind CSS, Cloudflare DNS
Frameworks
Angular
Performance
fast
Mobile
good
Accessibility
basic
SEO
basic

Security

Observed score
75/100
Good practices seen
  • HTTPS enforced
  • No exposed sensitive data in HTML
  • Use of PGP key for contact

Analytics and tracking

Services
Umami
Tracking level
minimal
Privacy practices
poor

Advertising

Tracking pixels
umami (u.cd0.eu)
Transparency
basic

Site quality

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

Key observations

  1. Personal portfolio website with clear developer identity
  2. No privacy or cookie policies found
  3. No terms of service or security policies present
  4. Contact info includes email and PGP key but no phone or physical address
  5. Uses modern Angular framework and good design practices
  6. Includes links to multiple external projects and social platforms
  7. No signs of malicious or adult content
  8. Minimal tracking via Umami analytics
  9. No WAF or blocking detected
Technical notes

Notes

The website uses a modern Angular framework (v16.2.0) with Tailwind CSS and Font Awesome for UI elements. It is served with Cloudflare DNS, indicating good hosting infrastructure. The site loads quickly and is mobile responsive. However, no CMS is detected, indicating a custom or static site approach. The use of Umami analytics shows a preference for privacy-friendly tracking. There is no evidence of technical debt or outdated libraries. Opportunities exist to enhance SEO and accessibility compliance. Overall, the technical implementation is solid and modern.
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 eps-dev.de. 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 eps-dev.de.

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.