Skip to main content

Security report for bewares.it

Markus Göllnitz · Technology · N/a

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

Security score

40/100

Risk levelHigh

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

The website bewares.it is a personal portfolio and project showcase for Markus Göllnitz, a free software developer focused on Linux mobile environments and GNOME applications. The site highlights his involvement in open source projects such as Usage, Railway, and Papers, and emphasizes his contributions to the GNOME ecosystem and mobile Linux community. The business model is centered around open source development and community engagement, targeting Linux users and free software enthusiasts. The site is small-scale, reflecting an individual developer's presence rather than a corporate entity. Technically, the website is a statically hosted, well-optimized site with modern HTML5, CSS3, and JSON-LD structured data for semantic clarity. It is mobile responsive and accessible, with fast performance and good SEO practices. No CMS or complex frameworks are detected, indicating a lightweight and maintainable infrastructure. Hosting details are not explicit but the site claims no access logs and no PII collection, enhancing privacy. From a security perspective, the site uses HTTPS and DNSSEC, which are strong indicators of secure domain and transport layers. However, it lacks explicit security headers and formal privacy or cookie policies, which are areas for improvement. No forms or data collection mechanisms are present beyond a contact email link, minimizing attack surface. The WHOIS data is consistent with the website content and owner identity, supporting legitimacy and trustworthiness. Overall, the site presents a low-risk profile with good technical and security hygiene for a personal developer site. Strategic recommendations include adding privacy and cookie policies, implementing security headers, and publishing a security.txt file to improve transparency and security posture further.

Scanned

NIS2 and GDPR posture

GDPR outside view
10/ 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 bewares.it

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
75
Security headers
15
Email security
40
DNS health
60
Network security
40
GDPR outside view
10
Average
40

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

Markus Göllnitz positions himself as a dedicated free software developer with a niche focus on mobile Linux and GNOME applications. His competitive advantage lies in his active maintenance of key GNOME apps and contributions to mobile Linux usability, supported by recognized programs like Google Summer of Code. The business model is non-commercial, community-driven, and open source-centric, relying on reputation and collaboration rather than direct revenue. The target audience includes Linux users, GNOME enthusiasts, and open data contributors. Growth indicators include ongoing project maintenance and community involvement. Partnerships such as the 'Schmiddi on Mobile' project enhance ecosystem integration. The website reflects a professional and consistent personal brand with strong trust signals.

Security posture

The website demonstrates a mature security posture for a personal project site. HTTPS and DNSSEC are properly implemented, ensuring secure communications and domain integrity. The absence of access logs and PII collection reduces privacy risks. However, the lack of security headers such as Content-Security-Policy and Strict-Transport-Security is a gap that could be exploited in advanced attacks. No vulnerability disclosure or incident response information is provided, which limits transparency in case of security events. The site does not collect user data via forms, minimizing exposure. Overall, the security culture appears cautious but could benefit from formalized policies and headers to align with best practices.

Recommendations

  1. Implement and publish a comprehensive privacy policy and cookie policy to enhance transparency and GDPR compliance.
  2. Add essential security headers including Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security to strengthen defense-in-depth.
  3. Create and host a security.txt file to facilitate responsible vulnerability disclosure and incident response communication.
  4. Consider adding explicit incident response contact channels such as security@ or abuse@ email addresses.
  5. Maintain regular audits of dependencies and update technologies to avoid potential vulnerabilities and technical debt.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Markus Göllnitz
Description
Developer of free software. Excited about Linux on mobile. Member of GNOME. Contributor to open data. Enthusiast for linked data. Passionate about photography. Physics student with interest in mathematics.
Key services
Development and maintenance of GNOME applications (Usage, Railway, Papers), Contributions to mobile Linux and GNOME projects
Content quality
good
Branding
consistent

Technology

Stack
HTML5, CSS3, JSON-LD, SVG
Platforms
Static site hosting
Performance
fast
Mobile
excellent
Accessibility
good
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enabled
  • DNSSEC enabled
  • No access logs collected
  • No PII collected or stored

Analytics and tracking

Tracking level
minimal
Privacy practices
excellent

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 portfolio and project showcase for a free software developer.
  2. No privacy or cookie policies found, but site claims no PII collection and no access logs.
  3. No forms present; no data collection beyond email contact link.
  4. Strong presence in open source and GNOME community.
  5. Site is statically hosted with good mobile optimization and accessibility.
  6. No advertising or tracking detected.
  7. WHOIS data is transparent and consistent with site content.
Technical notes

Notes

The website is built using modern, standards-compliant HTML5 and CSS3 with embedded JSON-LD structured data for semantic richness. It uses SVG images for icons and profile pictures, contributing to fast load times and scalability. The site is statically hosted, likely on a privacy-conscious platform given the claim of no access logs. Mobile optimization is excellent, with responsive design and accessibility considerations evident in the CSS and layout. No CMS or JavaScript frameworks are detected, reducing complexity and attack surface. SEO is supported by meta tags and structured data. The technical stack is minimalistic but effective, suitable for a personal portfolio and project showcase. Opportunities exist to enhance security headers and formalize privacy and security documentation.
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 bewares.it. 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 bewares.it.

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.