Skip to main content

Security report for geraldbinder.com

Gerald Binder · Media · Germany

High risk. 9 critical or high findings in GDPR outside view, SSL/TLS and 2 other checks.

Security score

28/100

Risk levelHigh

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

Gerald Binder's website is a personal blog primarily targeting German-speaking audiences interested in diverse topics such as chili recipes, media theory, travel, and quotes. The site operates on a WordPress platform with a modest but consistent content update history, positioning itself as a niche media outlet rather than a commercial enterprise. Technically, the site uses an Apache server with WordPress 5.0.22 and integrates social media plugins for Facebook and Twitter. However, the absence of HTTPS and modern security configurations significantly undermines the site's security posture. Privacy compliance is minimal, with a basic privacy policy page but no cookie consent mechanisms or GDPR compliance indicators. Overall, the site is functional but lacks critical security and privacy features, which poses risks to user trust and data protection.

Scanned

NIS2 and GDPR posture

GDPR outside view
18/ 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

9 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

      No HTTPS encryption

      GDPR requires appropriate security measures for personal data

      What to do: Implement SSL/TLS certificate for HTTPS

  2. SSL/TLS

    TLS encrypts the connection and proves the site is really yours. Weak or expiring certificates trigger browser warnings and put traffic at risk.

    • Critical

      No HTTPS Encryption

      Website does not use HTTPS encryption, making all data transmission vulnerable to interception

      What to do: Implement SSL/TLS certificate and redirect all HTTP traffic to HTTPS

  3. Network security

    Services reachable from the internet are the first thing attackers probe. Anything open that does not need to be should be closed.

    • Critical

      Critical Service Exposed: MySQL

      Port 3306 (MySQL) is publicly accessible - MySQL - Database server

      What to do: Immediately restrict access to MySQL using firewall or VPN

      • NIS2 21(2)(e)
      • IR 2024/2690 6.7.2(f): Implementing Regulation (EU) 2024/2690, Annex point 6.7.2(f): Network security
      • NIST CM-7: NIST SP 800-53 Rev. 5 CM-7: Least Functionality
      • NIST SC-7: NIST SP 800-53 Rev. 5 SC-7: Boundary Protection

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

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

Keep watching geraldbinder.com

This scan found 20 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. See sample alerts.

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
0
Security headers
15
Email security
50
DNS health
85
Network security
0
GDPR outside view
18
Average
28

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 · found on this site
  • 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 serves as a personal or small-scale media blog with content organized into thematic categories. It leverages social media for audience engagement but does not appear to monetize through advertising or affiliate programs. The business model is content-driven with potential for community building. The hosting provider is kasserver.com, indicating a standard shared hosting environment. The lack of detailed business information or certifications suggests a low commercial profile. The site’s market position is niche and personal, with moderate trust signals such as regular updates and social media presence.

Security posture

The security posture is weak due to the lack of HTTPS, absence of security headers, and no advanced DNS security measures like DNSSEC. The site does not implement HSTS, OCSP stapling, or session resumption, which are standard best practices. No incident response or vulnerability disclosure policies are present. The SPF record is permissive, and no security frameworks or certifications are indicated. These gaps expose the site and its visitors to potential risks such as data interception and phishing. Immediate remediation of SSL/TLS and security headers is recommended.

Recommendations

  1. Implement a valid SSL/TLS certificate and enforce HTTPS site-wide.
  2. Add security headers including Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options.
  3. Enable HSTS with includeSubDomains and preload directives.
  4. Deploy DNSSEC to enhance DNS security and harden SPF record to ~all or -all.
  5. Introduce a cookie consent mechanism and update privacy policy for GDPR compliance.
  6. Establish an incident response contact and vulnerability disclosure policy to improve security transparency.
Technical notes

Notes

The website runs on an outdated WordPress version (5.0.22) with legacy jQuery (1.12.4) and uses the Koji theme alongside the Ultimate Social Media Icons plugin. The hosting environment is Apache on a server with IP 85.13.129.6, managed by kasserver.com. Performance metrics are missing, but chunked transfer encoding and lack of caching suggest suboptimal speed. Mobile optimization is basic with responsive meta tags but no advanced accessibility features. SEO is minimal with basic meta tags and no structured data like JSON-LD or Open Graph. The site would benefit from modernization of its tech stack, performance optimization, and enhanced SEO and accessibility practices.
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 geraldbinder.com. 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 geraldbinder.com.

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.