Skip to main content

Security report for drewdevault.com

Technology · N/a

Medium risk. 6 critical or high findings in Email security, Security headers and 2 other checks.

Security score

55/100

Risk levelMedium

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

Drew DeVault's website is a personal blog primarily focused on technology, free and open source software, and programming language development. The site serves as a platform for sharing articles, project announcements, and personal insights, targeting developers and open source enthusiasts. The business model appears to be centered around content sharing and community engagement, with donation support via Liberapay. The website has a consistent and professional design, with high-quality content and clear navigation, making it a trusted resource within its niche. Technically, the site is built using the Hugo static site generator, delivering fast and mobile-optimized content without reliance on complex backend systems. The absence of forms and tracking technologies suggests a privacy-conscious approach. However, the lack of explicit security headers and privacy policies indicates room for improvement in security and compliance maturity. The domain is well-established, registered since 2010, and WHOIS data aligns with the website's personal nature, supporting legitimacy. From a security perspective, the site lacks visible security headers and formal policies such as privacy or cookie policies, which could expose it to compliance risks, especially under GDPR. No incident response or vulnerability disclosure mechanisms are present, which may hinder effective security communication. Despite these gaps, the static nature of the site and absence of user input reduce attack vectors. Overall, the security posture is moderate but could benefit from enhancements. The overall risk assessment is low given the site's personal blog nature and limited attack surface. Strategic recommendations include implementing privacy and cookie policies, enabling DNSSEC, adding security headers, and establishing vulnerability disclosure channels to enhance trust and compliance. These steps will improve the site's security posture and align it better with modern web standards.

Scanned

NIS2 and GDPR posture

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

6 findings rated critical or high. Fix these first.

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

  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 X-Frame-Options header

      Prevents clickjacking attacks

      What to do: Add "X-Frame-Options: DENY" or "X-Frame-Options: SAMEORIGIN"

  3. GDPR outside view

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

    • 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

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

Keep watching drewdevault.com

This scan found 24 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
30
Email security
60
DNS health
70
Network security
40
GDPR outside view
53
Average
55

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

The website operates as a personal blog by Drew DeVault, focusing on free software, open source, and technology commentary. It occupies a niche market segment catering to developers and open source advocates. The business model is content-driven with community support via donations, lacking commercial transactions or large-scale operations. The site demonstrates consistent content updates and a loyal audience base. There is no evidence of partnerships or subsidiaries. The blog's competitive advantage lies in its authoritative voice and technical depth. Growth indicators include regular publishing and engagement with open source projects. The ecosystem includes links to SourceHut and Liberapay, reflecting alignment with privacy and open source values.

Security posture

The website exhibits a moderate security maturity level. It uses HTTPS (implied by domain and modern standards, though SSL configuration details are not provided), but lacks DNSSEC and security headers such as Content-Security-Policy or Strict-Transport-Security. No privacy or cookie policies are present, indicating compliance gaps with GDPR and similar regulations. The absence of incident response contacts or security.txt files limits the ability to report vulnerabilities. The static site architecture and lack of forms reduce exposure to common web vulnerabilities. No vulnerable libraries or exposed sensitive data were detected. Overall, the security culture appears minimal but sufficient for a personal blog, with room for improvement in formal security and privacy practices.

Recommendations

  1. Implement a comprehensive privacy policy and cookie policy to improve GDPR compliance.
  2. Enable DNSSEC on the domain to enhance DNS security and prevent spoofing.
  3. Add essential security headers such as Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security.
  4. Create and publish a security.txt file to provide clear vulnerability disclosure and incident response contacts.
  5. Consider adding minimal analytics with privacy-respecting configurations to monitor site usage without compromising user privacy.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Description
Personal blog of Drew DeVault featuring articles on technology, free and open source software, programming languages, and related topics.
Key services
Blog articles, Open source project announcements, Donation support via Liberapay
Content quality
excellent
Branding
consistent

Technology

Stack
Hugo static site generator, CSS, HTML5
Performance
fast
Mobile
good
Accessibility
good
SEO
good

Security

Observed score
50/100

Analytics and tracking

Tracking level
minimal
Privacy practices
poor

Advertising

Transparency
poor

Site quality

Design
excellent
User experience
excellent
Content relevance
excellent
Navigation
excellent
Professionalism
excellent
Trustworthiness
high

Key observations

  1. Website is a personal blog focused on free software and technology topics.
  2. No privacy or cookie policies found, indicating potential compliance gaps.
  3. No security.txt or incident response information available.
  4. No forms or user input fields detected, reducing attack surface.
  5. No advertising or tracking technologies detected, indicating privacy-conscious design.
  6. WHOIS data shows domain is stable and consistent with website content.
  7. No security headers detected in provided data; SSL status unknown.
  8. Website uses Hugo static site generator, indicating a static content delivery approach.
Technical notes

Notes

The website is built using the Hugo static site generator, delivering fast and efficient content with minimal dependencies. The HTML is well-structured with valid meta tags for viewport and charset, and includes an RSS feed link. CSS is minified and served locally, indicating good performance optimization. The site is mobile-optimized with responsive design. No JavaScript frameworks or analytics scripts were detected, reflecting a minimalistic and privacy-focused approach. Hosting details are not explicit, but the domain registrar is 1API GmbH. The absence of DNSSEC and security headers suggests technical debt in security hardening. Overall, the technical infrastructure is modern, performant, and well-maintained for a personal blog.
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 drewdevault.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 drewdevault.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.