Skip to main content

Security report for joeyh.name

Joey Hess · Technology · N/a

Medium risk. 6 critical or high findings in Security headers and GDPR outside view.

Security score

58/100

Risk levelMedium

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

The website joeyh.name is a personal technical portfolio and blog belonging to Joey Hess, a free software developer and technologist. The site features a variety of personal and technical content including blog posts, code repositories, talks, and podcasts. The business model is primarily personal branding and knowledge sharing, targeting a general audience interested in technology and free software. The site is positioned as an individual contributor's platform rather than a commercial enterprise. Technically, the site is built using the ikiwiki static site generator, with a simple HTML, CSS, and JavaScript stack. Hosting is under a domain registered with Gandi SAS, a reputable registrar. The site shows moderate performance and basic mobile optimization. SEO and accessibility are basic but functional. No advanced analytics or tracking technologies are detected, indicating a privacy-conscious approach. From a security perspective, the domain status clientTransferProhibited is a positive indicator against unauthorized domain transfers. However, the site lacks security headers, privacy and cookie policies, and vulnerability disclosure mechanisms. No HTTPS status was explicitly detected in the provided data, so SSL configuration is unknown. The site does not appear to use any WAF or security challenge mechanisms, and no vulnerabilities or suspicious patterns were found. Overall, the site is safe, trustworthy, and professionally maintained as a personal technical resource. The main risks relate to lack of formal privacy and security policies, which could be improved to enhance compliance and user trust.

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

6 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 joeyh.name

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

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

Joey Hess operates as an individual technologist and free software developer with a personal website serving as a portfolio and blog. The market positioning is that of an experienced developer sharing knowledge and projects rather than a commercial business. Revenue streams are not evident, suggesting a non-commercial or self-funded model. The target audience includes free software enthusiasts, developers, and the general tech community. The partnership ecosystem includes links to related technical sites and interviews but no formal business partnerships. Growth indicators include recent blog posts and active content maintenance. Strategic observations highlight the site's role as a personal branding and knowledge-sharing platform rather than a commercial entity.

Security posture

The security posture is moderate. The domain is protected against unauthorized transfer via clientTransferProhibited status. However, the absence of security headers, privacy and cookie policies, and vulnerability disclosure reduces the overall security maturity. No incident response or security contact information is provided. The site does not employ a WAF or other blocking mechanisms, which simplifies access but may expose it to some risks. No exposed sensitive data or vulnerabilities were detected. Compliance with GDPR or other privacy regulations is not evident. The security culture appears informal, consistent with a personal site rather than a corporate environment.

Recommendations

  1. Implement and publish a comprehensive privacy policy and cookie policy to improve privacy compliance.
  2. Add security headers such as Content-Security-Policy, X-Frame-Options, and Strict-Transport-Security to enhance security posture.
  3. Ensure HTTPS is enforced site-wide and verify SSL configuration is strong.
  4. Publish a vulnerability disclosure policy or security.txt file to facilitate responsible reporting.
  5. Improve mobile optimization and accessibility to enhance user experience and compliance.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Joey Hess
Description
Personal website of Joey Hess focused on building worthwhile things that might last, featuring blog posts, technical projects, and personal interests.
Key services
blog posts, technical code repositories, talks and podcasts, personal projects
Content quality
good
Branding
consistent

Technology

Stack
HTML5, CSS, JavaScript
Frameworks
ikiwiki
Performance
moderate
Mobile
basic
Accessibility
basic
SEO
basic

Security

Observed score
60/100
Good practices seen
  • Domain status clientTransferProhibited

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
high

Key observations

  1. Website is a personal technical blog and portfolio for Joey Hess.
  2. No privacy, cookie, or terms of service policies found.
  3. No explicit contact emails or phone numbers visible; contact form is available.
  4. No security.txt or vulnerability disclosure found.
  5. No advertising or tracking technologies detected.
  6. Site uses ikiwiki CMS and is hosted under domain registered by Gandi SAS.
  7. Content is safe and suitable for general audiences.
  8. No WAF or blocking mechanisms detected.
  9. Site design is simple but functional with dated blog entries indicating active maintenance.
Technical notes

Notes

The website uses ikiwiki as a static site generator, with standard HTML, CSS, and JavaScript technologies. The site is hosted on a domain registered with Gandi SAS, a reputable registrar. Performance is moderate with basic mobile responsiveness and accessibility. SEO is basic with meta description present but no advanced structured data or Open Graph tags detected. No analytics or tracking scripts are present, indicating minimal data collection. The site structure is clear and navigation is straightforward. Technical debt appears low given the static nature of the site, but modernization opportunities include improved mobile optimization and security header implementation.
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 joeyh.name. 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 joeyh.name.

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.