Skip to main content

Security report for flufftech.net

Other · N/a

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

Security score

53/100

Risk levelMedium

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

The website flufftech.net is a personal blog and online presence of an individual known as 'rail' who identifies as a fox on the internet. The site focuses on sharing personal interests, blog posts, and community engagement through links to social and code repositories. It is a small-scale, niche personal site with a consistent branding theme and a friendly, informal tone. The business model is primarily content sharing with voluntary support via Ko-Fi. Technically, the site is built using the Zola static site generator, hosted with Cloudflare DNS and registrar services, and demonstrates good performance and mobile optimization. Security posture is adequate with HTTPS enforced and no visible vulnerabilities, though improvements such as enabling DNSSEC and adding security headers are recommended. Privacy compliance is lacking as no privacy or cookie policies are present, and no contact information or incident response details are provided. Overall, the site is safe, trustworthy for general audiences, and free from adult or questionable content. The domain registration is consistent with the website's nature and age, supporting legitimacy. Strategic recommendations include enhancing privacy compliance, adding security policies, and improving trust signals through contact information and vulnerability disclosure mechanisms.

Scanned

NIS2 and GDPR posture

GDPR outside view
50/ 100 · Medium
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. 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';…

  2. GDPR outside view

    These are the privacy signals visitors and data protection authorities look for under GDPR.

    • High

      No Privacy Policy found

      GDPR requires a clear and accessible privacy policy

      What to do: Add a comprehensive privacy policy page and link to it prominently

    • 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

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

Keep watching flufftech.net

This scan found 23 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
75
Security headers
15
Email security
70
DNS health
70
Network security
40
GDPR outside view
50
Average
53

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

Flufftech.net operates as a personal blog targeting a niche community interested in technology, personal expression, and the fediverse. The site leverages open source tools and promotes transparency through source code availability. Revenue streams appear limited to voluntary donations via Ko-Fi. The site maintains a network of related community sites through badges and links, indicating active participation in a broader ecosystem. The business model is informal and content-driven, with no commercial or enterprise scale operations. Growth indicators are limited but the site shows consistent branding and engagement with like-minded communities. Partnerships are informal and community-based rather than corporate. Overall, the site serves as a personal platform rather than a commercial business.

Security posture

The security posture of flufftech.net is moderate to good. The site uses HTTPS, which is mandatory for secure communications. No forms or input fields reduce the attack surface. No security headers were detected in the HTML content, which is a gap that could be addressed to improve protection against common web attacks. DNSSEC is not enabled, which is a recommended security enhancement. No privacy or cookie policies are present, indicating potential compliance gaps with GDPR or similar regulations. No incident response or vulnerability disclosure information is provided, limiting transparency in security management. No exposed sensitive data or vulnerable libraries were detected. Overall, the site is low risk but could benefit from implementing standard security best practices and compliance documentation.

Recommendations

  1. Enable DNSSEC on the domain to enhance DNS security and prevent spoofing.
  2. Implement standard security headers such as Content-Security-Policy, X-Content-Type-Options, and Strict-Transport-Security.
  3. Publish a privacy policy and cookie policy to improve GDPR and privacy compliance.
  4. Add a security.txt file to provide clear vulnerability disclosure and incident response contact information.
  5. Provide clear contact information to improve trust and facilitate communication.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Description
Personal website/blog of an individual named 'rail' who identifies as a fox on the internet with interests in computers and networks. The site includes blog posts, about me section, and links to social and code repositories.
Key services
Blog posts, Personal information sharing, Social and code repository links
Content quality
good
Branding
consistent

Technology

Stack
HTML5, CSS3, Zola static site generator
Performance
fast
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
80/100
Good practices seen
  • HTTPS enforced (implied by URL and Cloudflare registrar)
  • No forms or inputs detected to be vulnerable
  • No exposed sensitive data

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
moderate

Key observations

  1. Personal blog website with a niche audience
  2. No privacy, cookie, or terms of service policies found
  3. No contact emails or phone numbers explicitly provided
  4. No forms or data collection mechanisms present
  5. No security.txt or vulnerability disclosure information
  6. Good use of Creative Commons licensing and open source code transparency
  7. No advertising or tracking technologies detected
  8. Website is fast, mobile optimized, and well structured
  9. No adult or questionable content detected
  10. No WAF or blocking mechanisms detected
Technical notes

Notes

The website is built using the Zola static site generator, which is a modern and efficient tool for static content delivery. The site uses clean HTML5 and CSS3 with multiple external stylesheets for fonts, base styling, navigation, and footer. Hosting and DNS are managed via Cloudflare, providing reliable infrastructure and HTTPS support. The site loads quickly and is mobile optimized with viewport meta tags and responsive design. No JavaScript libraries or analytics scripts were detected, indicating minimal tracking and a lightweight footprint. SEO is supported by proper meta tags including Open Graph tags and an Atom feed link. Accessibility is basic but present with language and charset declarations. Overall, the technical implementation is modern, performant, and privacy-conscious but could be enhanced with accessibility improvements and security headers.
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 flufftech.net. 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 flufftech.net.

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.