Skip to main content

Security report for haylinmoore.com

Haylin Moore · Technology · N/a

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

Security score

53/100

Risk levelMedium

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

Haylin Moore's website serves as a personal professional portfolio and technical blog highlighting his expertise as a software and network engineer. The site features detailed descriptions of his current and past roles at reputable technology companies, alongside open source projects and technical writings. The target audience includes technology professionals and open source enthusiasts. The business model is centered on personal branding and knowledge sharing rather than commercial transactions. Technically, the website is built using modern web standards with HTML5, CSS3 (Pure.css framework), and JavaScript. It is mobile-optimized and performs well with fast loading times. The site uses HTTPS, ensuring secure connections, but lacks explicit security headers and privacy policies. No analytics or tracking scripts are present, indicating a privacy-conscious approach. From a security perspective, the site demonstrates good baseline practices such as HTTPS usage and absence of user input forms, reducing attack surface. However, it lacks published security policies, incident response contacts, and vulnerability disclosure mechanisms. The WHOIS data is privacy protected, which is appropriate for a personal site, and no suspicious patterns were detected. Overall, the website is professional, trustworthy, and safe for general audiences. Strategic improvements include adding privacy and cookie policies, security headers, and contact information to enhance compliance and 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

8 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"

    • 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';…

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

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

Keep watching haylinmoore.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. 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
60
DNS health
75
Network security
40
GDPR outside view
50
Average
53

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 positions Haylin Moore as a skilled technology professional with experience at notable companies like Qumulo and Arista Networks. The portfolio showcases a strong focus on network and software engineering, open source contributions, and technical thought leadership through blog posts. The business model is personal branding and community engagement rather than direct commercial activity. The site links to a broad ecosystem of technology-related domains and collaborators, indicating a well-connected professional network. Growth indicators include recent project updates and active GitHub repositories. The absence of commercial elements suggests a focus on reputation building and knowledge sharing.

Security posture

The security posture is moderate with HTTPS enforced and no visible vulnerabilities or exposed sensitive data. The lack of security headers and formal security policies represents an area for improvement. No forms or user data collection reduces risk exposure. The absence of incident response contacts and vulnerability disclosure policies limits transparency and readiness. GDPR compliance is not addressed explicitly. Overall, the site is low risk but could benefit from enhanced security best practices and compliance documentation.

Recommendations

  1. Implement and publish a comprehensive privacy policy and cookie policy to improve compliance and user trust.
  2. Add security headers such as Content Security Policy (CSP), HTTP Strict Transport Security (HSTS), and X-Frame-Options to enhance security posture.
  3. Provide clear contact information including a security or abuse contact email to facilitate incident reporting.
  4. Consider publishing a vulnerability disclosure policy or security.txt file to encourage responsible security reporting.
  5. Enhance accessibility features to improve usability for all users and meet best practices.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Haylin Moore
Description
Personal website and blog of Haylin Moore, a software and network engineer from the east coast. The site showcases personal projects, writings, and professional background including current and past employers.
Key services
Software engineering insights, Network engineering expertise, Open source project contributions, Technical blog articles
Content quality
good
Branding
consistent

Technology

Stack
HTML5, CSS3 (Pure.css framework), JavaScript
Frameworks
Pure.css
Performance
fast
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
75/100
Good practices seen
  • HTTPS enforced (implied by canonical URL https://hayl.in/)
  • No forms detected to collect user input

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. Personal professional portfolio and blog site
  2. No privacy, cookie, or terms of service policies found
  3. No contact emails or phone numbers explicitly provided
  4. No forms or user input fields detected
  5. Site uses HTTPS and modern CSS framework
  6. No analytics or tracking scripts detected
  7. No advertising or affiliate marketing present
  8. Content is technical and professional with open source projects and blog posts
  9. No security headers explicitly detected in HTML content
  10. No security or incident response policies published
Technical notes

Notes

The website uses a clean and modern tech stack with HTML5, CSS3 (Pure.css), and JavaScript. It is mobile responsive and loads quickly, indicating good performance optimization. The absence of a CMS suggests a static or custom-built site, reducing complexity and potential vulnerabilities. No analytics or third-party tracking scripts are present, enhancing privacy. The site lacks explicit security headers and formal metadata such as JSON-LD structured data, which could improve SEO and security. Hosting provider details are not discernible from the content. Overall, the technical implementation is solid with room for enhancements in security and metadata.
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 haylinmoore.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 haylinmoore.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.