Skip to main content

Security report for elmikewalsh.com

Mike Walsh · Technology · Chile

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

Security score

68/100

Risk levelMedium

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

The website elmikewalsh.com serves as a personal portfolio and blog for Mike Walsh, a front-end web designer, developer, and translator based in Villarrica, Chile. The site highlights his skills, writings, and professional presence with links to his GitHub, Medium, and Mastodon profiles. The business model is that of an individual professional showcasing services and content to a general audience interested in technology, politics, humor, and life. The site is well-structured, visually consistent, and optimized for mobile devices, reflecting a good level of digital maturity for a personal brand. Technically, the website is built using modern web standards including HTML5, CSS3, JavaScript, and JSON-LD structured data for SEO. It uses a static site generator (Publii), which contributes to fast loading times and good performance. The site is served over HTTPS with a valid SSL certificate, and minimal external scripts are used, primarily for analytics via Cloudflare Insights. Accessibility and SEO optimizations are present but could be enhanced further. From a security perspective, the site enforces HTTPS and does not expose sensitive data or use vulnerable libraries. However, it lacks explicit security headers and does not provide privacy, cookie, or terms of service policies, which are important for compliance and user trust. No contact information for security incidents or vulnerability disclosure mechanisms are present. The WHOIS data is unavailable or the domain is unregistered, which raises concerns about domain legitimacy and trustworthiness. Overall, the website is professional and safe for general audiences but would benefit from improved privacy compliance, clearer domain registration information, and enhanced security practices. Strategic recommendations include publishing privacy and cookie policies, adding security headers, providing contact channels for incident response, and implementing a vulnerability disclosure policy to strengthen 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 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

    • 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 elmikewalsh.com

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
75
Security headers
50
Email security
65
DNS health
70
Network security
100
GDPR outside view
50
Average
68

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

Breach exposure

Leaked credentials and lookalike domains from OffSeq Breach. The counts are free; the detailed lists are paid add-ons.

Dark web exposure

Add-on

Leaked records that mention elmikewalsh.com, from OffSeq Breach.

No leaked records found

Breach holds no records for elmikewalsh.com right now. New leaks arrive continuously, so monitoring on Breach alerts you if that changes.

Monitor on Breach (opens in a new tab)

Technical appendix

Business context, site observations and technical notes gathered during the scan, and the standards behind each reference.

Business context

Business profile

Elmikewalsh.com operates as a personal brand website for Mike Walsh, targeting clients and readers interested in front-end web design, development, and translation services. The business model is service-oriented with content marketing through blogging. The site positions Mike Walsh as a skilled individual professional rather than a corporate entity. The presence of GitHub and Medium profiles supports credibility and community engagement. There is no indication of partnerships, subsidiaries, or parent companies. Revenue streams likely derive from freelance or contract work and possibly consulting. The website's clean design and focused content suggest a niche market presence with growth potential through content and service expansion.

Security posture

The website demonstrates a basic to moderate security posture. HTTPS is enforced with a valid SSL certificate, which is a critical security baseline. No forms or inputs collect sensitive data, reducing attack surface. However, the absence of security headers such as Content-Security-Policy, X-Frame-Options, and others is a gap. The lack of privacy and cookie policies indicates non-compliance with GDPR and other privacy regulations. No incident response or vulnerability disclosure information is provided, which limits transparency and preparedness. The missing WHOIS data for the domain reduces trust and raises questions about domain ownership legitimacy. Overall, the security posture is adequate for a personal portfolio but requires improvements for professional and compliance standards.

Recommendations

  1. Publish comprehensive privacy and cookie policies to improve GDPR compliance and user trust.
  2. Implement standard security headers (Content-Security-Policy, X-Frame-Options, Strict-Transport-Security) to enhance protection against common web attacks.
  3. Provide clear contact information for security incidents and consider publishing a vulnerability disclosure or security.txt file.
  4. Verify and update domain registration information to ensure transparency and legitimacy.
  5. Enhance accessibility features and conduct regular security audits to maintain a strong security posture.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Mike Walsh
Description
Mike Walsh, a front-end designer, developer, and translator in Villarrica, Chile, writes about tech, politics, humor, and life. See his blog and portfolio.
Key services
front-end web design, web development, translation, blog writing
Content quality
good
Branding
consistent

Technology

Stack
HTML5, CSS3, JavaScript, JSON-LD, Cloudflare Insights
Performance
fast
Mobile
good
Accessibility
good
SEO
good

Security

Observed score
85/100
Good practices seen
  • HTTPS enforced
  • No exposed sensitive data
  • No visible vulnerable libraries
  • No forms collecting sensitive data

Analytics and tracking

Services
Cloudflare Insights
Tracking level
minimal
Privacy practices
poor

Advertising

Tracking pixels
Cloudflare Insights
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 portfolio and blog for Mike Walsh, a front-end developer and translator based in Chile.
  2. No WHOIS registration data available, possibly domain not registered or WHOIS data restricted.
  3. No privacy, cookie, or terms of service policies found on the site.
  4. No contact emails or phone numbers explicitly provided on the homepage or footer.
  5. Site uses HTTPS with a valid SSL certificate.
  6. No forms present on the homepage; no data collection detected.
  7. Social media links to GitHub, Medium, and Mastodon are present.
  8. No security.txt or vulnerability disclosure information found.
  9. Site uses a static site generator (Publii) and minimal external scripts.
  10. No advertising or affiliate marketing detected.
Technical notes

Notes

The website is built on a static site generator (Publii), leveraging modern web technologies such as HTML5, CSS3, JavaScript, and JSON-LD structured data for SEO. It uses Cloudflare Insights for analytics, which is lightweight and privacy-conscious. The site loads quickly and is mobile optimized with good accessibility practices. No CMS or complex backend detected, reducing attack surface and maintenance overhead. However, the site lacks advanced security headers and privacy compliance mechanisms. The absence of WHOIS data suggests a need to verify domain registration status. Overall, the technical infrastructure is solid for a personal portfolio but could be enhanced with improved security and 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 elmikewalsh.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 elmikewalsh.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.