Skip to main content

Security report for werd.io

Ben Werdmuller · Media · United States

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

Security score

60/100

Risk levelMedium

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

Werd I/O is an independent media and blogging platform authored by Ben Werdmuller, focusing on topics at the intersection of technology, media, and democracy. The website operates on a reader-supported subscription model, providing thoughtful essays and articles to a general audience interested in societal and technological issues. The market position is niche but credible, with a small but engaged audience. The business is small-sized, US-based, and founded in 2013, reflecting a mature presence in independent digital media. Technically, the site is built on the Ghost CMS platform, leveraging modern web technologies including JavaScript, CSS, and Cloudflare DNS services. The site demonstrates good performance, mobile optimization, and SEO practices. However, accessibility is basic and could be improved. The technical infrastructure is modern and well-maintained, supporting a smooth user experience. From a security perspective, the site enforces HTTPS and uses clientTransferProhibited status on the domain, indicating domain transfer protection. However, DNSSEC is not enabled, and no security headers are detected, which are areas for improvement. There is no visible privacy or cookie policy, nor incident response or vulnerability disclosure information, which impacts compliance and trust. No critical vulnerabilities or exposed sensitive data were found. Overall, the website is trustworthy and professional but would benefit from enhanced privacy compliance and security best practices. Strategic recommendations include enabling DNSSEC, publishing privacy and cookie policies, adding security headers, and providing incident response contacts to improve user trust and regulatory compliance.

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

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 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 werd.io

This scan found 26 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
35
DNS health
80
Network security
100
GDPR outside view
53
Average
60

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

Werd I/O operates as a niche independent media outlet with a focus on technology, democracy, and societal issues. Its competitive advantage lies in its author-driven content and reader-supported subscription model, avoiding reliance on advertising. The business model is content subscription and community engagement. The target audience includes readers interested in thoughtful analysis of media and technology. Growth indicators include regular content updates and active social media presence on decentralized platforms like Mastodon and emerging platforms like Bluesky and Threads. The partnership ecosystem is limited but includes payment processing via Stripe and hosting via Ghost CMS. The operation is lean and focused on content quality and community support.

Security posture

The website demonstrates a moderate security maturity level with HTTPS enforced and domain transfer protection enabled. However, the absence of DNSSEC and security headers such as Content-Security-Policy or X-Frame-Options reduces the overall security posture. There is no public incident response or vulnerability disclosure information, which limits transparency and readiness for security incidents. Data protection practices are minimal, with no visible privacy or cookie policies, impacting GDPR compliance. The site does not expose sensitive data or use vulnerable libraries based on the analysis. Overall, the security posture is adequate for a small independent media site but requires improvements to meet higher compliance and security standards.

Recommendations

  1. Enable DNSSEC on the domain to improve DNS security and prevent spoofing.
  2. Publish comprehensive privacy and cookie policies to enhance GDPR and privacy compliance.
  3. Implement security headers such as Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security.
  4. Provide clear incident response and vulnerability disclosure contact information to improve transparency and trust.
  5. Enhance accessibility features to improve usability for all users and meet accessibility standards.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Ben Werdmuller
Description
Writing at the intersection of technology, media, and democracy by Ben Werdmuller
Key services
Publishing articles and essays, Subscription-based reader support
Content quality
good
Branding
consistent

Technology

Stack
JavaScript, CSS, Ghost CMS, Cloudflare DNS
Frameworks
Ghost
Platforms
Ghost CMS platform
Performance
fast
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
80/100
Good practices seen
  • HTTPS enforced
  • clientTransferProhibited domain status
  • No exposed sensitive data in HTML

Analytics and tracking

Tracking level
minimal
Privacy practices
poor

Advertising

Marketing tools
Ghost Members (subscription management), Stripe (payment processing)
Transparency
basic

Site quality

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

Key observations

  1. Website is a personal independent media/blog platform by Ben Werdmuller.
  2. Content is well structured with multiple recent posts and clear navigation.
  3. No explicit privacy, cookie, or terms of service policies found.
  4. Subscription forms collect email addresses for reader support.
  5. Social media presence includes Mastodon, Bluesky, and Threads links.
  6. Uses Ghost CMS with modern web technologies and good performance.
  7. No security headers detected; DNSSEC not enabled.
  8. No contact emails or phone numbers explicitly provided on site.
  9. No vulnerability disclosure or incident response information available.
Technical notes

Notes

The website uses Ghost CMS, a modern and popular platform for blogging and content management, ensuring a solid technical foundation. The use of Cloudflare DNS and CDN services supports performance and availability. The site loads quickly and is mobile optimized, with proper meta tags and SEO-friendly structure. JavaScript and CSS are well managed with versioning for cache control. However, the site lacks advanced accessibility features and security headers. There is no evidence of legacy or vulnerable libraries. Overall, the technical implementation is modern and efficient but could benefit from additional security and accessibility enhancements.
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 werd.io. 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 werd.io.

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.