Skip to main content

Security report for hayden.moe

N/A · Technology · United Kingdom

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

Security score

64/100

Risk levelMedium

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

The website hayden.moe is a personal blog and portfolio site for Hayden, a UK-based DevOps and Platform Engineer. The site serves as a platform for sharing technical insights, personal interests, and community engagement through social media and Discord. It targets developers and technology enthusiasts, positioning itself as a niche personal technical blog with a focus on DevOps and platform engineering topics. The business model is primarily personal branding and content sharing, with no commercial transactions or services offered directly on the site. Technically, the site is built using modern web standards with HTML5 and CSS, leveraging the Astro framework for styling. Hosting and DNS are managed via Cloudflare, providing good performance and security at the infrastructure level. The site is mobile optimized and has a clean, consistent design with good navigation and user experience. However, there is room for improvement in accessibility and SEO optimization. From a security perspective, the site enforces HTTPS and uses domain transfer protection, but lacks DNSSEC and security headers such as Content-Security-Policy and 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, which is a notable gap especially for GDPR compliance. No incident response or vulnerability disclosure information is provided. Overall, the site is low risk with a good security baseline but would benefit from enhanced privacy compliance and security hardening. Strategic recommendations include publishing privacy and cookie policies, enabling DNSSEC, adding security headers, and implementing a vulnerability disclosure policy to improve trust and compliance.

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 hayden.moe

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
65
DNS health
80
Network security
100
GDPR outside view
50
Average
64

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

Hayden.moe operates as a personal technical blog and portfolio for an individual DevOps engineer based in the UK. The site targets a niche audience of developers and technology professionals interested in DevOps and platform engineering. The business model is non-commercial, focusing on personal branding and community engagement through social media platforms such as GitHub, Discord, Twitch, and Bluesky. The site demonstrates consistent branding and good content quality, with a focus on reproducibility and automation in DevOps. There are no indications of revenue streams or partnerships. The domain age and privacy protection are consistent with a personal site. The site’s ecosystem includes links to social and community platforms but no direct business partnerships or subsidiaries.

Security posture

The website maintains a moderate security posture with HTTPS enforced and domain transfer protection enabled. However, the lack of DNSSEC and security headers reduces the overall security maturity. No forms or data collection mechanisms reduce the attack surface. The absence of privacy and cookie policies indicates compliance gaps, particularly with GDPR. No incident response or vulnerability disclosure mechanisms are present, limiting the ability to handle security incidents effectively. No vulnerabilities or exposed sensitive data were detected in the content. Overall, the security posture is adequate for a personal blog but would benefit from implementing best practices such as security headers, DNSSEC, and formal privacy compliance documentation.

Recommendations

  1. Publish 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. Implement security headers including Content-Security-Policy, X-Content-Type-Options, and Strict-Transport-Security.
  4. Create and publish a vulnerability disclosure policy or security.txt file to facilitate responsible reporting.
  5. Consider adding accessibility improvements and SEO enhancements to broaden audience reach and usability.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
N/A
Description
Personal blog and portfolio of a UK-based DevOps and Platform Engineer named Hayden, sharing insights on DevOps, platform engineering, and personal interests.
Key services
Technical blogging, Personal portfolio, Community engagement via social media and Discord
Content quality
good
Branding
consistent

Technology

Stack
HTML5, CSS (Astro framework CSS file), Cloudflare DNS, GitHub for version control
Frameworks
Astro
Performance
fast
Mobile
good
Accessibility
basic
SEO
basic

Security

Observed score
80/100
Good practices seen
  • HTTPS enforced (implied by canonical URL https://hayden.moe/)
  • Domain status clientTransferProhibited
  • No exposed sensitive data in HTML

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. Website is a personal blog and portfolio of a UK-based DevOps engineer named Hayden.
  2. No privacy or cookie policies found, indicating potential compliance gaps.
  3. No forms detected on the site; minimal data collection.
  4. Social media and community links are provided for engagement.
  5. No advertising or tracking scripts detected, indicating privacy-conscious design.
  6. Site uses Cloudflare DNS and likely CDN for hosting and performance.
  7. No security headers detected in provided data; opportunity for improvement.
  8. WHOIS data shows privacy protection, common for personal sites.
  9. No signs of malicious or suspicious content.
Technical notes

Notes

The website is built with modern web technologies including HTML5 and CSS, styled using the Astro framework. Hosting and DNS services are provided by Cloudflare, ensuring good performance and security at the network level. The site loads quickly and is mobile optimized with a clean, monospace font-based design consistent with developer-focused branding. No CMS or heavy JavaScript frameworks were detected, indicating a lightweight and maintainable codebase. The site lacks advanced SEO features and accessibility enhancements but provides a solid foundation for a personal technical blog. There are no signs of technical debt or outdated libraries. Opportunities exist to improve security headers and implement privacy compliance features.
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 hayden.moe. 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 hayden.moe.

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.