Skip to main content

Security report for gultsch.de

Daniel Gultsch · Technology · N/a

High risk. 11 critical or high findings in GDPR outside view, Email security and 2 other checks.

Security score

41/100

Risk levelHigh

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

The website gultsch.de serves as a professional landing page for Daniel Gultsch, a freelance open-source software developer specializing in instant messaging, email, and open standards. The site highlights his leadership roles in projects such as Conversations and Ltt.rs and his active involvement in the XMPP Standards Foundation. The business model is focused on freelance development and community leadership within a niche technology sector. The website content is well-structured, professionally presented, and targets developers and open-source enthusiasts. Technically, the site is built using the Hugo static site generator and styled with Bootstrap 5.3.3, ensuring good performance and mobile optimization. External resources are loaded securely via HTTPS CDNs. However, no explicit security headers were detected, and SSL configuration details are not provided. The site does not employ analytics or tracking tools, reflecting a privacy-conscious approach. From a security perspective, the site demonstrates basic best practices such as resource integrity checks but lacks published security policies, incident response contacts, and privacy or cookie policies. The WHOIS data is consistent with the website's claims, showing legitimate domain registration and hosting. No suspicious patterns or privacy protection masking registrant data were found. Overall, the website is trustworthy and professional but could improve its privacy compliance and security posture by publishing relevant policies and implementing security headers.

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

11 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

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

  3. 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 gultsch.de

This scan found 28 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
42
Security headers
15
Email security
60
DNS health
65
Network security
40
GDPR outside view
25
Average
41

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

Daniel Gultsch operates as a small-scale freelance software developer with a strong focus on open-source projects related to instant messaging and communication protocols. His leadership in recognized projects and active role in the XMPP Standards Foundation position him as a niche expert with a dedicated community following. The business model relies on freelance development and community contributions rather than commercial sales. The website serves primarily as a portfolio and informational hub rather than a transactional platform. There is no evidence of partnerships, subsidiaries, or parent companies. The absence of advertising and tracking tools aligns with a privacy-respecting ethos. Growth indicators include ongoing project leadership and community engagement.

Security posture

The website exhibits a moderate security maturity level. It uses HTTPS for external resources and includes integrity attributes for scripts and stylesheets, indicating attention to resource security. However, the absence of security headers such as Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security reduces protection against common web attacks. No security or incident response policies are published, and no contact channels for security issues are provided. The lack of analytics and tracking reduces privacy risks. Overall, the security posture is adequate for an informational site but could be enhanced to protect user data and improve trust.

Recommendations

  1. Publish a comprehensive privacy policy and cookie policy to improve GDPR compliance and user trust.
  2. Implement and configure security headers including Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security.
  3. Add a security policy page with incident response contact information to demonstrate security readiness.
  4. Consider adding HTTPS enforcement and verify SSL certificate configuration to ensure secure connections.
  5. Maintain transparency by providing clear contact information including verified company emails and phone numbers.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Daniel Gultsch
Description
Freelance open-source software developer focused on instant messaging, email, open standards, and communication protocols. Project lead for Conversations and Ltt.rs, active member and chair of the XMPP Standards Foundation council.
Key services
Open-source software development, Project leadership for Conversations and Ltt.rs, Security research
Content quality
good
Branding
consistent

Technology

Stack
Hugo 0.142.0, Bootstrap 5.3.3, JavaScript, CSS
Frameworks
Bootstrap
Performance
fast
Mobile
good
Accessibility
good
SEO
good

Security

Observed score
70/100
Good practices seen
  • Use of integrity and crossorigin attributes on CSS and JS resources
  • HTTPS implied by external CDN links (jsdelivr.net, bootstrapcdn.com)

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
high

Key observations

  1. Website is a personal/professional landing page for a freelance software developer.
  2. Content is focused on open-source projects and standards involvement.
  3. No privacy, cookie, or terms of service policies found on the main page.
  4. No contact emails or phone numbers explicitly listed on the homepage; contact page referenced.
  5. No forms detected on the homepage; contact form likely on /contact/ page.
  6. No analytics or tracking scripts detected.
  7. Use of modern static site generator (Hugo) and Bootstrap framework.
  8. No advertising or affiliate marketing detected.
  9. No security policy or incident response information published.
  10. No security headers detected in provided data; SSL status unknown but external resources use HTTPS.
Technical notes

Notes

The website is built on a modern static site generator (Hugo) combined with Bootstrap for responsive design, resulting in fast loading times and good mobile optimization. The use of CDN-hosted CSS and JS with integrity checks enhances security. No CMS or dynamic backend detected, reducing attack surface. The site lacks analytics and tracking scripts, which benefits privacy but limits user behavior insights. No broken elements or errors were observed in the HTML content. Hosting is via INWX, a reputable domain registrar and hosting provider. Opportunities exist to improve security headers and SSL enforcement to reduce technical risks.
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 gultsch.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 gultsch.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.