Skip to main content

Security report for blakewatson.com

Blake Watson · Technology · N/a

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

Security score

62/100

Risk levelMedium

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

Blake Watson's website is a personal site showcasing his work as a software engineer, hobbyist game developer, and writer. The site serves as a platform for sharing journal entries, microblogs, projects, and assistive technology gear information. It targets a general audience interested in technology and personal insights. The business model is primarily personal branding and content sharing, with a niche focus on assistive technology and software development. The domain has been active since 2005, supporting the site's credibility and longevity. Technically, the website is built as a static site using modern web standards including HTML5, CSS, and JavaScript. It leverages Cloudflare for DNS and possibly CDN services, and uses Fathom Analytics for privacy-focused visitor tracking. The site is mobile optimized, accessible, and performs well with fast loading times. No CMS or major frameworks are detected, indicating a custom or lightweight build. From a security perspective, the site uses HTTPS with a good SSL configuration and has domain transfer protections enabled. However, it lacks DNSSEC and security headers such as Content-Security-Policy or Strict-Transport-Security. There are no visible vulnerabilities or exposed sensitive data. Privacy compliance is weak due to the absence of privacy and cookie policies. No contact information or incident response channels are provided, limiting user trust and support options. Overall, the site is trustworthy and professional but would benefit from enhanced privacy compliance, security headers, and published policies to improve user trust and regulatory adherence. The risk level is low given the personal nature of the site and lack of sensitive data collection, but improvements are recommended to align with best practices.

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

8 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 blakewatson.com

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. 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
70
DNS health
60
Network security
100
GDPR outside view
50
Average
62

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 represents an individual professional rather than a corporate entity, focusing on personal content and community engagement. Market positioning is niche, targeting software developers, hobbyists, and those interested in assistive technology. The business model is content-driven without direct monetization visible. Growth indicators include regular content updates and active social media presence. The partnership ecosystem is minimal, with external links primarily to social and code hosting platforms. Strategic observations suggest potential for expanding audience engagement through enhanced content policies and clearer contact channels.

Security posture

The security maturity level is moderate. HTTPS is enforced, and domain transfer protections are in place, indicating basic security hygiene. The absence of DNSSEC and security headers represents gaps that could be exploited in certain attack scenarios. No vulnerability disclosure or incident response information is provided, which could delay response to security incidents. Data protection practices are minimal, with no privacy or cookie policies published. The site does not collect sensitive user data, reducing risk exposure. Overall, the security posture is adequate for a personal site but should be improved to meet higher standards.

Recommendations

  1. Enable DNSSEC to protect against DNS spoofing and improve domain security.
  2. Implement and publish a comprehensive privacy policy and cookie policy to enhance GDPR compliance and user trust.
  3. Add security headers such as Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security to harden the site against common web attacks.
  4. Provide clear contact information and establish an incident response channel to improve transparency and support.
  5. Consider publishing a vulnerability disclosure policy or security.txt file to facilitate responsible security reporting.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Blake Watson
Description
Personal website of Blake Watson, a software engineer, side-project enthusiast, hobbyist game developer, sometimes writer, and full-time wheelchair user.
Key services
Personal blog and journal, Microblog updates, Project showcases, Assistive technology gear information
Content quality
good
Branding
consistent

Technology

Stack
HTML5, CSS, JavaScript, Cloudflare DNS, Fathom Analytics
Performance
fast
Mobile
good
Accessibility
good
SEO
good

Security

Observed score
80/100
Good practices seen
  • HTTPS enabled
  • Domain status clientTransferProhibited
  • No exposed sensitive data in HTML
  • No vulnerable libraries detected

Analytics and tracking

Services
Fathom Analytics
Tracking level
minimal
Privacy practices
poor

Advertising

Tracking pixels
Fathom Analytics
Transparency
basic

Site quality

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

Key observations

  1. Personal website with clear author identity
  2. No privacy or cookie policies found
  3. No contact emails or phone numbers publicly listed
  4. No forms detected on the site
  5. Use of modern web technologies and analytics
  6. No security.txt or vulnerability disclosure policy
  7. No security headers detected in provided data
  8. No suspicious or malicious content detected
Technical notes

Notes

The website is a well-structured static site using modern web technologies without reliance on heavy frameworks or CMS platforms. Hosting appears to be supported by Cloudflare DNS and CDN services, contributing to fast performance and good availability. The use of Fathom Analytics indicates a privacy-conscious approach to visitor tracking. The site is mobile optimized and accessible, with clear navigation and consistent branding. Technical risks are low but include the lack of DNSSEC and security headers, which are recommended for improved security posture. There is no evidence of technical debt or outdated libraries.
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 blakewatson.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 blakewatson.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.