Skip to main content

Security report for lewisakura.moe

Private by Design, LLC · Technology · United States

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

Security score

73/100

Risk levelMedium

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

The website lewisakura.moe is a personal site belonging to Lewis, a young software engineer and aspiring content creator specializing in backend development and game development on platforms such as Roblox. The site serves as a portfolio and contact point, showcasing various projects and placements, both paid and volunteer. The business model is primarily freelance and team-based development with future plans for content creation as a VTuber. The site targets technology enthusiasts and potential collaborators. Technically, the site is built using the Astro framework, leveraging modern web technologies and hosted with Cloudflare DNS services. It is well optimized for performance and mobile devices, with good SEO metadata and clear navigation. No CMS or analytics tools are detected, indicating a lightweight and privacy-conscious approach. From a security perspective, the site uses HTTPS and has domain transfer and deletion protections enabled. However, DNSSEC is not enabled, and no security headers are detected, which are areas for improvement. No privacy or cookie policies are published, which impacts compliance posture. Contact information is clearly provided via email and Discord, but no formal incident response or security policies are present. Overall, the site is safe, professional, and trustworthy for its intended personal and freelance use. Strategic recommendations include adding privacy and cookie policies, enabling DNSSEC, implementing security headers, and considering incident response documentation to enhance security and compliance.

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

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

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
50
Email security
95
DNS health
85
Network security
100
GDPR outside view
35
Average
73

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 lewisakura.moe, from OffSeq Breach.

Total records
4
Employees
0
Customers
4
Third parties
0
Weak passwords
25%

2 subdomains affected

See the 10 newest leaked credentials

A one-off add-on to this report that lists the most recent identifier and password pairs OffSeq Breach holds for lewisakura.moe.

Select it in the checkout above.

Breach keeps ingesting new leaks, so these numbers can grow between scans.

Technical appendix

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

Business context

Business profile

Lewis operates as an individual freelance software engineer and content creator with a niche focus on backend development and Roblox game development. The business model includes paid commissions, volunteer work, and personal projects. The portfolio reveals a mix of short-term and ongoing projects, indicating flexibility and adaptability. The target market includes technology enthusiasts, game developers, and content consumers. The website's presence on multiple social media platforms supports community engagement and brand building. The use of privacy protection in WHOIS is typical for personal sites and helps protect identity. The business is small, recently founded, and positioned as a growing personal brand with potential expansion into content creation.

Security posture

The website demonstrates a moderate security maturity level with HTTPS enforced and domain status protections in place. The absence of DNSSEC and security headers represents a moderate risk that could be mitigated to improve DNS and HTTP security. No vulnerabilities or exposed sensitive data were detected. The lack of privacy and cookie policies indicates compliance gaps, particularly with GDPR. Incident response readiness is not documented, which could delay response to security incidents. Overall, the security posture is adequate for a personal site but should be enhanced to support professional credibility and compliance.

Recommendations

  1. Enable DNSSEC on the domain to improve DNS security and prevent spoofing.
  2. Publish a comprehensive privacy policy and cookie policy to improve GDPR compliance.
  3. Implement standard security headers such as Content-Security-Policy, X-Content-Type-Options, and Strict-Transport-Security.
  4. Develop and publish an incident response policy with clear contact channels for security issues.
  5. Consider adding analytics with privacy-respecting configurations to monitor site usage and improve user experience.
Site observations

Automated reading of the public site. Ratings are indicative.

Business

Company
Private by Design, LLC
Description
Personal website of Lewis, a 20-year-old software engineer and aspiring content creator focused on backend development, game development (primarily Roblox), and content creation including plans to become a VTuber.
Key services
Backend software engineering, Game development (Roblox, Unity, Unreal, Godot), Content creation (future VTuber plans), Freelance commissions
Content quality
good
Branding
consistent

Technology

Stack
Astro v5.2.5, JavaScript (ES Modules), Cloudflare DNS, CSS
Frameworks
Astro
Platforms
Roblox, Discord
Performance
fast
Mobile
good
Accessibility
basic
SEO
good

Security

Observed score
75/100
Good practices seen
  • HTTPS enforced (implied by canonical URL and Cloudflare usage)
  • Domain status clientTransferProhibited and clientDeleteProhibited

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. Personal website of a young software engineer and content creator
  2. No privacy, cookie, or terms of service policies found
  3. No security or incident response policies published
  4. Contact information provided via email and Discord username
  5. No forms detected on the website
  6. Modern static site generated with Astro framework
  7. No analytics or tracking scripts detected
  8. No advertising or affiliate marketing detected
  9. Good mobile optimization and SEO metadata present
  10. No security headers detected in provided data
Technical notes

Notes

The website is built using the Astro static site generator (version 5.2.5), leveraging modern JavaScript modules and CSS for styling. It is hosted behind Cloudflare DNS, which provides performance and security benefits. The site loads quickly and is mobile optimized with responsive design. SEO metadata including Open Graph tags and canonical links are properly implemented. No CMS or third-party analytics/tracking scripts are detected, indicating a lightweight and privacy-focused implementation. The absence of security headers and DNSSEC are technical gaps. Overall, the technical infrastructure is modern, efficient, and well-suited for a personal portfolio site.
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 lewisakura.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 lewisakura.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.