Skip to main content

Security report for jappie.dev

N/A · Technology · N/a

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

Security score

56/100

Risk levelMedium

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

The website jappie.dev is a personal portfolio site belonging to an individual known as Jappie3, who focuses on Linux, particularly NixOS, DevOps technologies, and custom keyboard projects. The site serves as a showcase for various open source projects and technical interests, targeting a niche audience of Linux enthusiasts and developers. The content is well structured, with clear descriptions of projects and links to code repositories, but lacks formal business or corporate information. Technically, the site uses modern web standards including HTML5, CSS3, and JavaScript, with a custom font and a privacy-respecting analytics service (Plausible). The site is mobile responsive and performs well, though accessibility features are basic. No CMS or hosting provider details are evident. Security headers and HTTPS status are not confirmed from the data provided, but no forms or user input fields reduce attack surface. From a security perspective, the site shows good practices by not exposing sensitive data or using vulnerable libraries. However, the absence of security headers and privacy policies indicates room for improvement in compliance and security posture. No incident response or vulnerability disclosure mechanisms are present. The site does not appear to be blocked or protected by a WAF, allowing full content access. Overall, jappie.dev is a well-maintained personal technical site with moderate trustworthiness and good content quality. Strategic recommendations include adding privacy and cookie policies, implementing security headers, and providing clearer contact information to enhance credibility and compliance.

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

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

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

Keep watching jappie.dev

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
75
Security headers
15
Email security
70
DNS health
85
Network security
40
GDPR outside view
50
Average
56

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 site represents a personal technical portfolio rather than a commercial business entity. Its market positioning is niche, appealing to Linux and DevOps communities and keyboard enthusiasts. The business model is non-commercial, focusing on open source contributions and personal projects. There are no revenue streams or partnerships explicitly stated, though links to Radicle code forge and Nix Webring suggest community engagement. Growth indicators are limited due to the personal nature. The partnership ecosystem includes open source platforms and community networks. Strategic observations highlight the importance of formalizing privacy and security practices to build trust and potentially expand audience reach.

Security posture

The security maturity level is basic to moderate. The site avoids common vulnerabilities by not having forms or exposed sensitive data. However, the lack of security headers such as Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security reduces defense-in-depth. No vulnerability disclosure or incident response information is provided, which limits transparency and readiness. GDPR compliance is not demonstrated due to missing privacy and cookie policies. The use of Plausible Analytics indicates some privacy awareness. Overall, the security posture is adequate for a personal site but would benefit from enhancements to align with best practices and compliance requirements.

Recommendations

  1. Implement a comprehensive privacy policy and cookie policy with clear GDPR compliance statements.
  2. Add security headers including Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security to improve security posture.
  3. Establish a security.txt file or vulnerability disclosure policy to facilitate responsible reporting.
  4. Provide clear and verified contact information such as a company email address to enhance trust and communication.
  5. Regularly audit and update technical stack and dependencies to maintain security and performance.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
N/A
Description
Personal website of Jappie3, focused on Linux (NixOS), DevOps technologies, split keyboards, and programming projects.
Key services
Open source projects, NixOS configuration, Wayland tools, Keyboard firmware packaging
Content quality
good
Branding
consistent

Technology

Stack
HTML5, CSS3, JavaScript, JetBrains Mono font, Plausible Analytics
Performance
fast
Mobile
good
Accessibility
basic
SEO
basic

Security

Observed score
70/100
Good practices seen
  • No forms present to collect user input
  • No exposed sensitive data in HTML

Analytics and tracking

Services
Plausible Analytics
Tracking level
minimal
Privacy practices
basic

Advertising

Tracking pixels
Plausible Analytics
Transparency
basic

Site quality

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

Key observations

  1. Personal technical portfolio website with focus on Linux, DevOps, and keyboard projects.
  2. No privacy, cookie, or terms of service policies found.
  3. No forms or direct contact emails visible; contact via Matrix and Bluesky social links.
  4. Minimal tracking via Plausible Analytics, respecting privacy.
  5. No security headers detected in provided data; HTTPS status unknown.
  6. No business registration or company information disclosed.
  7. Website is well structured, mobile responsive, and uses modern fonts and CSS.
  8. No advertising or affiliate marketing detected.
  9. No suspicious or malicious content detected.
Technical notes

Notes

The website is built with clean, valid HTML5 and CSS3, using a custom font (JetBrains Mono) and minimal JavaScript primarily for analytics and UI enhancements. It leverages Plausible Analytics, a privacy-focused analytics platform, indicating a modern approach to user tracking. The site is mobile responsive with a grid layout and media queries for different screen sizes. No CMS or backend technologies are detected, suggesting a static site or simple hosting environment. Performance is likely fast due to minimal resources and efficient design. Accessibility is basic but could be improved with ARIA roles and semantic HTML enhancements. SEO optimization is minimal but present through proper use of headings and links.
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 jappie.dev. 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 jappie.dev.

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.