Skip to main content

Security report for lkhrs.com

Luke’s Wild Website · Technology · United States

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

Security score

74/100

Risk levelMedium

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

Luke’s Wild Website is a personal portfolio and blog site operated by Luke Harris, a developer and designer based in Chicago. The site serves as a platform for sharing blog posts, notes, and personal insights, targeting a general audience interested in technology and personal content. The website is built on the Ghost CMS platform, utilizing modern web technologies such as HTML5, CSS3, and JavaScript, with a clean and consistent design that supports good user experience and mobile optimization. However, the site lacks explicit contact information, privacy policies, and security headers, which impacts its overall trustworthiness and compliance posture. From a technical perspective, the website demonstrates moderate performance and good SEO optimization but lacks advanced security configurations such as HTTPS enforcement and security headers. The absence of WHOIS registration data raises concerns about domain legitimacy, although the site content appears genuine and updated recently. No advertising or analytics services are detected, indicating minimal user tracking and a privacy-conscious approach, albeit without formal policies. Security posture is currently weak due to missing HTTPS confirmation, lack of security headers, and no visible incident response or data protection policies. The site does not expose sensitive data or show signs of vulnerabilities but would benefit from implementing standard security best practices and publishing privacy and cookie policies to improve compliance and user trust. Overall, the website is functional and professional for a personal blog but requires improvements in security and compliance to enhance credibility and protect visitors.

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

5 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 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

  3. SSL/TLS

    TLS encrypts the connection and proves the site is really yours. Weak or expiring certificates trigger browser warnings and put traffic at risk.

    • High

      Weak SSL Key Length

      SSL certificate uses 256-bit key, which is considered weak

      What to do: Use at least 2048-bit RSA or 256-bit ECC key

      • CWE-326
      • OWASP A04:2025
      • Mozilla TLS: Mozilla Server Side TLS 6.0 intermediate: rsa_key_size 2048

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

Keep watching lkhrs.com

This scan found 17 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
65
Email security
70
DNS health
85
Network security
100
GDPR outside view
50
Average
74

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 operates as a personal brand and content platform for Luke Harris, focusing on technology and design topics. Its market position is niche, serving a small audience interested in personal blogs and developer insights. The business model is primarily informational and personal branding without evident monetization or commercial services. The absence of contact details and formal business information suggests a non-commercial intent. Growth indicators and partnerships are not evident, and the site appears self-managed. The lack of WHOIS data and privacy policies limits business credibility and may affect user trust. The site’s ecosystem is minimal, with no external partnerships or subsidiaries identified.

Security posture

The current security maturity level is low, with no HTTPS confirmation in the provided data and no security headers detected. There are no visible vulnerabilities or exposed sensitive data, but the absence of privacy, cookie, and incident response policies indicates compliance gaps, particularly with GDPR and similar regulations. The site lacks a vulnerability disclosure policy and security.txt file, reducing transparency for security researchers. Incident response readiness is unknown due to missing contact channels for security issues. Overall, the security culture appears informal, typical for a personal website, but improvements are recommended to mitigate risks and enhance trust.

Recommendations

  1. Implement HTTPS with a valid SSL/TLS certificate and enforce secure connections site-wide.
  2. Add standard security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options.
  3. Publish comprehensive privacy and cookie policies to comply with GDPR and other regulations.
  4. Provide clear contact information including a dedicated security or abuse email address.
  5. Establish a vulnerability disclosure policy and consider adding a security.txt file to facilitate responsible reporting.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Luke’s Wild Website
Description
I’m Luke Harris, a developer and designer who has spent way too much time on the computer. I live in Chicago with my partner and cats.
Key services
Blog, Notes, Mutex, About, Now, Uses, Stats, Blogroll, Contact
Content quality
good
Branding
consistent

Technology

Stack
HTML5, CSS3, JavaScript, Ghost CMS
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
40/100

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 portfolio/blog for Luke Harris.
  2. No privacy, cookie, or terms of service policies found.
  3. No contact emails or phone numbers explicitly provided.
  4. No security headers or explicit HTTPS confirmation in provided data.
  5. No advertising or analytics scripts detected.
  6. Content is safe and suitable for general audiences.
  7. WHOIS data missing, which is a concern for domain legitimacy.
  8. Site uses Ghost CMS and modern web fonts.
  9. No forms detected on the homepage content.
  10. Social media links are not explicitly present except self-link to website.
Technical notes

Notes

The website uses Ghost CMS, a modern and popular blogging platform, combined with standard web technologies like HTML5, CSS3, and JavaScript. The site loads custom fonts and scripts efficiently, indicating moderate performance. Mobile optimization is good, and SEO meta tags are well implemented. However, no hosting provider or CDN information is available, and no advanced frameworks beyond Ghost are detected. Accessibility is basic but could be improved. The lack of security headers and HTTPS confirmation are technical risks. Overall, the infrastructure is suitable for a personal blog but requires enhancements for professional and secure operation.
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 lkhrs.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 lkhrs.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.