Skip to main content

Security report for lmika.org

Technology · Australia

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

Security score

57/100

Risk levelMedium

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

The website lmika.org is a personal blog and portfolio site for Leon Mika, a software developer and occasional music writer based in Melbourne, Australia. The site features blog posts, photos, and links to various technology and personal interest sites. It is built using the Hugo static site generator and hosted on the Micro.blog platform, indicating a modern and lightweight technical infrastructure. The site includes JavaScript enhancements such as a service worker and lightbox functionality for images, and uses minimal third-party analytics via tinylytics.app. From a security perspective, the site uses HTTPS and registers a service worker, but lacks advanced security headers and does not have visible privacy or cookie policies, nor contact information for security incidents or data protection officers. The domain is privacy protected via Contact Privacy Inc., which is typical for personal sites, and the domain age aligns with the site's content history. No vulnerabilities or suspicious patterns were detected in the content or technical setup. Overall, the site presents a good level of content quality, technical implementation, and business credibility for a personal blog, but falls short on privacy compliance and security best practices. There is no evidence of adult or unsafe content, and the site is fully accessible without WAF or blocking mechanisms.

Scanned

NIS2 and GDPR posture

GDPR outside view
35/ 100 · High
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

9 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 lmika.org

This scan found 26 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
65
Security headers
15
Email security
70
DNS health
55
Network security
100
GDPR outside view
35
Average
57

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 serves as a personal brand platform for an individual software developer, targeting a general audience interested in software development, technology, and personal musings. The business model is primarily content sharing and personal branding rather than commercial transactions. The site links to a broad ecosystem of technology bloggers and influencers, indicating engagement with a knowledgeable community. There are no indications of revenue streams or partnerships beyond content recommendations. The site is small in scale, consistent with an individual operator, and shows steady content updates and engagement with current technology topics.

Security posture

The security posture is moderate. HTTPS is used, and a service worker is registered, which is positive. However, the absence of security headers such as Content-Security-Policy, X-Frame-Options, and others reduces the overall security hardening. No privacy or cookie policies are present, which is a compliance gap under GDPR and similar regulations. No incident response or vulnerability disclosure information is provided, limiting transparency and readiness. The domain uses privacy protection, which is justified for a personal site. No critical vulnerabilities or exposed sensitive data were found.

Recommendations

  1. Implement and publish a comprehensive privacy policy and cookie policy with consent mechanisms to improve privacy compliance.
  2. Add security headers such as Content-Security-Policy, X-Frame-Options, and X-Content-Type-Options to enhance security posture.
  3. Provide clear contact information for general inquiries and security incidents, including a security or abuse email address.
  4. Consider publishing a security.txt file to facilitate vulnerability disclosure and improve transparency.
  5. Enable DNSSEC on the domain to improve DNS security and trustworthiness.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Description
Software Developer and occasional writer of music. Based in Melbourne, Australia.
Key services
software development insights, personal blogging, music writing
Content quality
good
Branding
consistent

Technology

Stack
Hugo 0.117.0, JavaScript, CSS, HTML5, Service Worker, glightbox
Platforms
Micro.blog
Performance
moderate
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
60/100
Good practices seen
  • Uses HTTPS (implied by canonical URL https://lmika.org/)
  • Service Worker registered

Analytics and tracking

Services
tinylytics.app
Tracking level
minimal
Privacy practices
poor

Advertising

Tracking pixels
tinylytics.app
Marketing tools
tinylytics.app
Transparency
basic

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 software developer based in Melbourne, Australia.
  2. No privacy, cookie, or terms of service policies found.
  3. No contact emails or phone numbers explicitly provided.
  4. No security.txt or vulnerability disclosure information found.
  5. Uses Micro.blog platform and Hugo static site generator.
  6. Includes multiple external links to reputable technology and personal blogs.
  7. Minimal tracking via tinylytics.app analytics.
  8. No signs of adult or unsafe content.
  9. No WAF or blocking mechanisms detected.
  10. Domain uses privacy protection but is consistent with personal use.
Technical notes

Notes

The website uses a modern static site generator (Hugo) and is hosted on Micro.blog, a platform tailored for blogging and personal publishing. The tech stack includes JavaScript for UI enhancements and service worker registration for offline capabilities. External resources are loaded from reputable CDNs and Micro.blog domains. Performance is moderate with good mobile optimization and basic accessibility features. SEO is supported with proper meta tags and Open Graph data. There is no evidence of technical debt or legacy technologies. Opportunities exist to improve security headers and privacy compliance to reduce risk and enhance user trust.
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 lmika.org. 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 lmika.org.

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.