Skip to main content

Security report for beyondco.de

Beyond Code GmbH · Technology · Germany

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

Security score

64/100

Risk levelMedium

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

Beyond Code GmbH is a small technology company based in Germany specializing in software tools and educational video courses for web developers, particularly those working with PHP and Laravel. Their market position is focused on providing essential developer tools such as Laravel Herd, Tinkerwell, and Expose, alongside open source packages and developer services. The website reflects a professional and consistent brand with excellent content quality targeting web developers seeking productivity and learning resources. Technically, the site uses modern frameworks like Laravel, Livewire, and Alpine.js, hosted behind Cloudflare, but suffers from slow load times and lacks a valid SSL certificate, resulting in no HTTPS support. Security posture is weak due to missing SSL/TLS, absence of security headers, and no cookie consent mechanism, which impacts user trust and compliance. Privacy and terms of service pages are present and comprehensive, with GDPR compliance indicated. Overall, the site is functional and professional but requires urgent security improvements to protect user data and enhance trust.

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

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

    • High

      No Cookie Consent Banner found

      GDPR requires explicit consent for non-essential cookies

      What to do: Implement a cookie consent banner that appears on first visit

  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 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 beyondco.de

This scan found 21 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
85
Security headers
50
Email security
75
DNS health
55
Network security
100
GDPR outside view
18
Average
64

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

Beyond Code operates in the developer tools niche, leveraging open source and educational content to build a loyal developer community. Their business model combines software sales, video courses, and services, supported by affiliate and referral programs. The company demonstrates strong branding consistency and trust signals through open source contributions and active social media presence. Their partnership ecosystem includes integrations with Google services and email providers. Growth indicators include recent product launches and active blog content. The company targets PHP and Laravel developers globally, with a focus on macOS users for some products. Revenue streams likely include software licenses, course sales, and consulting services. Strategic observations suggest opportunities to improve technical performance and security to maintain competitive advantage.

Security posture

The current security maturity level of Beyond Code's website is low due to the absence of a valid SSL certificate and HTTPS support, which is a critical vulnerability exposing users to data interception risks. The lack of HTTP security headers and cookie consent mechanisms further weakens the security posture and compliance with privacy regulations. No explicit incident response or security policy information is found, indicating limited formal security governance. While no active vulnerabilities like Heartbleed or POODLE are detected, the missing TLS protocols and session resumption features reduce the site's resilience. The business impact includes potential loss of user trust, GDPR non-compliance risks, and exposure to man-in-the-middle attacks. Enhancing SSL configuration and implementing security best practices are essential to improve the security culture and readiness.

Recommendations

  1. Install and maintain a valid SSL/TLS certificate to enable HTTPS across the entire site.
  2. Implement HTTP security headers such as HSTS, Content-Security-Policy, and X-Frame-Options to protect against common web attacks.
  3. Add a cookie consent banner/mechanism to comply with GDPR and enhance user privacy transparency.
  4. Optimize website performance to reduce load times, improving user experience and SEO.
  5. Develop and publish a formal security policy and incident response plan to demonstrate security governance and readiness.
Technical notes

Notes

The website is built on a modern PHP/Laravel stack with frontend technologies including Livewire and Alpine.js, indicating a contemporary development approach. Hosting is managed via Cloudflare, providing CDN and DNS services. However, the lack of a valid SSL certificate and disabled TLS protocols represent significant technical debt and security risk. Performance metrics show a slow load time of over 15 seconds, likely due to resource loading inefficiencies. SEO is supported by proper meta tags and Open Graph data, but accessibility features are basic and could be improved. The site lacks a CMS indication, suggesting a custom or framework-based implementation. Technical modernization efforts should focus on SSL/TLS enablement, performance optimization, and enhanced accessibility compliance.
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 beyondco.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 beyondco.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.