Skip to main content

Security report for jan-osing.de

Other · Germany

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

Security score

61/100

Risk levelMedium

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

Jan's website is a personal portfolio and social presence site for a young developer from Germany. It focuses on personal interests such as gaming, anime, open source software, and Linux distributions. The site is simple, well-structured, and provides links to various social and community platforms. The technical infrastructure is basic, relying on static HTML and CSS with Cloudflare DNS services. There is no evidence of advanced frameworks or CMS usage. Security posture is minimal with no visible security headers or policies, but no critical vulnerabilities or malicious content were detected. Privacy compliance is lacking as no privacy or cookie policies are present. Overall, the site is low risk but would benefit from improved security and compliance documentation.

Scanned

NIS2 and GDPR posture

GDPR outside view
28/ 100 · High
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. 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 Cookie Policy found

      GDPR requires clear information about cookie usage

      What to do: Add a dedicated cookie policy explaining cookie usage and purposes

  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 jan-osing.de

This scan found 24 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
30
Email security
65
DNS health
70
Network security
100
GDPR outside view
28
Average
61

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 jan-osing.de, from OffSeq Breach.

No leaked records found

Breach holds no records for jan-osing.de 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

The website represents an individual rather than a commercial entity, targeting a niche audience interested in open source, gaming, and anime communities. There is no monetization or business model evident. The site acts as a personal branding and social hub. The external links indicate active participation in open source and federated social networks. The lack of business information and certifications is consistent with a personal site. Growth potential is limited to personal reputation rather than commercial expansion.

Security posture

Security maturity is low with no explicit security policies, incident response contacts, or vulnerability disclosure mechanisms. The site uses Cloudflare DNS which provides some protection, but no security headers or HTTPS enforcement details are visible. No forms or data collection reduce attack surface. Recommendations include adding security headers, HTTPS enforcement, and privacy policies to improve compliance and trust.

Recommendations

  1. Implement and publish a privacy policy and cookie policy to improve GDPR compliance.
  2. Add security headers such as Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security.
  3. Ensure HTTPS is properly configured and enforced site-wide.
  4. Publish an incident response contact or security.txt file to facilitate vulnerability reporting.
  5. Consider adding accessibility improvements and SEO enhancements for better user experience and discoverability.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Description
Personal website of Jan, a 20-year-old developer from Germany studying business informatics. Shares interests in gaming, anime, open source, Linux, and related communities.
Content quality
good
Branding
consistent

Technology

Stack
HTML5, CSS, Cloudflare DNS
Performance
moderate
Mobile
basic
Accessibility
basic
SEO
basic

Security

Observed score
50/100

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
basic
Trustworthiness
moderate

Key observations

  1. Personal website with no commercial or corporate branding
  2. No privacy, cookie, or terms of service policies found
  3. No forms or data collection mechanisms present
  4. No security or incident response policies disclosed
  5. No analytics or tracking scripts detected
  6. External links mostly to social and open source related domains
  7. No advertising or marketing tools detected
  8. WHOIS data limited but consistent with personal site
  9. No suspicious or malicious content detected
Technical notes

Notes

The website is built with static HTML and CSS, with no detected JavaScript frameworks or CMS. Hosting appears to be via Cloudflare DNS and possibly CDN services. Performance is moderate with no heavy scripts or tracking. Mobile optimization is basic but functional. SEO and accessibility are minimal but adequate for a personal site. There is opportunity to modernize with responsive design frameworks and improve metadata for SEO. No technical debt or vulnerabilities were detected in the provided content.
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 jan-osing.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 jan-osing.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.